[580] in Info-AFS_Redistribution

home help back first fref pref prev next nref lref last post

Re: Changing cell names

daemon@ATHENA.MIT.EDU (Jeanette_Dravk@transarc.com)
Thu Feb 6 10:01:43 1992

Date: Thu,  6 Feb 1992 08:40:40 -0500 (EST)
From: Jeanette_Dravk@transarc.com
To: Info-AFS@transarc.com, d3f082@maddog.pnl.gov,
Cc: ta_harper@pnlg.pnl.gov
In-Reply-To: <odYCpsO14C78I3I0py@hatti5.cs.chalmers.se>


Christer Bernerus asks:

>>  Change the cell name in ThisCell and CellServDB on every machine in the cell.
>>    -you can do an 'fs newcell' to avoid rebooting the machines.

But if you only do this, the cache mgrs will still recognize the old
name ... Beware!

This is true.  Not everyone has the option of booting all their clients
right away though, so for some this can be a temporary stop-gap fix until
the next scheduled reboot.  It's not without it's drawbacks.


>>  Change every user's password in the database so that it is encrypted (and
>>  can thereafter be decrypted) properly.

>Do you by this mean that I as a System admin can change the encrypted
>passwords or do I need the cooperation of all my users ?

An administrator can always change a user's password using 'kas setpassword'.
This will change the old password to the new password, encrypt it, and store it
in the Authentication Database.

This is not the same as reading an encrypted password.  There is no way for
you, as an administrator, to decrypt a user's password.


>Why is the encryption key so tightly coupled to the cell name ?

Combining the cellname with the password means the same password in two
different cells will result in different keys in the different cells.


Jeanette Dravk-
Product Support, Transarc Corporation



home help back first fref pref prev next nref lref last post