The debian-private mailing list leak, part 1. Volunteers have complained about Blackmail. Lynchings. Character assassination. Defamation. Cyberbullying. Volunteers who gave many years of their lives are picked out at random for cruel social experiments. The former DPL's girlfriend Molly de Blanc is given volunteers to experiment on for her crazy talks. These volunteers never consented to be used like lab rats. We don't either. debian-private can no longer be a safe space for the cabal. Let these monsters have nowhere to hide. Volunteers are not disposable. We stand with the victims.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Libcrypt in LIBC 6 issues

> Yes, this has come up before. Libcrypt is world-war-two technology,
> and we'll take the risk on it.

Good answer, wrong facts: crypt(1), the command line program, is
pre-ww2 rotor technology (with some symmetries that make it easier to
crack :-) crypt(3), ie. libcrypt, iterates DES, which is emphatically
*not* WW2 technology, as it was invented by IBM in the early 70's.
(The passwd crypt algorithm is to take the password, turn it into a
*key*, use that key to DES-encrypt a block of zeroes 16 times.  Some
ascii re-encoding is also involved.  If I remember right, the salt is
used to hack one of the lookup tables.)

> The best way to deal with it would be to export libcrypt code that is not
> reversible - it would work as a one-way hash function for passwords,

There's a straightforward way to do that: simply expand the whole
thing inline (maybe unrolling the loops too, or maybe don't bother),
so the DES routine doesn't actually have an entry point.  Then you can
probably find some optimization, or at least minor improvements, to
help bind the thing together while you're in there :-) 


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-private-request@lists.debian.org . 
Trouble?  e-mail to templin@bucknell.edu .