public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Casey Marshall <csm@gnu.org>
To: mauve-discuss@sources.redhat.com
Subject: RFC: PKITS tests
Date: Sun, 23 Jul 2006 21:02:00 -0000	[thread overview]
Message-ID: <ED523C44-C3C1-4F1F-A5D2-70BC80EEBA85@gnu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1214 bytes --]

I wrote a partial implementation of the PKITS test suite, which was  
developed by NIST to test X.509 certificate parsing and path  
checking, some time ago to test the X.509 classes I had written. I  
had put this into GNU Crypto CVS to keep track of, and so it was  
already written to use the Mauve test harness. These are great tests  
to run against any Java implementation, because Java usually has an X. 
509 implementation standard, and running them against Classpath CVS  
revealed a regression in our security providers. Any objections to  
putting these test files into Mauve?

The test suite comprises 100 test classes and a bunch more example  
certificates and CRLs in the binary DER format. I wrote the test  
classes, but the example certs were developed by NIST and DigitalNet  
for the test suite.

The main page for the test suite is here:

   <http://csrc.nist.gov/pki/testing/x509paths.html>

There was a statement about how the test files can be redistributed  
(aside from those developed by NIST, which are public domain under US  
law) was posted to their mailing list:

   <http://cio.nist.gov/esd/emaildir/lists/pkits/msg00048.html>

If no-one objects, I'll commit these tests to Mauve.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 478 bytes --]

                 reply	other threads:[~2006-07-23 21:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=ED523C44-C3C1-4F1F-A5D2-70BC80EEBA85@gnu.org \
    --to=csm@gnu.org \
    --cc=mauve-discuss@sources.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).