Minifridge

Dialup Jon Norstog thursday at allidaho.com
Tue Aug 24 14:17:26 UTC 2010


MaGill!

Thanks! That's how I did it  on that 3000/600, IIRC, - set the password to
null in single user mode, got in as root and was able to rummage all around
the machine.  And copy all the precious data to a fresh hard drive.

jn


---------- Original Message -----------
From: "William H. Magill" <magill at mcgillsociety.org>
To: Linux on Alpha processors <axp-list at redhat.com>
Cc: Dialup Jon Norstog <thursday at allidaho.com>
Sent: Mon, 23 Aug 2010 23:04:04 -0400
Subject: Re: Minifridge

> Don't know if this will post to the whole list... I seem to remember 
> having problems posting before.
> 
> Here's a bunch of stuff form my C2 (Enhanced Security) Tru64 5.1A system.
> 
> A 4.0 system is not too different as I recall.
> 
> 1- Krnel is either "genvmunix"  (not customized) or "vmunix" 
> (configured).
> 
> 2- I believe the default in 5.x was to configure for a cluster... 
> this means that most all variable files are found in 	 /cluster/members/{memb}/
> 	 /cluster/members/member0/
> 
> 3- the Trusted Computing Base for C2 is
> 
> 	/tcb/
> 
> 	/tcb/files/auth.db  -- for uids less than 100 (default)
> 	/var/tcb/flies/auth.db  for uids greater than or equal to 100 
> (default)
> 
> 	/tcb/bin/edauth
> 
> 4- the protected password authentication database (man prpasswd)  
> entries must exist in both /etc/passwd and /tcb/files/auth.db
> 
> 5- a typical auth.db entry (as viewed via edauth) [from the man page]
> 
>  perry:u_name=perry:u_id#101:\
>                :u_pwd=aZXtu1kmSpEzm:\
>                :u_minchg#0:u_succhg#653793862:u_unsucchg#622581606:u_nullpw:\
>                :u_suclog#671996425:u_suctty=tty1:\
>                :u_unsuclog#660768767:u_unsuctty=tty1:\
>                :u_maxtries#3:chkent:
> 
>   This protected password database entry is for the user perry.  The 
> user ID  for perry is 101.  This value must match the /etc/passwd 
> entry for this  user.  The account has a password and its encrypted 
> form is specified by  the u_pwd field.
> 
>   The database entry specifies a minimum password change time of 0,
>  indicat-  ing that the password can be changed at any time. 
>  Furthermore, the account  is permitted to have a null password. 
>  The account has a maximum consecu-  tive unsuccessful login 
> threshold of 3, indicating that the account is  locked after three 
> failed attempts.  The remaining fields provide account  information 
> such as the last successful and unsuccessful password change  times 
> as well as the last successful and unsuccessful login times and ter- 
>  minal names.
> 
> BTW: on a 4/233 to open the case... it slides back about 1/4 inch, 
> then you pivot it upwards from the rear. The entire top and two 
> sides come off together.
> 
> T.T.F.N.
> William H. Magill
> # Flat-panel iMac (2.1) [800MHz - Super Drive - 768 Meg] OS X 10.4.11 
> # iMac6,1 Core 2 Duo [2.16GHz - 3 GB 667] OS X 10.6.4
> # MacBook Pro4.1 Core 2 Duo [2.5GHz - 4GB 667] OS X 10.6.4
> # Mac mini Core Duo [1.66 Ghz - 2 GB 667]OS X 10.6.4
> # PWS433a [Alpha 21164 Rev 7.2 (EV56)- 64 Meg] Tru64 5.1a 
> # XP1000 [Alpha 21264-3 (EV6) - 256 meg] FreeBSD 5.3
> # XP1000 [Alpha 21264-A (EV6-7) - 256 meg] FreeBSD 5.3
> magill at mcgillsociety.org
> magill at mac.com
> whmagill at gmail.com
> 
> _______________________________________________
> axp-list mailing list
> axp-list at redhat.com
> https://www.redhat.com/mailman/listinfo/axp-list
> 
> -- 
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
------- End of Original Message -------




More information about the axp-list mailing list