From: "Daniel Cegiełka" <daniel.cegielka@gmail.com>
To: musl@lists.openwall.com
Subject: Re: [RFC] sha2: new <sha2.h> header
Date: Tue, 24 Mar 2015 18:06:53 +0100 [thread overview]
Message-ID: <CAPLrYETid81byMectUMjJ2bVkTUn1zZOO3SZL5Fo1oqM5AGkNw@mail.gmail.com> (raw)
In-Reply-To: <1427216271-141535-1-git-send-email-shawn@churchofgit.com>
2015-03-24 17:57 GMT+01:00 Shawn Landden <shawn@churchofgit.com>:
> We have sha512 and sha256 code sitting here, yet we don't export it with any useful interface.
>
> This came out of discussion with pikhq on IRC.
>
> No tests yet, and no sha256 until this gets some review.
http://www.openwall.com/lists/musl/2015/01/14/6
Daniel
prev parent reply other threads:[~2015-03-24 17:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 16:57 Shawn Landden
2015-03-24 17:00 ` Shawn Landden
2015-03-24 21:22 ` Shawn Landden
2015-03-24 22:02 ` Laurent Bercot
2015-03-24 17:06 ` Daniel Cegiełka [this message]
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=CAPLrYETid81byMectUMjJ2bVkTUn1zZOO3SZL5Fo1oqM5AGkNw@mail.gmail.com \
--to=daniel.cegielka@gmail.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).