SUMMARY: secsetup *still* breaks "su" notification in 3.2D-1!

From: Pat Wilson <paw_at_phibes.dartmouth.edu>
Date: Tue, 06 Aug 1996 09:32:17 +22306356

I wrote:

        After applying the "leap year" patch to a 3.2a system with C2 security, the
        "su" logs don't report _which_ user su'd:

        before: Aug 2 09:44:56 paw-test su: SU paw on /dev/ttyp0
        after: Aug 2 10:35:03 paw-test su: SU root on /dev/ttyp0

        I'm now seeing this same problem on a (new) 3.2D-1 system on which I've
        just invoked C2 (via the 'secsetup; reboot' process). We traced this to
        strangeness in the libc.a from OSF320-214 - is this fixed yet?

Many thanks to Sheila H. Franklin <sfrankl%unode2_at_relay.nswc.navy.mil>

who directed me to patch OSF360-350154 (now superceded by OSF360-350222),
which fixes the problem.

Pat Wilson
paw_at_dartmouth.edu
Received on Tue Dec 17 1996 - 17:43:19 NZDT

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:47 NZDT