Hi Nettle folks--
There's a typo in the Nettle manual about the ARCTWO block size. the attached patch (against 2.1) should fix it.
Of course, it might already be fixed on the development trunk. Is there a public revision control system for nettle someplace i can look at?
--dkg
PS i sent this message earlier PGP/MIME-signed, but it was rejected by the mailing list with "After content filtering, the message was empty" -- could the content filtering be relaxed a little bit to allow multipart/signed messages?
The message MIME structure looked like this:
└┬╴multipart/signed ├┬╴multipart/mixed │├╴text/plain │└╴text/x-diff attachment └╴application/pgp-signature attachment
I then tried re-sending it without the cryptographic signature, which produced a message like this:
└┬╴multipart/mixed ├╴text/plain └╴text/x-diff attachment
This second message was rejected with the message:
"The message's content type was not explicitly allowed"
Both of these seem like pretty reasonable message structures for posts to a cryptographic software development mailing list; it'd be nice if they could go through :)
Here is the patch inline:
arctwo-doc-fix.patch
--- nettle.texinfo.orig 2011-03-16 19:08:50.000000000 -0400 +++ nettle.texinfo 2011-03-16 19:09:26.000000000 -0400 @@ -871,7 +871,7 @@ @end deftp
@defvr Constant ARCTWO_BLOCK_SIZE -The AES block-size, 8 +The ARCTWO block-size, 8 @end defvr
@defvr Constant ARCTWO_MIN_KEY_SIZE
On 03/21/2011 02:24 AM, Daniel Kahn Gillmor wrote:
Of course, it might already be fixed on the development trunk. Is there a public revision control system for nettle someplace i can look at?
Gah, this question was already answered by niels several days ago, though it was after i sent this patch originally, and this message was caught up in fighting with the mailing list configuration.
It looks like this fix has not yet been made on the development trunk, if my reading of the CVS repo is accurate.
--dkg
Daniel Kahn Gillmor dkg@fifthhorseman.net writes:
PS i sent this message earlier PGP/MIME-signed, but it was rejected by the mailing list with "After content filtering, the message was empty" -- could the content filtering be relaxed a little bit to allow multipart/signed messages?
I agree this rejection was silly. I'm not so good at mailman configuration. The "pass_mime_types" option was set to
text/plain multipart/signed
I'm now changing it to
text multipart application/pgp-signature
Do you think that is good enough? Other suggestions?
Or is it better to completely disable this content-type filtering?
Regards, /Niels
On 03/21/2011 09:41 AM, Niels Möller wrote:
I agree this rejection was silly. I'm not so good at mailman configuration. The "pass_mime_types" option was set to
text/plain multipart/signed
I'm now changing it to
text multipart application/pgp-signature
Do you think that is good enough? Other suggestions?
I'm no mailman guru either, but these settings changes seem to have let my recent message "making algorithms in nettle dynamically enumerable" go through fine, while signed. So thanks!
Or is it better to completely disable this content-type filtering?
I've never used content-type filtering -- i'd lean toward turning it off unless there is a well-understood problem that it fixes (e.g. if a spammer is targetting the list with a bunch of garbage). But i'm happy with it as it currently stands :)
Thanks for the fix,
--dkg
Daniel Kahn Gillmor dkg@fifthhorseman.net writes:
arctwo-doc-fix.patch
--- nettle.texinfo.orig 2011-03-16 19:08:50.000000000 -0400 +++ nettle.texinfo 2011-03-16 19:09:26.000000000 -0400 @@ -871,7 +871,7 @@ @end deftp
@defvr Constant ARCTWO_BLOCK_SIZE -The AES block-size, 8 +The ARCTWO block-size, 8 @end defvr
@defvr Constant ARCTWO_MIN_KEY_SIZE
Checked in now. Thanks for spotting it.
Regards, /Niels
nettle-bugs@lists.lysator.liu.se