Jim Henderson wrote:
> On Thu, 26 Feb 2009 23:21:01 +0100, Fredrik Eriksson wrote:
> 
>> On Thu, 26 Feb 2009 22:37:20 +0100, Orchid XP v8 <voi### [at] devnull> wrote:
>>>>> No. They have all the master passwords; I don't even know what those
>>>>> are. So they can lock me out, but not the reverse.
>>>>  If you have the passwords for the routers, then you have the
>>>> passwords. :-)
>>> But I *don't* have the passwords for the routers.
>> If you have physical access to the routers, then you make the passwords.
>>
>>
>>>> Seriously. You should write up what's going on and send it to your
>>>> boss, his boss, and so on up the line. Explain they're crashing your
>>>> systems and you have no control over it, and ask them what the
>>>> appropriate procedure should be for violation of procedures.
>>> Nobody will care. If I say "they did X, which caused a problem",
>>> everybody will assume I don't know what I'm talking about.
>> It does not matter what they assume or even what they choose to do about
>> it. What matters is creating a paper trail to cover your own ass.
> 
> Exactly what I was going to say.
> 
> Andy, write the damn paper trail already!
> 
> Jim


he has - it's right here... too bad it isn't anything official.

Post a reply to this message

On Fri, 27 Feb 2009 09:36:53 -0500, Tom Austin wrote:

> Jim Henderson wrote:
>> On Thu, 26 Feb 2009 23:21:01 +0100, Fredrik Eriksson wrote:
>> 
>>> On Thu, 26 Feb 2009 22:37:20 +0100, Orchid XP v8 <voi### [at] devnull>
>>> wrote:
>>>>>> No. They have all the master passwords; I don't even know what
>>>>>> those are. So they can lock me out, but not the reverse.
>>>>>  If you have the passwords for the routers, then you have the
>>>>> passwords. :-)
>>>> But I *don't* have the passwords for the routers.
>>> If you have physical access to the routers, then you make the
>>> passwords.
>>>
>>>
>>>>> Seriously. You should write up what's going on and send it to your
>>>>> boss, his boss, and so on up the line. Explain they're crashing your
>>>>> systems and you have no control over it, and ask them what the
>>>>> appropriate procedure should be for violation of procedures.
>>>> Nobody will care. If I say "they did X, which caused a problem",
>>>> everybody will assume I don't know what I'm talking about.
>>> It does not matter what they assume or even what they choose to do
>>> about it. What matters is creating a paper trail to cover your own
>>> ass.
>> 
>> Exactly what I was going to say.
>> 
>> Andy, write the damn paper trail already!
>> 
>> Jim
> 
> 
> he has - it's right here... too bad it isn't anything official.

Yeah, that would make it a bit difficult to use in court.  "Yes, I'm 
'Invisible', and 'Orchid XP v3', m'lud."

Jim

Post a reply to this message

Invisible wrote:
>>> Option #1 is clearly unsatisfactory, and option #2 is likely to get
>>> me yelled at. I love my job...
>>
>> Make your boss earn his money. Ask for an executive decision.
> 
> You're talking about a man who has a packet of sunflower seeds next to
> his desk. (I'm not making this up.) Can you spell "bird brain"?
> 
> In fact, I take that back. It would be an insult to the birds...
> 
> I think my plan of action is to not actually *do* anything at this
> point, just ask IT why this was done.

Don't care about that, just send him an email explaining this all,
writing it as easy and self-explaining to read as possible. Make him do
the decision - you can tell him your opinion, but make sure it's his
call to decide. If you ask from him, you're doing it right, making sure
you're not violating (new) company policies yourself. And do it via
email to make sure it's written down, not just spoken.

Follow these two steps and you are fine:
Step 1: save your own ass properly
Step 2: be profitable for the company

-Aero

Post a reply to this message