|
Authored by: Anonymous on Thursday, April 26 2012 @ 10:27 AM EDT |
A lot of people use it as an excellent free cleanroom cipher
provider...
I think they probably even use it themselves.
Have they ever shown a hint of being unhappy with
bouncycastle cleanroom code or comments?
Then again who knows what they plan. It's clear that the
Java community is of little value to them, if they pursue
this line of thinking, soon they will have no community.[ Reply to This | Parent | # ]
|
|
Authored by: rsteinmetz70112 on Thursday, April 26 2012 @ 10:50 AM EDT |
I bet if you look at similar comments in many languages you would get very
similar construction, because that's just the way you do it so that everyone
understands what you are talking about.
---
Rsteinmetz - IANAL therefore my opinions are illegal.
"I could be wrong now, but I don't think so."
Randy Newman - The Title Theme from Monk
[ Reply to This | Parent | # ]
|
|
Authored by: Guil Rarey on Thursday, April 26 2012 @ 11:13 AM EDT |
Okay, so what alternative, clear and concise, technically accurate ways are
there to express the facts regarding the code objects and their relationships
discussed here?
That's really the issue, isn't it? If there are limited or no alternatives
satisfying the clarity, brevity and accuracy requirements for the statement,
then scenes a faire applies, right?
---
If the only way you can value something is with money, you have no idea what
it's worth. If you try to make money by making money, you won't. You might con
so[ Reply to This | Parent | # ]
|
|
Authored by: PJ on Thursday, April 26 2012 @ 11:41 AM EDT |
Ew. A punch of baloney... what an image. [ Reply to This | Parent | # ]
|
|
Authored by: lwoggardner on Thursday, April 26 2012 @ 05:41 PM EDT |
It would seem that BouncyCastle's clean room was clean in
terms of
implementation, but not the javadoc...
If you go beyond the first line of
the comment and read the
rest, I don't think there is an argument to suggest
this is
not literal copying
JDK 1.4
Javadocs and all
other since...
public class
CipherInputStream
extends FilterInputStream
A CipherInputStream is
composed of an InputStream and a
Cipher so that read() methods return data that
are read in
from the underlying InputStream but have been additionally
processed by the Cipher. The Cipher must be fully
initialized before being
used by a CipherInputStream.
For example, if the Cipher is initialized for
decryption,
the CipherInputStream will attempt to read in data and
decrypt
them, before returning the decrypted data.
This class adheres strictly to
the semantics, especially the
failure semantics, of its ancestor classes
java.io.FilterInputStream and java.io.InputStream. This
class has exactly
those methods specified in its ancestor
classes, and overrides them all.
Moreover, this class
catches all exceptions that are not thrown by its ancestor
classes. In particular, the skip method skips, and the
available method counts
only data that have been processed
by the encapsulated Cipher.
It is
crucial for a programmer using this class not to use
methods that are not
defined or overriden in this class
(such as a new method or constructor that is
later added to
one of the super classes), because the design and
implementation of those methods are unlikely to have
considered security
impact with regard to CipherInputStream.
BouncyCastle JCE for Java 1.3
public class
CipherInputStream
extends java.io.FilterInputStream
A
CipherInputStream is composed of an InputStream and a
Cipher so that read()
methods return data that are read in
from the underlying InputStream but have
been additionally
processed by the Cipher. The Cipher must be fully
initialized before being used by a CipherInputStream.
For example, if the
Cipher is initialized for decryption,
the CipherInputStream will attempt to
read in data and
decrypt them, before returning the decrypted data.
This
class adheres strictly to the semantics, especially the
failure semantics, of
its ancestor classes
java.io.FilterInputStream and java.io.InputStream. This
class has exactly those methods specified in its ancestor
classes, and
overrides them all. Moreover, this class
catches all exceptions that are not
thrown by its ancestor
classes. In particular, the skip method skips, and the
available method counts only data that have been processed
by the encapsulated
Cipher.
It is crucial for a programmer using this class not to use
methods
that are not defined or overriden in this class
(such as a new method or
constructor that is later added to
one of the super classes), because the
design and
implementation of those methods are unlikely to have
considered
security impact with regard to CipherInputStream.
[ Reply to This | Parent | # ]
|
|
|
|
|