1995-12-04 - Re: Cracked: WINDOWS.PWL

Header Data

From: Rich Graves <llurch@networking.stanford.edu>
To: Frank Andrew Stevenson <frank@funcom.no>
Message Hash: 5b765c27601ebf1c7e044f446802d208d76d3b8d65c1a8a3cfccf588bf95e8ca
Message ID: <Pine.ULT.3.91.951204113806.16412D-100000@Networking.Stanford.EDU>
Reply To: <Pine.SGI.3.91.951204174641.2847A-100000@odin>
UTC Datetime: 1995-12-04 19:47:53 UTC
Raw Date: Mon, 4 Dec 95 11:47:53 PST

Raw message

From: Rich Graves <llurch@networking.stanford.edu>
Date: Mon, 4 Dec 95 11:47:53 PST
To: Frank Andrew Stevenson <frank@funcom.no>
Subject: Re: Cracked: WINDOWS.PWL
In-Reply-To: <Pine.SGI.3.91.951204174641.2847A-100000@odin>
Message-ID: <Pine.ULT.3.91.951204113806.16412D-100000@Networking.Stanford.EDU>
MIME-Version: 1.0
Content-Type: text/plain


-----BEGIN PGP SIGNED MESSAGE-----

Very interesting.

Do you have information on the content of the various resource records
within a .PWL file? They should be the stored usernames and passwords for
every other authenticated service used by the "user profile."

I.e. the "default login," say, the local Windows password, encrypts the
.PWL file, and the contents are the passwords used for NetWare, NT,
Dial-Up Networking, the screen saver, .PWL-enabled "security" utilities,
etc.

If anyone wants a sample .PWL file including known values of all of the 
above, I can have it for you within a day. Of course I wouldn't want to 
give you any *real* passwords.

Of course I should just compile your code myself, but it's a busy day, 
and I'd hate to unnecessarily duplicate someone else's work...

- -rich
 moderator of the win95netbugs list
 http://www-leland.stanford.edu/~llurch/win95netbugs/faq.html

-----BEGIN PGP SIGNATURE-----
Version: 2.6.2

iQCVAwUBMMNP9Y3DXUbM57SdAQF+1wP/RFHvnjpne9bGsU6K8xxT3UPav2nt+8wR
2CUnY/Dm32bTDegx7QO8zpUVckNR2YwxG5ivZhBnov8UhMcngWdMLPjkdSCepPXP
cvKTTwAVknmxqLXkyuVSn06PGKlNz5RQnluop5s74IJ3nmJPAFnU+/pGWvlZY3cN
jh42jdlo/8s=
=zDbs
-----END PGP SIGNATURE-----





Thread