Discussion Locked

Giving WEP Key to non-technical people

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Why is that in each company we have people who think they are tech savy and want to play IT. They somehow convince the Manager that if they fired the IT person they can help out only to access what on the network. How do you handle such people?

7 replies

by why me worry?

I don't know the reason exactly behind these people and their intentions, but buying a Linksys wireless router and setting up a wireless network at home does not make one a Network guru or IT professional. Anyhow, such mentality stems from the dot com days when anyone who knew how to power on a PC or connect a keyboard was automatically branded as an "IT Guru" by those who knew nothing about IT or what the function of IT was. I'd love to see these so called "know it alls" do my job for a day. I guarantee that they would be hauled away in an ambulance with a nervous breakdown and soiled undergarments from the daily stress and technical issues we have to endure every day.

by dr dij

to give all passwords to upper management. I don't know if this is directly related to your post but I've had problems where upper management asked for all passwords for end users. I didn't think this was a good idea.

Sure, they should have an admin password available locked away in case sysadmin gets run over by a bus. But there is no reason in the world they need all the passwords for either all internal end users or external customers logging into a service via wan or web.

Some consultant tells them they should have this without telling them they don't need them all. If a customer lost their password in the online service above I mentioned, I would assign them a new one. I didn't even keep their original one on purpose for security, so no faked transactions. (this was a service where data integrity for individuals was critical).

The advantage: in the remote chance the caller hadn't authenticated themselves to me to request a password change, the original users would know because they wouldn't be able to login.

And chances are if they requested a new password, it was a new person using system, so effectively a change password would lockout the previous user who was no longer with the customer site or doing some other job for customer.

Modern security systems have password reset functions built in. So support personnel don't always need your password.

by dougwadley

This worked for me in seeing off a challenge to my administration of a specialty area.

Ask the manager to remove the IT person from active support for a fortnight (there's always some maintenance they can do). All complaints must be referred to the manager.

Mop blood off floor - continue as before.

by snoopdoug

First of all, avoid direct confrontation. You may win the battle, but you will lose the war. Agree with the parts of their argument that makes sense, but gently point out the fallacy of the remaining parts. Don't make it sound like they haven't thought it out, perhaps just act as if it is the first time you ever thought of the danger of part 3 of their argument.

Or just let them hang from their own petard. Stand back, watch them crash and burn, and offer to help. Be sure to CC as many other company managers and officers as could be construed as being thorough. You will be seen as the hero, but don't gloat or say "I told you so". Fake sincerity is crucial at this point, LOL.

Or quit. If this is yet another example of the company ignoring your expert advice, going over your head or around your back, you should think about another company. Leave while you have a job--you will always look more employable.

I work as a contract programmer/writer. In my experience I have found that I am very leery of working for a startup where none of the principles has worked with a writer before. I find that quite often they go through two or three writers before they figure out how to work with them. If the interviews are chaotic, if folks are constantly late, don't have a conference room scheduled, or other red flags wave, I do not take on the contract, regardless of how interesting the gig or how high the rate. Better my sanity than a big paycheck.

doug in Seattle

by realvdude

Depending on what size organization we're talking about, giving out a WEP key is not a big deal. Hopefully there is additional security, unless it is a home network (I even run additional security at this level). If your large enough, your talking to some sales guy at his desk, and telling him what to put in the wireless configuration, so guess what, you've just given out the key! Now you have some faith tihs sales guy is not going to give out or sell the key for evil intention, but that is why it should never be your only security. In fact, you could use MAC filtering for your wireless, so that anyone else trying to use the key would also have to spoof their MAC as well.

As far as some novice or wanabe trying to take the IT job, well their just not happy with their job/pay. I happen to work at one of those companies that is big enough to need a IT person and small enough not to be able to afford one. The IT job is split between myself maintaining servers and the senior hardware tech handle desktops. He handles user changes, and I handle resource security and the internet. Most companies fall above or below this, and would either use an outside IT consultant or have a solo IT person. In either of those cases, the manager or owner should have enough information tucked away in the safe to replace either the consultant or the employee.
Also serving in client support, it is frustrating when dealing with a consultant (often a friend or relative) who has attained that BA of BS and doesn't know what they are doing. It's especially frustrating when I find out that someone is getting paid for their lack of knowledge. In both cases the client usually bawks at the invoice for my time to hold someone's hand through they should have known how to do.

by fred123456

If your sure they don't have the chops then let them try and fail.

In fact, talk to your boss and take a week off around the same time that something is getting installed or setup.

by realvdude

You may be 100% sure they'll fail, but are you ready to bet your job on it? Even if they struggle for week to do what you could in a day, you have to be certain of what your boss is going to think. There is also the question/ramifications of are you going to swoop in and save the day, if called to do so.

This discussion is closed to new replies.