From: Isaac Dunham <idunham@lavabit.com>
To: musl@lists.openwall.com
Subject: Re: musl 0.9.3 released
Date: Sun, 5 Aug 2012 16:39:48 -0700 [thread overview]
Message-ID: <20120805163948.37781cf1@newbook> (raw)
In-Reply-To: <20120805052219.GH544@brightrain.aerifal.cx>
On Sun, 5 Aug 2012 01:22:20 -0400
Rich Felker <dalias@aerifal.cx> wrote:
> On Sun, Aug 05, 2012 at 12:56:24AM -0400, idunham@lavabit.com wrote:
> > > On 08/05/2012 03:00 AM, idunham@lavabit.com wrote:
> > >>
> > >>> I'd also like to finish and integrate the rest of rdp's porting
> > >>> work (mips64, ppc, and microblaze) and possibly get an x32
> > >>> (32-bit ABI on x86_64) port underway, and integrate additional
> > >>> hash function support (blowfish, sha, md5) for crypt.
> > >> All of these sound good.
> > ...In other words, if you or someone you are in
> > commmunication with is going to start using musl x32 for any reason
> > besides "It happens to be supported".
>
> If I were going to switch to x86_64 cpu, which I will probably do in
> the next few years, x32 would certainly be appealing. Not decided for
> sure, but it seems very nice to get all the important benefits of a
> 64-bit cpu with none of the bloat. I think this sounds appealing to
> a big part of musl's target userbase too...
OK, that's what I was asking.
> > >> Something other than standard crypt (isn't that DES, which can be
> > >> cracked in a day on the right machine?) would be one of the more
> > >> interesting ones from my perspective. Remembering the recent
> > >> test results, I'd be hoping for bcrypt as well (it's where OpenCL
> > >> cracking gets the least benefit).
> > > which test results are you referring to ?
> >
> > best discussion:
> > http://openwall.info/wiki/john/GPU
> > http://openwall.info/wiki/john/GPU/bcrypt
<snip>
> > 4. This is "If you plan to add hashes (which Rich has stated
> > that he hopes to do, in the original post), please consider
> > making bcrypt one of them."
>
> How bloated is it? Sadly crypto folks seem to love giant bloated
> tables...
Well, now that I look it up, bcrypt() is blowfish crypt() (at least,
it's the primary blowfish-based crypt()--it does have a few
peculiarities of its own)
It is somewhat expensive in terms of resources, per the results
mentioned.
next prev parent reply other threads:[~2012-08-05 23:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-03 2:36 Rich Felker
2012-08-03 14:01 ` Gregor Richards
2012-08-05 1:00 ` idunham
2012-08-05 3:58 ` John Spencer
2012-08-05 4:56 ` idunham
2012-08-05 5:22 ` Rich Felker
2012-08-05 16:31 ` orc
2012-08-05 16:43 ` orc
2012-08-05 17:05 ` Daniel Cegiełka
2012-08-05 18:29 ` Rich Felker
2012-08-05 16:46 ` Rich Felker
2012-08-05 17:18 ` orc
2012-08-05 23:39 ` Isaac Dunham [this message]
2012-08-05 12:30 ` x32 (was: Re: [musl] musl 0.9.3 released) John Spencer
2012-08-05 12:46 ` Daniel Cegiełka
2012-08-05 12:58 ` Kurt H Maier
2012-08-05 13:15 ` Daniel Cegiełka
2012-08-05 13:32 ` x32 Anthony G. Basile
2012-08-05 14:13 ` x32 Daniel Cegiełka
2012-08-05 13:19 ` x32 Anthony G. Basile
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=20120805163948.37781cf1@newbook \
--to=idunham@lavabit.com \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).