Re: Passwords
I had something similar in a school.
I worked as a kind of roving technician/consultant for schools and ended up with dozens of them, working one each day or half-day every week.
Eventually, after many years, one loved me so much that they outbid all the other schools to have me full time (it is no exaggeration to say that they had to argue with a London Borough HR/Finance department in order to create a brand new payscale for the desired salary because no such payscale at that level existed at the time for support staff, and there were major ructions over it - until I witnessed the head basically say loudly and clearly down a phone line something along the lines of "I'm the head, you're just the Borough team in place to support me. I'm choosing to hire him, I don't see what that has to do with you and your systems being unable to cope with that, just resolve this"... I was put under NDA and apparently in that Borough was the only support staff on a special, unadvertised payscale that nobody else had... Anyway...).
I worked for them for a while but then the school changed and they employed lots of very daft teaching staff who didn't understand IT (and one who was given the title of IT Coordinator - which is basically the person on teaching staff who interfaces with the actual technical IT manager, etc. - who then tried to tell me my job while knowing absolutely nothing) and things began to get silly.
So I walked. It was a shame, but there you go. One of the governors was an IT guy in the city and we agreed it would be best if I handed over to him - at least in terms of knowledge - and then they could pass on anything to the next guy they found. So that's what I did, I made a CD-R with all the documentation of the network, and handed copies over officially to the head and to this governor.
A few months later, I was in another job. I got a phone call from that school. It was the IT Coordinator guy. He *demanded* the main network administration password. Never gonna happen. It lets you see salaries and HR notes and the like and there was no need for it (this was back when things were divided into "curriculum" and "admin" networks and he basically wanted the master passwords to everything). He was adamant and kept pushing and got quite angry on the phone.
I asked why he needed it.
Flashback 6 months prior when he'd just started. He demanded - without prior consultation, authorisation or notification - that the school must buy a bunch of portable MP3 recorders. Absolutely vital. Critical. More important than everything else on the entire network that was running the school. I refused to authorise it (not really my place to authorise academic IT anyway, but it wasn't coming out of my budget for sure, so he'd have to convince the head, not me). He got really quite shirty about it.
A month later, he comes to me grinning with a cardboard box full of brand-new "MP3" recorders. Smug as hell. I mean, I was expecting that, mate. It's not smug to have convinced the school to do exactly what I told you you would need to do. He demanded I make them work on the network computers. Yeah, I don't think you understand how they work because they have nothing to do with the computer, really, they just record the audio and then act like a storage device. But, yeah, sure. I take the box.
He then asked me for the administrator password. We don't give that out to teaching staff, no. He got shirty again. I asked why he needed it. Apparently he had bought, without authorisation again, a piece of software for the kids to bring in the audio and edit and save it. Okay. I mean, I don't know why you think you need the administrator password (I'll install it, thanks, it's my job) or why you had to go behind people's backs to buy that stuff (and I wouldn't have bought that software and was explaining why when he just stopped me mid-track and told me to "just do it" and walked off).
So I installed the software across the network (cue this massive all-staff email from him boasting about his new project and how everyone should start using it, etc.), and I tested one of the recorders. It did exactly what it was designed to do. So I authorised them and gave them back to him.
The first lesson with them, he came storming in. Turns out the "MP3" recorders only recorded in WMA copy-protected format. I mean, it literally said that on the box and the website description. And the software only accepted MP3 files. I mean, it's the kind of thing an IT manager would check before allowing you to purchase them and authorising such a purchase, but I was cut out of the loop on that one. He demanded that I fix it. Nope. He insisted that I give him the administrator password. Nope. Somehow he believed that would magically fix these things that ONLY recorded WMA and the software that ONLY opened MP3. Ensue a massive several-week-long argument between me and him about it.
In the end, I went as far as I was prepared to go (being the only IT guy on very good hourly rates, I was both extremely busy with actually important stuff, and not willing to waste my time on trivia like that, and the head was generally in agreement). I made a network folder. Any WMA saved in there would trigger some software I wrote, which would convert the audio to MP3 and a minute later it would magically appear in another folder on the network as an MP3. Literally Save it here from the recorder, then by the time you open the software, you can open it from over there in the right format.
Not. Good. Enough. I was told quite clearly, several times, loudly, by this guy.
I was months into having had enough of him (and he was one reason I left), so my support for this project ended there and I wasn't interested in the fuss he continued to make.
So now fast-forward to when I've left that school, am working elsewhere, and I'm being disturbed at my new employer by a long ranty phone call demanding the network administrator password. To get his MP3/WMA software magically talking to each other without having to save it in between (he just wanted the MP3 software to "see" the recorder and pick up the WMA's that it couldn't open, automatically). I told him no. He got extremely irate. I explained (again) that it wouldn't do anything, but also that I was absolutely not going to give him any password - I didn't work there any longer, it wasn't my responsibility and no way was I going to compromise the system.
He then insisted that the head at that school had ordered that I give him that password and that nobody knew it so the school must have it, and he'd been chosen to be the custodian of it. Highly doubtful, I knew that head and he's the one who'd championed my salary - he'd just call me if that was the case. I called him out on the lie. I said he'd have to ask the head for authorisation and I'd have to hear it from him, because I don't believe he'd authorised it. He screamed at me down the phone for some time and demanded how I "would ever possibly know" what the head had ordered or not.
"Well... for one, he already has that password. It was in my handover that he signed off on. For two, the governor also has a copy of that password, just to ensure that someone had it somewhere else. And three... the reason that you don't know this is that it was explicitly discussed on handover and I was told to never give *you* any access or password ever."
The governor, being an IT guy, had understood the "problem" with the MP3/WMA thing immediately and I'd warned him on handover. He was the one who said "Under no circumstances give him that password", and the head was present and agreed. We handed over knowing that it was never going to work, and that he was never going to be party to the privileged details because he just didn't know what he was talking about.
So the big long phone call which he'd made without the school's knowledge, to demand the network administrator's password, to get his embarrassing pet project that had never truly worked the way he intended to work properly, and claiming that the head had authorised it? I can only imagine that got him into big trouble. But he didn't get the password from me.
I checked the school website and their staff list about a year or so later - he was gone.