>
> The last time this came around, I believe it was discovered that
> setting the cryptall flag wasn't enough, because of other brokenness
> in the AFS client.
>
> Ah, I found the email on this subject! Chaskiel M Grundman
> <[EMAIL PROTECTED]> pointed out to me that modifying cryptall
> _also_ changes the security index passed to the remote server to
> 3, which is invalid (it should be 2).
Is this something you can do on some specific clients (e.g., ones that are
running on a "really insecure" network, as opposed to our otherwise
"insecure" net), yet still have non-cryptall clients work as usual? Does
trying to set this up cause the fileserver to only accept fully encrypted
rx connections, or does it allow the client to choose what it wants?
Robert Banz ([EMAIL PROTECTED])
UMBC University Computing
(410) 455-3933 fax: (410) 455-1065
