|
| Authored by: Anonymous on Wednesday, April 25 2012 @ 04:56 PM EDT |
| I spotted that too. Wonder if it was a transcription error. [ Reply to This | Parent | # ]
|
|
|
| Authored by: lwoggardner on Wednesday, April 25 2012 @ 06:30 PM EDT |
From the
bouncy castle
website
A clean room implementation of the JCE
1.2.1.
I think they also backported some of the new Java crypto
apis
to
be available for older versions of Java[ Reply to This | Parent | # ]
|
|
|
| Authored by: Anonymous on Wednesday, April 25 2012 @ 08:37 PM EDT |
BouncyCastle implements Java's cryptography API, JCE. The JCE is an extension of
the core Java APIs into an area they don't address, cryptography.[ Reply to This | Parent | # ]
|
|
|
| Authored by: Anonymous on Friday, April 27 2012 @ 12:49 AM EDT |
I'm one of the authors of Bouncy Castle. It's been around for over 10 years.
We created a compatible provider when crypto was basically disallowed
outside the USA due to export reasons.
We also implemented a clean-room implementation of the JCE, have a signing
certificate from Sun to package the provider and all of this is based on some
low level primitives we call the "light-weight" library.
It was built this way so it would run on the Palm Pilot originally, then JavaME
(called J2ME back then).
We have all sorts of higher level libraries (like CMS/PGP) which
"most" people
use.
We're still very definitely around. We've very definitely open source.[ Reply to This | Parent | # ]
|
|
