The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: arrigo@alchemistowl.org (Arrigo Triulzi)
Subject: [TUHS] History of exploits - request for authors
Date: Fri, 29 Dec 2017 12:22:52 +0100	[thread overview]
Message-ID: <45CBBAF3-CE6D-4DA5-B685-E78CEE6674C1@alchemistowl.org> (raw)
In-Reply-To: <20171219201721.GA95741@accordion.employees.org>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1408 bytes --]

On 19 Dec 2017, at 21:17, Derek Fawcus <dfawcus+lists-tuhs at employees.org> wrote:
> 
> On Tue, Dec 19, 2017 at 12:08:21PM +1100, Dave Horsfall wrote:
>> 
>>     Leaving a "login" simulator on a terminal (quite common).
> 
> Well if you include that one, you may want to include the simple
> brute force testing of passwords against /etc/passwd
> (before shadow files existed). The login name and real names
> (direct or reversed) would tend to get at least one hit.

Well, we all ran Alec’s crack for fun & profit (and some to land themselves in trouble)… I think that doesn’t really qualify as a hack per-se, just a technique which used to work easily and now requires a little bit more computing power (OK, a lot more as the hashing of passwords has become rather more serious).

Personally I feel that if we go down the password route then, besides the “easy” brute-forcing of old /etc/passwd files, we have to include the LANMAN password hashes but, again, of historical interest definitely but not sure it can be turned into an article unless someone manages to write it all the way to the latest oopsies like Linux’s systemd and usernames starting with a digit or Apple’s 10.13 “be root with a simple Enter”. I guess one could write it from the point of view of looking at the bad decisions, their implications and the bugs which made even bad decisions look almost good.

Arrigo



  parent reply	other threads:[~2017-12-29 11:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-18 10:31 Arrigo Triulzi
2017-12-19  1:08 ` Dave Horsfall
2017-12-19 20:17   ` Derek Fawcus
2017-12-19 20:32     ` Ron Natalie
2017-12-20  2:22       ` Dave Horsfall
2017-12-19 23:45     ` Dave Horsfall
2017-12-29 11:22     ` Arrigo Triulzi [this message]
2017-12-19 20:25   ` Derek Fawcus
2017-12-19  1:25 ` Larry McVoy
2017-12-20  0:01   ` Nemo
2017-12-29 11:14   ` Arrigo Triulzi

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=45CBBAF3-CE6D-4DA5-B685-E78CEE6674C1@alchemistowl.org \
    --to=arrigo@alchemistowl.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).