Skip to Content.
Please activate JavaScript in your web browser
List archive
Re: [SM-Commit] GIT changes to master grimoire by David Haley (0e651c36ed0f5c7e8852c499eec07eb835df4872)
Chronological
Thread
<
Chronological
>
<
Thread
>
From
: Remko van der Vossen <wich AT yuugen.jp>
To
: David Haley <khoralin AT gmail.com>, "sm-commit AT lists.ibiblio.org" <sm-commit AT lists.ibiblio.org>
Subject
: Re: [SM-Commit] GIT changes to master grimoire by David Haley (0e651c36ed0f5c7e8852c499eec07eb835df4872)
Date
: Wed, 13 Nov 2013 23:12:48 +0100
>
Additionally, the SOURCE_HASH field has been updated from SHA512,
>
which I presume defaults to WORKS_FOR_ME, to SHA1:UPSTREAM_HASH.
Do we consider sha1 to be sufficiently secure? I remember something about
sha512 or pgp signature being required by our guidelines.
Regards, Remko
[SM-Commit] GIT changes to master grimoire by David Haley (0e651c36ed0f5c7e8852c499eec07eb835df4872)
,
David Haley, 11/13/2013
Re: [SM-Commit] GIT changes to master grimoire by David Haley (0e651c36ed0f5c7e8852c499eec07eb835df4872)
,
Remko van der Vossen, 11/13/2013
Re: [SM-Commit] GIT changes to master grimoire by David Haley (0e651c36ed0f5c7e8852c499eec07eb835df4872)
,
Eric Sandall, 11/20/2013
Archive powered by
MHonArc 2.6.24
.