From: Mark Wielaard <mark@klomp.org>
To: Casey Marshall <csm@gnu.org>
Cc: tromey@redhat.com, mauve-discuss@sources.redhat.com
Subject: Re: X.509 certificate tests
Date: Tue, 26 Oct 2004 20:33:00 -0000 [thread overview]
Message-ID: <1098822778.2556.61.camel@localhost> (raw)
In-Reply-To: <87fz41gy3q.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 2037 bytes --]
Hi,
On Tue, 2004-10-26 at 19:58, Casey Marshall wrote:
> 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].
Please add the following text from that to the README:
The test document and data were jointly developed by NIST and
DigitalNet. Any contribution made to this project by NIST is covered by
Title 17 Section 105 of the United States Code which states that any
work developed by the United State Government is not subject to
copyright protection (see http://www4.law.cornell.edu/uscode/17/105.html).
So, NIST's contributions to the test documentation and data are in the
public domain.
While DigitalNet's contributions to the documentation and data may be
subject to copyright, all of the work done by DigitalNet on this project
was done under contract for NSA. So, it would be up to NSA to decide
how DigitalNet's contributions to the project could be used. In
response to your query, I asked DigitalNet about the use of the test
suite and received the following response:
"V51 [of NSA] approved of the public release of the PKITS test data
and documents. There are no restrictions regarding their redistribution."
when you add this data.
Although we are more relaxed about accepting contributions to Mauve than
with for example GNU Classpath (for which we require written
confirmation by all contributors) we still want to have a record who
contributed what when. This can be done in the ChangeLog and the README
file though. Even if it wouldn't be a very big disaster if we ever have
to remove a test from mauve we should try to prevent ever having to be
in such a situation and prevent any unclearity about the origins of any
of the tests.
Thanks,
Mark
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2004-10-26 20:33 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
2004-10-26 20:33 ` Mark Wielaard [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=1098822778.2556.61.camel@localhost \
--to=mark@klomp.org \
--cc=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).