The Unix Heritage Society mailing list
 help / color / Atom feed
From: Royce Williams <royce@techsolvency.com>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Recovered /etc/passwd files
Date: Fri, 18 Oct 2019 07:01:12 -0800
Message-ID: <CA+E3k90Z2kxk89tdPqha=2q82MxEbVsAwN24SRCEZ1+nwHxERw@mail.gmail.com> (raw)
In-Reply-To: <90ffe509-76b5-6629-c55a-7785815fda2e@kilonet.net>

[-- Attachment #1: Type: text/plain, Size: 1744 bytes --]

On Fri, Oct 18, 2019 at 6:35 AM Arthur Krewat <krewat@kilonet.net> wrote:

> This has been solved.
>
> First attempted was a full 8-character upper/lower/numeric brute force
> which took over 6 days and failed.
>
> Second attempt was lower-case with control characters, and succeeded in
> around 40 minutes.
>
> There's a control character in it ;)
>

I'd long suspected that someone would have done this; it would be a great
way to expand the total keyspace, and extend the life of

But given Ken's seminal work in password stretching and keyspace analysis,
I always suspected that it was ken, not bill.

in 2015, I was intrigued by the idea that he'd left a little puzzle in a
hash that he knew would be publicly available. I even went so far as to
construct a small FPGA cluster in pursuit of that theory:

https://www.techsolvency.com/passwords/ztex/

What original caught my attention was the logic behind enforcing password
quality in passwd.c during a specific era of BSD code, which exited
ambiguously in a double negative of sorts, where control characters were
not disallowed during password entry. (I'll try to dig up the source.)

Anyway, I must have made an error in my original work in 2015, in which I
found both of ken's:

https://twitter.com/TychoTithonus/status/1182181560264491008

... but managed to miss bill's entirely, thinking that it had already been
cracked. In the superset of all CSRG-published distros, there are slightly
more than 1400 total hashes, and one of bill's appears to have been lost in
the shuffle (the other was trivial).

So some hearty (and bittersweet!) kudos for solving this puzzle! It is what
drove me into password auditing as a passion (and profession).

Royce

--
Royce Williams
Tech Solvency

[-- Attachment #2: Type: text/html, Size: 2489 bytes --]

<div dir="ltr"><div dir="ltr">On Fri, Oct 18, 2019 at 6:35 AM Arthur Krewat &lt;<a href="mailto:krewat@kilonet.net">krewat@kilonet.net</a>&gt; wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">This has been solved.<br>
<br>
First attempted was a full 8-character upper/lower/numeric brute force <br>
which took over 6 days and failed.<br>
<br>
Second attempt was lower-case with control characters, and succeeded in <br>
around 40 minutes.<br>
<br>
There&#39;s a control character in it ;)<br></blockquote><div><br></div><div>I&#39;d long suspected that someone would have done this; it would be a great way to expand the total keyspace, and extend the life of</div><div><br></div><div>But given Ken&#39;s seminal work in password stretching and keyspace analysis, I always suspected that it was ken, not bill. </div><div><br></div><div>in 2015, I was intrigued by the idea that he&#39;d left a little puzzle in a hash that he knew would be publicly available. I even went so far as to construct a small FPGA cluster in pursuit of that theory:</div><div><br></div><div><a href="https://www.techsolvency.com/passwords/ztex/">https://www.techsolvency.com/passwords/ztex/</a><br></div><div><br></div><div>What original caught my attention was the logic behind enforcing password quality in passwd.c during a specific era of BSD code, which exited ambiguously in a double negative of sorts, where control characters were not disallowed during password entry. (I&#39;ll try to dig up the source.)</div><div><br></div><div>Anyway, I must have made an error in my original work in 2015, in which I found both of ken&#39;s:</div><div><br></div><div><a href="https://twitter.com/TychoTithonus/status/1182181560264491008">https://twitter.com/TychoTithonus/status/1182181560264491008</a><br></div><div><br></div><div>... but managed to miss bill&#39;s entirely, thinking that it had already been cracked. In the superset of all CSRG-published distros, there are slightly more than 1400 total hashes, and one of bill&#39;s appears to have been lost in the shuffle (the other was trivial).</div><div><br></div><div>So some hearty (and bittersweet!) kudos for solving this puzzle! It is what drove me into password auditing as a passion (and profession).</div><div><br></div><div>Royce</div><div><br></div><div>--</div><div>Royce Williams</div><div>Tech Solvency</div></div></div>

  reply index

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2019-10-19 13:45 Norman Wilson
2019-10-19 20:27 ` ewe2
2019-10-19 20:41   ` Arthur Krewat
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
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

Reply instructions:

You may reply publically 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='CA+E3k90Z2kxk89tdPqha=2q82MxEbVsAwN24SRCEZ1+nwHxERw@mail.gmail.com' \
    --to=royce@techsolvency.com \
    --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

The Unix Heritage Society mailing list

Archives are clonable: git clone --mirror http://inbox.vuxu.org/tuhs

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://inbox.vuxu.org/vuxu.archive.tuhs


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git