From: "Raif S. Naffah" <raif@swiftdsl.com.au>
To: Mark Wielaard <mark@klomp.org>
Cc: mauve-discuss@sourceware.org
Subject: Re: test with HTTPS url
Date: Sat, 04 Mar 2006 10:50:00 -0000 [thread overview]
Message-ID: <200603042153.46131.raif@swiftdsl.com.au> (raw)
In-Reply-To: <1141398633.4959.69.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1650 bytes --]
hello Mark,
On Saturday 04 March 2006 02:10, Mark Wielaard wrote:
> On Wed, 2006-03-01 at 00:54 +1100, Raif S. Naffah wrote:
> > i just checked in a new testlet
> > (gnu.testlet.gnu.java.security.jce.TestOfHttps) that accesses the
> > url
> >
> > https://www.paypal.com/
> >
> > if there is a known https-accessible location that is/can be used
> > for running such tests let me know and i'll amend the test
> > accordingly.
>
> I think that is fine for now. We could install a https server on
> builder.classpath.org or maybe have something like Wolfgang just
> suggested a Mauve local https server.
>
> Three small comment on the test itself.
> - You seem to be using the eclipse templates. Not that it still
> contains a "FIXME: your info here" :)
noted.
> - It declares a GNU-CRYPTO Tag and explicitly installs the Jessie and
> GnuCrypto providers. But it really should just work for any JDK1.4
> out of the box (and it actually does!)
it does with the JDK because the JDK contains export-controlled crypto.
for us in Classpath to do that we would then break what A. Green asked
for wrt. separating export-controlled from non-export-controlled crypto
code.
> - It prints out all lines read to System.out. That isn't really
> necessary and obscures the output of the test.
noted.
> If you could correct those issue that would be great.
i'm checking in a version that fixes the first and last issues. if we
want to re-consider the export-controlled option let me know since we
would have then to do more work in the Classpath tree before changing
this testlet.
cheers;
rsn
[-- Attachment #2: Type: application/pgp-signature, Size: 218 bytes --]
prev parent reply other threads:[~2006-03-04 10:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-28 13:52 Raif S. Naffah
2006-03-03 15:10 ` Mark Wielaard
2006-03-04 10:50 ` Raif S. Naffah [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=200603042153.46131.raif@swiftdsl.com.au \
--to=raif@swiftdsl.com.au \
--cc=mark@klomp.org \
--cc=mauve-discuss@sourceware.org \
/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).