...

Sep. 11th, 2008 10:52 am
[identity profile] toxico.livejournal.com posting in [community profile] techrecovery
Wow, people sure do get bitchy when you don't just arbitrarily give them a password simply because they asked.

"We're trying to install some security cameras, and the port over which the feed is broadcast is being blocked by this application. What's the password to unlock the interface so I can edit the policies?"
"How do you know it's that application doing it?"
"It's in the log file."
"Okay, fair enough. Can you send that to me?"
"What?! Can't you just give it to me?"
"Only after you show me the log file."
"This is ridiculous grumble bitch mumble inefficient blah."

~45 seconds of verbal diarrhea later~

"Yup, there it is! Here's the password."


See, was that so HARD?! Douche.

Date: 2008-09-11 04:50 pm (UTC)
From: [identity profile] tallanvor.livejournal.com
Well, either they're the ones who are supposed to be editing the policies and therefore should have the password, or someone else should be making the changes... So, in this case, I can understand why they'd be a bit annoyed.

Date: 2008-09-11 05:06 pm (UTC)
From: [identity profile] tallanvor.livejournal.com
Then it sounds like management is doing something wrong...

Either they're not supposed to have the passwords and someone at your location is supposed to make the changes no matter how much the people at that location complain about it, or they're allowed to manage things themselves, in which case they should have the access they need.

I like the policy I work under. When customers call in with a problem, we can answer questions, and get log files/configuration information so that we can replicate the problem and come up with a solution, but we're never supposed to go in and make changes on their systems ourselves. That way we can never get blamed for breaking anything.

Date: 2008-09-11 05:41 pm (UTC)
From: [identity profile] tallanvor.livejournal.com
Now come on, there's no reason to be an ass just because we disagree. --Save that for the idiots who post here asking for help without reading the community info!

And I never said there was something wrong with a hands-on approach, especially if that's what you're paid to do. --Just that the particular policy you described doesn't make sense to me.

Date: 2008-09-11 04:58 pm (UTC)
From: [identity profile] amynnah.livejournal.com
I understand that...

We get people calling on behalf of other people, and they throw OMG hissy-fits when we can't change the password on their say-so for this other person. Reason being? HIPAA (Health Information Privacy Act). This policy has been in place a couple years, and people still try to push it. If we cannot speak to (and verify) that the person indeed needs their password reset, we can get in metric fucktons of trouble.

That sounds rough... :( And some people don't seem to understand policies which are in place for a valid reason.

Date: 2008-09-11 06:42 pm (UTC)
From: [identity profile] ace-brickman.livejournal.com
secretaries have the hardest time with that

"B-B-B-But he's in a meeeeeeeeeeeeeeeeting!"

that's why we're a 24-hour support line, bia.. now get him on the phone or STFU

Date: 2008-09-12 05:29 am (UTC)
jecook: (Default)
From: [personal profile] jecook
We are slightly more lax then that around my place- if a supervisor calls in for an subordinate's password reset (which happens more frequently then I'm willing to admit) we can (and usually do) tell them the temporary or default password, which is a "you've logged in, please change your password NOW" affair.

But one supervisor asking for, say their bosses password? there are exactly two people that can get away with that at my place- the admin assistants to the executive team, and the execs generally call it in themselves anyhow.

Date: 2008-09-11 05:15 pm (UTC)
From: [identity profile] grayhawkfh.livejournal.com
Heh. Federal Gov't Agency: We may NOT change passwords until you prove you are who you say you are.

Read: We need photo ID. Preferably the one the agency issued you.

Don't like it? Tough.

Date: 2008-09-11 05:28 pm (UTC)
From: [identity profile] sdaemon.livejournal.com
Why, how dare you take reasonable steps to avoid being caught in a social engineering scam!

Date: 2008-09-12 04:39 am (UTC)

Profile

techrecovery: (Default)
Elitist Computer Nerd Posse

April 2017

S M T W T F S
      1
2345678
91011121314 15
16171819202122
23242526272829
30      

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Mar. 20th, 2026 07:00 pm
Powered by Dreamwidth Studios