Orchid XP v8 wrote:
> If you are the manager, you can instruct the system administrators to 
> keep out of your files. Why are we having this discussion again? ;-)

That reminds me of a tip on how to enforce a singleton in C++; that is, 
how to make sure noone instantiates a particular class.  The following 
code will do the trick:

// If you instantiate the following class you WILL BE FIRED!!!
class Singleton {
...

...Chambers

Post a reply to this message

Darren New wrote:
> 
> Plus, I'm pretty sure that if you (say) encrypt files on a USB drive, 
> the actual private key to decrypt the files isn't on the drive itself. 
> Rather, it's only stored on the C: drive on the machine you log in 
> to[1]. So if you encrypt your backups, it's probably pretty secure, and 
> certainly better than nothing.
> 

And if you *need* those backups, 'cause the darn HD of the workstation 
crashed, they are extremely secure? :)

-- 
Eero "Aero" Ahonen
    http://www.zbxt.net
       aer### [at] removethiszbxtnetinvalid

Post a reply to this message

Eero Ahonen wrote:
> So... If we have 4 men, with intelligences 1, 8, 9 and 9, the average is 
> (1+8+9+9)/4=6,75, so 75% of men are more intelligent than average person 
> (who, if he existed, would be over 6 times as intelligent as the dumpest 
> one).

I usually drop the outliers (top and bottom quartiles) first.  That 
would leave us with (8+9)/2=8.5 average, with an even 50% split :)

...Chambers

Post a reply to this message

scott wrote:
>> Very, very few people are capable of coming up with strong passwords 
>> that they can actually remember.
> 
> Especially when some stupid system forces you to change it every month.
> 

This exact policy has led most passwords in the bank I work in to be a 
combination of a random prefix and a numerical postfix.  When it's time 
to change the password, you just increment the postfix, and done.

...Chambers

Post a reply to this message

Chambers wrote:
> 
> This exact policy has led most passwords in the bank I work in to be a 
> combination of a random prefix and a numerical postfix.  When it's time 
> to change the password, you just increment the postfix, and done.

Well done, if the prefixes really are random. Usually they go as 
"monday.1", "monday.2" etc...

> ...Chambers


-- 
Eero "Aero" Ahonen
    http://www.zbxt.net
       aer### [at] removethiszbxtnetinvalid

Post a reply to this message

Chambers wrote:

> // If you instantiate the following class you WILL BE FIRED!!!
> class Singleton {
> ...

...this works in C++? Neat!

-- 
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*

Post a reply to this message

>>>> You do realize that if it's a company machine, he controls the boot
>>>> order.
>>> Yes, but (IIRC) in this part of the discussion it was said that it
>>> would be difficult for the manager of a company to prevent system
>>> administrators to read confidential information.
>>>
>>> If you are the manager, you can instruct system administrators to set
>>> the desired boot order on your PC.
>> If you are the manager, you can instruct the system administrators to
>> keep out of your files. Why are we having this discussion again? ;-)
> 
> Because not all sysadmins follow their manager's instructions.

...which is kind of the point I was making. ;-)

-- 
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*

Post a reply to this message

Jim Henderson wrote:

> What is the current max length of a Windows password?  I know my 20-
> character password had to be cut down to 14 IIRC on WinNT and possibly 
> Win2K - the dumb thing seemed to be that when setting the password, the 
> password got truncated and then hashed, but when checking, it was hashed 
> as is (or vice versa), so if you set your password to a value that was 
> too long, you could never login.

Isn't that cute?

Yes, I ran into this too. I think it varies depending on whether you use 
LANMAN or Kerberos. (So... it's nice and reliable then!)

-- 
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*

Post a reply to this message

"Orchid XP v8" <voi### [at] devnull> wrote in message
news:48712fff$1@news.povray.org...
> >>>> You do realize that if it's a company machine, he controls the boot
> >>>> order.
> >>> Yes, but (IIRC) in this part of the discussion it was said that it
> >>> would be difficult for the manager of a company to prevent system
> >>> administrators to read confidential information.
> >>>
> >>> If you are the manager, you can instruct system administrators to set
> >>> the desired boot order on your PC.
> >> If you are the manager, you can instruct the system administrators to
> >> keep out of your files. Why are we having this discussion again? ;-)
> >
> > Because not all sysadmins follow their manager's instructions.
>
> ...which is kind of the point I was making. ;-)

Yeah, but while it's hard to tell if someone has followed the instruction
"Don't read my files", it's fairly easy to tell if they've followed the
instruction to set the boot order of a particular machine..

Post a reply to this message

Eero Ahonen wrote:
> And if you *need* those backups, 'cause the darn HD of the workstation 
> crashed, they are extremely secure? :)

You put an escrow key on a floppy and lock that up somewhere separate.

Some things could be easier, yes. :-)

-- 
Darren New / San Diego, CA, USA (PST)
  Helpful housekeeping hints:
   Check your feather pillows for holes
    before putting them in the washing machine.

Post a reply to this message