Slashdot Mirror
Bone-Headed IT Mistakes
snydeq writes "PCs preconfigured with stone-age malware, backups without recovery, Social Security numbers stored in plain view of high school students — Andy Brandt gives InfoWorld's Stupid Users series a new IT admin twist. Call it fratricide if you will, but getting paid to know better is no guarantee against IT idiocy, as these stories attest."
http://www.infoworld.com/archives/emailPrint.jsp?R=printThis&A=/article/08/06/16/25FE-stupid-users-part-3-admins_1.html Printer friendly version, rather then 7 pages.
Deleting hundreds of thousands of White House emails, and not having a backup?
http://www.thedailywtf.com/
pretty much a new bone head story every day
Information Security isn't going to get better without a major shift in how people work. As a society, we need to examine who really needs what data and then truly limit everyone to what they need. Until we can define these roles/access levels in black and white terms and permanently adhere to the controls put in place, there will always be IT blunders.
The problem is that these changes are rarely permanent, but more of a pendulum that swings back and forth as events like this occur. If Bob is taking home Social Security numbers on his laptop and someone steals it, controls may be put in place to prevent people from saving files to their laptops (and Bob is let go). Six months later, Suzie complains that she needs to be able to copy a proposal she's working on so that she can work on her flight to Japan. An exception is made. This typically snowballs until we're back to where Joe can copy the accounting records with SSNs.
Ease of access and efficiency nearly always trump security when these breaches aren't fresh in everyone's minds.
When a company simply accepts what the sales drone says about a given product as a fact.
(/local/home/curiosity)-#who -u|grep thecat|cut -c 44-49|xargs kill -9
2. Continuing education for your IT people.
3. Just because someone looks old, doesn't make them a competent 'seasoned' IT guy.
4. Respect your IT pro's opinions.
We all have a plethora of stories of users, but even more of fellow co-workers in over their heads causing massive damage. Sometimes it goes unseen, other times it can desecrate a business. Make sure your IT people are educated, have a passion for what they do. Not just a paycheck monkey draining your resources.
A good test here, if your IT head is an ex-HR manager, mailroom clerk, secretary, or other far removed profession and have yet to get any certifications or degrees to prove their competence after 10 years then you probably are in trouble. Not in every case, but enough to make you worry.
Im not saying that a cert or degree proves that you are competent, but it at least shows that you try to be.
CS: It is all sink or swim...oh and did I mention there are sharks in that water?
I was new to the whole *nix thing but had been let loose as root on all the boxes at work. Someone suggested I could/should create a script to customise my environment so that I could run it when I logged on. Problem was I named the script "df" (my initials) and then promptly decided that it needed to go in to the /usr/bin/ directory. Yeah - now you know why I posted anonymously. :-D
See your mistake was believing that you actually had a "trusted IT friend".
You mad
At my middle school, there was a policy to give every student an ID card. That's fine. They decided that the best number to use for their ID is their Social Security Card. That's bad. They printed out a sheet every day listing the absent students for the day, with their names and their school id's. That is worse. Teachers threw these into their trashcans when they were done. Yes, the train wreck isn't over yet. The spreadsheet containing all of these numbers was on a public share. It was also accessible from the school website.
Or how about 3 years later, in my high school. All of the teachers user names and default passwords were on a spreadsheet on a network share. A publicly accessible network share. If a teacher didn't change their default password (a 4 digit number), A student would have full reign over their data.
Worse off, the grade book program was accessible from any networked machine (thanks Novell)
Thank god this was nearly a decade ago... So, one could pick a random terminal in the school and make subtle changes to their own (or perhaps someone elses) grades.
I used to think "I wish that I was alive during the 80's so that I could have been part of the cracking scene there". In hindsight, I could have done such bad things during the 90's, when I grew up.
Hold on a minute here.
The IT guy blames his boss for installing the Alexa toolbar, which lead to the deletion of all dynamic content on the company's web site.
No it didn't.
Yes, the Alexa toolbar isn't something anybody needs to run, and yes, Alexa should respect robots.txt, but whoever set up their web site is clearly incompetent:
1) Never rely on robots.txt for security.
2) The article says the Alexa spider captured usernames and passwords? What the hell were usernames and passwords doing unprotected on the web site?
3) The Alexa spider clicked all the Delete links. Never ever use links to delete things! Always use a submit button with POST, not GET. Generally, most spiders won't submit POST forms.
Security through obscurity is even less effective when the obscurity is poor.
$x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
$x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
Not as major is the Infoworld examples, but I still to this day sometimes forget to set-up a virtual interface when configuring a cisco router. This little command me more often than I care to admit:
telnet 192.168.1.1
cisco-router$ en
cisco-router$ config t
cisco-router(config)# int g0/1
cisco-router(config-if)# ip address 10.1.1.1 mask 255.255.255.0
Connection Closed
Gaaaaaaaaaaaaaaaaaaaaaaaah!
Database take a dump? No backup of the transaction log? Fear not! With just two easy steps, your life will be back on track:
1. Update Resume`
2. Leave Town!
The game.
I used to work with a guy who did the "useless backup" thing. He set up an automated backup system that encrypted the files to tape. It ran fine for a long while. But when we had a server failure and needed to recover from the backup tapes, he couldn't remember what the decryption password was. All he could do was sit there saying "I remember that it was a good one." I just wanted to smack him...
This guy's the limit!
Ah yes, the Daily WTF: the Penthouse Forum of the IT world.
A company decides to run an internal check to see how many people will respond to a phishing scam. They send out an email to a group looking like the intranet page, "reminding" everyone to submit their username and password for the upcoming upgrade this weeken.
The email is actually an HTML form, but users being users, some of course hit reply instead of filling out the form and hitting submit. Worse yet, some hit "Reply All". Worse yet, some had HTML turned off, so the password wasn't even hidden in HTML source, it was in plain text for all on the list to see.
Yes, testing internally to see how many people are susceptible to phishing attacks is a good thing. However, send it via bcc, so group replies won't have passwords spreading around the company like a bad joke.
Next up, inform some people you are running your test. We have two different security groups, corporate, and the one I'm in. We didn't know about it, and all but shut down corporate security's access to the network. We traced the originating IP to their network, as well as the form submission IP. Since they weren't answering their phones, we didn't have much choice.
I found out because a supposedly "technical" engineer called me saying he had responded to it, and realized some people were replying and he could see other people's passwords. He didn't think there was anything wrong with submitting it, because it looked so real it couldn't be fake.
I used to work in Unix Support for a large multi-national. Had loads of customers ring in with cock ups over the years. Some of them were silly, like a developer with root access typing rogue spaces where they shouldn't be. e.g: "chmod -R me / foobar". Conversations always started like "OMG I own the whole system, HELP!". Others were more obtuse, like a world renowned news reporting organisation who allowed one of their developers to install a very important database in his own account. System management got outsourced to Singapore, he then left the company, so Singapore deleted his account. We were left trying to reconstruct was was left from a dd image copy of the disk.
:-)
Another one I remember (about 20 years ago) was where one customer had systems that would crash at about 10am every monday morning. After a very long trouble shooting experience (i.e. months) the cause was found to be a delivery lorry that arrived every monday morning. He would back up to the loading bay, where some rubber bumpers (fenders) had been installed. He had the habit of stopping the lorry when he banged into the bumpers. Unfortunately this sent a shock wave through the building sufficient to cause some of the disks in the computer room throw a hissy fit and park their heads in the middle of whatever I/O they were doing.
In the early 90's I found myself having to pick up SCO Unix support for my sin's. Thankfully it only lasted 4 years. Two specific customer incidents I remember from that time. One was a call from a hospital who's system seemed in a right state. The guy was panicing, so I cut short my usual trouble shooting routine, got in the car and drove down there. Took one look at the system, typed ^D and then left after it'd finished booting to multi-user. Taught me a lesson; embarrassed the hell out of the customer and I never heard from him again.
The second was more interesting. I had a customer in the MoD at HMS Dolphin in Gosport. A number of their systems would crash simultaneously at certain times during the week. There was no real pattern to when, but when one of them went, they all did. I couldn't find the problem. No common denominators. Power monitors didn't show anything. Nothing. That was until one day the customer was staring out the window when the systems crashed. He remembered seeing one of the warships leaving the harbor and sailing right past his window. He also remembered seeing the ship starting its RADAR as it went past; and as the beam swept the computer room, all the systems crashed. The fix: a snotty email dictating that captains don't start their radar until they've cleared the harbor and made it out to sea.
I could go on typing for another hour straight with stories like this that either I've seen, or have happened to friends/colleagues
One of my co-workers once decided to install a beta version of Windows NT on the company's Novell file server, which EVERYBODY used for EVERYTHING. He did this in the evening when noone would notice and then he left for two weeks' vacation!!! I have never in my entire life met a more arrogant SOB. The entire company was down for over a day as we restored the server from a backup.
The boss refused to fire him (out of a cannon), so we filled the entire volume of his office with computer boxes. We went up and over the drop ceiling to deposit the last few boxes so he could not even open the door. When he returned from vacation, it took him a whole day to figure out how to get the boxes out.
There are people who simply don't know even the basic syntax out there, much less the basic CS notions, and still got hired because they were the cheapest. Sadder still, only a minority of them get fired for gross incompetence.
Seriously, I've seen people who didn't even know what quotes do in Java, pretend they're Java gurus. Literally. One needed an explanation of why Java complains when he writes something like getUserData(John Smith), Java gives him a syntax error.
Another one needed some explaining as to why if he declares a variable in the constructor, it's not visible in another method. Seemed to essentially assume that since the constructor has the same name as the class, that's where you declare class members. Right? Mind you, the whole concept of scope seemed a bit fuzzy to him.
One particularly promising young padawan tried to "fix" a bug by changing every single if in the program from to Actually insisted that the bug was now fixed. 'Cause Java generates different code when you write "== true." Ookaayy.
An inventive guy tried to get around some data objects being invariant (you know, all getters and no setters) by writing basically a method like this: Was genuinely surprised that calling "nuller(someDataObject.getName())" didn't actually set the name to null. Took some explaining to understand that it's not some Java bug, but, really, how it's supposed to work.
An _architect_ made a whole team use the boxed objects (Integer, Character, Boolean) instead of the primitive types (int, char, boolean) in all method calls, as a speed optimization. See, if you have an Integer parameter, Java only copies a pointer, not the whole int. (That was before Java 5 and its automatic boxing and unboxing, too, btw.) Sadder even, nobody in that team had any objections.
And that's just the simple ones, the ones that can be told in one paragraph. There are more, but let's not write a whole tome.
So, really, there are some truly monumentally clueless people out there. And they do random clueless things, until by sheer brute force they arrive at something which survives their testing with a couple of clicks in the GUI. Yay, they solved the problem. (Not.) Give them enough time and lack of interest to actually get a book and learn, and it'll grow into an "experience" of such witch-doctor tricks that worked once, and cargo cult code that tries to look like something they saw once, but they never understood why.
So, well, if you see some code sample that looks like it _must_ be a fabricated story... well, it is at least _possible_ that it's true. And know that someone somewhere probably wrote an even bigger abomination.
A polar bear is a cartesian bear after a coordinate transform.