From: Arthur Krewat <krewat@kilonet.net>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Recovered /etc/passwd files
Date: Tue, 8 Oct 2019 13:38:42 -0400 [thread overview]
Message-ID: <b2905a0a-62ff-1e76-f8c1-427ec25af7f4@kilonet.net> (raw)
In-Reply-To: <20191005180503.GA31679@tom-desk.erg.abdn.ac.uk>
[-- Attachment #1: Type: text/plain, Size: 2765 bytes --]
I have some more out of this list, but not sure if I should send them or
not. Ken's has not been cracked - yet.
ozalp:m5syt3.lB5LAE:40:10:& Babaoglu,4156423806:/usr/ozalp:/bin/csh
hpk:9ycwM8mmmcp4Q:9:10:Howard Katseff,2019495337:/usr/staff/hpk:/bin/csh
tbl:cBWEbG59spEmM:10:10:Tom London,2019492006:/usr/staff/tbl
ken:ZghOT0eRm4U9s:52:10:& Thompson:/usr/staff/ken
fabry:d9B17PTU2RTlM:305:10:Bob &,4156422714:/usr/staff/fabry:/bin/csh
On 10/5/2019 2:05 PM, Tom Jones wrote:
> On Thu, Oct 03, 2019 at 09:30:31PM +0200, Leah Neukirchen wrote:
>> Finn O'Leary <finnoleary@inventati.org> writes:
>>
>>> Hi, I remember that someone had recovered some ancient /etc/passwd files
>>> and had decrypted(?) them, and I remember reading that either ken or
>>> dmr's
>>> password was something interesting like './,..,/' (it was entirely
>>> punctuation characters, was around three different characters in
>>> total, and
>>> was pretty damn short). I've tried to find this since, as a friend was
>>> interested in it, and I cannot for the life of me find it!
>> I did this once, but I never managed to crack all of them.
>> It was bwk who used /.,/.,
>>
>> My findings (from https://github.com/dspinellis/unix-history-repo/blob/BSD-3-Snapshot-Development/etc/passwd):
>>
>> gfVwhuAMF0Trw:dmac
>> Pb1AmSpsVPG0Y:uio
>> ymVglQZjbWYDE:/.,/.,
>> c8UdIntIZCUIA:bourne
>> AAZk9Aj5/Ue0E:foobar
>> E9i8fWghn1p/I:apr1744
>> IIVxQSvq1V9R2:axolotl
>> 9EZLtSYjeEABE:network
>> P0CHBwE/mB51k:whatnot
>> Nc3IkFJyW2u7E:...hello
>> olqH1vDqH38aw:sacristy
>> 9ULn5cWTc0b9E:sherril.
>> N33.MCNcTh5Qw:uucpuucp
>> FH83PFo4z55cU:wendy!!!
>> OVCPatZ8RFmFY:cowperso
>> X.ZNnZrciWauE:5%ghj
>> IL2bmGECQJgbk:pdq;dq
>> 4BkcEieEtjWXI:jilland1
>> 8PYh/dUBQT9Ss:theik!!!
>> lj1vXnxTAPnDc:sn74193n
>>
>> But I never managed to crack ken's password with the hash
>> ZghOT0eRm4U9s, and I think I enumerated the whole
>> 8 letter lowercase + special symbols key space.
>>
>> The uncracked ones are:
>>
>> ozalp:m5syt3.lB5LAE:40:10:& Babaoglu,4156423806:/usr/ozalp:/bin/csh
> m5syt3.lB5LAE:12ucdort
>
>> hpk:9ycwM8mmmcp4Q:9:10:Howard Katseff,2019495337:/usr/staff/hpk:/bin/csh
>> tbl:cBWEbG59spEmM:10:10:Tom London,2019492006:/usr/staff/tbl
>> ken:ZghOT0eRm4U9s:52:10:& Thompson:/usr/staff/ken
>> fabry:d9B17PTU2RTlM:305:10:Bob &,4156422714:/usr/staff/fabry:/bin/csh
> I pointed my FreeBSD build machine at the password file, but it didn't
> manage many guesses a second (55000 per core with 48 cores, using john).
>
> I asked a friend to point their GPU rig at the password file. It is a
> MSI Graphics Card R9 290X and is doing about 255MHashes/Second using
> hashcat. He is going to do the alphanumeric space and then call it a
> day.
>
> "for hashcat, 80s DES crypt is -m 1500"
>
> - [tj]
>
[-- Attachment #2: Type: text/html, Size: 38990 bytes --]
next prev parent reply other threads:[~2019-10-08 17:39 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-03 18:51 Finn O'Leary
2019-10-03 19:30 ` Leah Neukirchen
2019-10-03 20:41 ` Finn O'Leary
2019-10-03 22:04 ` Steffen Nurpmeso
2019-10-03 23:24 ` Dave Horsfall
2019-10-04 0:59 ` WIlliam Cheswick
2019-10-04 16:08 ` Arthur Krewat
2019-10-04 10:29 ` Leah Neukirchen
2019-10-04 15:05 ` Ken Thompson via TUHS
2019-10-05 18:05 ` Tom Jones
2019-10-08 17:38 ` Arthur Krewat [this message]
2019-10-08 20:40 ` Dave Horsfall
2019-10-08 20:57 ` Arthur Krewat
2019-10-09 12:55 ` Leah Neukirchen
2019-10-09 16:17 ` Arthur Krewat
2019-10-05 17:29 ` Michael Kjörling
2019-10-05 17:49 ` Arthur Krewat
2019-10-08 18:38 Norman Wilson
2019-10-08 18:51 ` Arthur Krewat
2019-10-08 21:02 ` Dave Horsfall
2019-10-08 21:22 ` Arthur Krewat
2019-10-09 5:49 ` Nigel Williams
2019-10-09 5:52 ` Nigel Williams
2019-10-09 6:00 ` Warner Losh
2019-10-09 8:16 ` Andy Kosela
2019-10-09 8:53 ` Ken Thompson via TUHS
2019-10-09 9:16 ` Leah Neukirchen
2019-10-09 23:04 ` Dave Horsfall
2019-10-10 6:31 ` Vincenzo Nicosia
2019-10-09 19:59 ` Rob Pike
2019-10-09 20:09 ` Kurt H Maier
2019-10-09 21:05 ` Bakul Shah
2019-10-09 21:09 ` Warner Losh
2019-10-09 21:16 ` Arthur Krewat
2019-10-09 22:05 ` Adam Thornton
2019-10-09 23:28 ` Steffen Nurpmeso
2019-10-11 12:28 ` Anthony Martin
2019-10-09 20:14 ` Arthur Krewat
2019-10-10 20:24 ` Clem Cole
2019-10-10 20:38 ` Nemo
2019-10-10 20:52 ` John P. Linderman
2019-10-11 6:24 ` Dave Horsfall
2019-10-11 11:09 ` William Pechter
2019-10-11 23:46 ` Finn O'Leary
2019-10-12 0:21 ` Arthur Krewat
2019-10-10 8:21 ` Dan Cross
2019-10-10 11:58 ` Arthur Krewat
2019-10-10 12:07 ` Leah Neukirchen
2019-10-18 14:34 ` Arthur Krewat
2019-10-18 15:01 ` Royce Williams
2019-10-18 15:05 ` Royce Williams
2019-10-18 18:32 ` Royce Williams
2019-10-19 13:11 ` John P. Linderman
2019-10-10 13:57 ` Henry Bent
2019-10-10 14:05 ` Arthur Krewat
2019-10-15 16:32 ` Michael Kjörling
2019-10-10 14:10 ` Leah Neukirchen
2019-10-11 2:49 ` Dave Horsfall
2019-10-08 20:52 ` Dave Horsfall
2019-10-08 21:15 ` Michael Kjörling
2019-10-19 13:45 Norman Wilson
2019-10-19 20:27 ` ewe2
2019-10-19 20:41 ` Arthur Krewat
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b2905a0a-62ff-1e76-f8c1-427ec25af7f4@kilonet.net \
--to=krewat@kilonet.net \
--cc=tuhs@minnie.tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).