From: Casey Marshall <csm@gnu.org>
To: tromey@redhat.com
Cc: mauve-discuss@sources.redhat.com
Subject: Re: X.509 certificate tests
Date: Tue, 26 Oct 2004 17:58:00 -0000 [thread overview]
Message-ID: <87fz41gy3q.fsf@gnu.org> (raw)
In-Reply-To: <m3r7nlfldm.fsf@localhost.localdomain> (Tom Tromey's message of "26 Oct 2004 11:19:01 -0600")
>>>>> "Tom" == Tom Tromey <tromey@redhat.com> writes:
Casey> The only really problematic part are the certificate data: they
Casey> are about 2.6M of binary goo. Any problem with including them?
Tom> As long as there are no legal issues I don't see a problem. My
Tom> copy of mauve seems to be about 14M already, a few more megabytes
Tom> won't hurt.
The test suite was developed by the US government, so it is not
subject to copyright.
Parts were contracted out by the NSA, but it seems that they have
stated that the test files are freely redistributable [1].
--
Casey Marshall || csm@gnu.org
[1] http://cio.nist.gov/esd/emaildir/lists/pkits/msg00047.html
next prev parent reply other threads:[~2004-10-26 17:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-26 5:46 Casey Marshall
2004-10-26 15:46 ` Tom Tromey
2004-10-26 17:09 ` Casey Marshall
2004-10-26 17:20 ` Tom Tromey
2004-10-26 17:58 ` Casey Marshall [this message]
2004-10-26 20:33 ` Mark Wielaard
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=87fz41gy3q.fsf@gnu.org \
--to=csm@gnu.org \
--cc=mauve-discuss@sources.redhat.com \
--cc=tromey@redhat.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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).