Problem
I did an upgrade of our development system from OSF 3.2B to 3.2G (via
3.2C as required). During the B to C upgrade it creates a new
/sys/conf/"node" file and saves the old. What it doesn't do is save the
C2 security option we were using, and appears to rebuild the kernel
without it and then (shutdown -r) re-boot without giving the opportunity
to add it in. This seems to send security back to BASE level. When I then
tried to toggle it back to enhanced (after adding to option back in), the
users found that if their passwords were greater than 8 characters they
had to type only the first 8 characters (thus causing me extra work to
unlock those users who had not realised!).
Is there any way to avoid all of this ?
Received on Thu Nov 07 1996 - 17:13:25 NZDT