home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!charon.amdahl.com!pacbell.com!mips!sdd.hp.com!usc!rpi!uwm.edu!bionet!ucselx!gdwest!good
- From: good@gdwest.gd.com (David L. Good)
- Newsgroups: comp.sys.hp
- Subject: Re: HP 9000/370, no root password!
- Message-ID: <1992Aug19.152522.2758@gdwest.gd.com>
- Date: 19 Aug 92 15:25:22 GMT
- References: <1992Aug15.022529.7176@mccc.edu> <1992Aug18.064054.8484@nessie.mcc.ac.uk>
- Organization: General Dynamics Corp.
- Lines: 26
-
- In article <1992Aug18.064054.8484@nessie.mcc.ac.uk> LeBlanc@mcc.ac.uk writes:
- >In article <1992Aug15.022529.7176@mccc.edu> pjh@mccc.edu (P. J. Holsberg) writes:
- >>A neighboring university has asked to donate to us a couple of
- >>HP9000/370 workstations, but the root password is not known.
- >>
- >>If we accept these, what can be done to gain superuser status?
- >
- >I've never done this with a 370, but on 340's you can easily
- >interrupt the boot sequence while fsck is being performed and
- >get root privileges. An fsck will be performed if the system is
- >switched off without using reboot or shutdown: do a sync first,
- >if you can, to minimise damage.
- >
- >Once you have root privileges, you can edit /etc/passwd and reboot.
- >
-
- That's certainly an interesting "feature". Is there any way to prevent
- this from occuring? We have a network of ~60 350s, and I'd hate to have
- users be able to be superuser anytime they want just by cycling power on
- a workstation!
-
-
- --
- David Good good@gdwest.gd.com
-
- This space intentionally left blank.
-