Package org.bouncycastle.crypto.digests

Class OpenSSLDigest

java.lang.Object

org.bouncycastle.crypto.digests.OpenSSLDigest

All Implemented Interfaces:

Digest, ExtendedDigest

Direct Known Subclasses:

OpenSSLDigest.MD5, OpenSSLDigest.SHA1, OpenSSLDigest.SHA256, OpenSSLDigest.SHA384, OpenSSLDigest.SHA512

public class OpenSSLDigest
extends Object
implements ExtendedDigest

Implements the BouncyCastle Digest interface using OpenSSL's EVP API.

Nested Class Summary

Nested Classes

Modifier and Type	Class	Description
static class	OpenSSLDigest.MD5
static class	OpenSSLDigest.SHA1
static class	OpenSSLDigest.SHA256
static class	OpenSSLDigest.SHA384
static class	OpenSSLDigest.SHA512

Method Summary

Modifier and Type	Method	Description
int	doFinal(byte[] out, int outOff)	close the digest, producing the final digest value.
protected void	finalize()	Invoked when the garbage collector has detected that this instance is no longer reachable.
String	getAlgorithmName()	return the algorithm name
int	getByteLength()	Return the size in bytes of the internal buffer the digest applies it's compression function to.
int	getDigestSize()	return the size, in bytes, of the digest produced by this message digest.
void	reset()	reset the digest back to it's initial state.
void	update(byte in)	update the message digest with a single byte.
void	update(byte[] in, int inOff, int len)	update the message digest with a block of bytes.

Methods inherited from class java.lang.Object

clone, equals, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Method Details

getAlgorithmName

public String getAlgorithmName()

Description copied from interface: Digest

return the algorithm name

Specified by:

getAlgorithmName in interface Digest

Returns:

the algorithm name

getDigestSize

public int getDigestSize()

Description copied from interface: Digest

return the size, in bytes, of the digest produced by this message digest.

Specified by:

getDigestSize in interface Digest

Returns:

the size, in bytes, of the digest produced by this message digest.

getByteLength

public int getByteLength()

Description copied from interface: ExtendedDigest

Return the size in bytes of the internal buffer the digest applies it's compression function to.

Specified by:

getByteLength in interface ExtendedDigest

Returns:

byte length of the digests internal buffer.

reset

public void reset()

Description copied from interface: Digest

reset the digest back to it's initial state.

Specified by:

reset in interface Digest

update

public void update(byte in)

Description copied from interface: Digest

update the message digest with a single byte.

Specified by:

update in interface Digest

Parameters:

in - the input byte to be entered.

update

public void update(byte[] in,
int inOff,
int len)

Description copied from interface: Digest

update the message digest with a block of bytes.

Specified by:

update in interface Digest

Parameters:

in - the byte array containing the data.

inOff - the offset into the byte array where the data starts.

len - the length of the data.

doFinal

public int doFinal(byte[] out,
int outOff)

Description copied from interface: Digest

close the digest, producing the final digest value. The doFinal call leaves the digest reset.

Specified by:

doFinal in interface Digest

Parameters:

out - the array the digest is to be copied into.

outOff - the offset into the out array the digest is to start at.

finalize

protected void finalize()
                 throws Throwable

Description copied from class: Object

Invoked when the garbage collector has detected that this instance is no longer reachable. The default implementation does nothing, but this method can be overridden to free resources.

Note that objects that override finalize are significantly more expensive than objects that don't. Finalizers may be run a long time after the object is no longer reachable, depending on memory pressure, so it's a bad idea to rely on them for cleanup. Note also that finalizers are run on a single VM-wide finalizer thread, so doing blocking work in a finalizer is a bad idea. A finalizer is usually only necessary for a class that has a native peer and needs to call a native method to destroy that peer. Even then, it's better to provide an explicit close method (and implement Closeable), and insist that callers manually dispose of instances. This works well for something like files, but less well for something like a BigInteger where typical calling code would have to deal with lots of temporaries. Unfortunately, code that creates lots of temporaries is the worst kind of code from the point of view of the single finalizer thread.

If you must use finalizers, consider at least providing your own ReferenceQueue and having your own thread process that queue.

Unlike constructors, finalizers are not automatically chained. You are responsible for calling super.finalize() yourself.

Uncaught exceptions thrown by finalizers are ignored and do not terminate the finalizer thread. See Effective Java Item 7, "Avoid finalizers" for more.

Overrides:

finalize in class Object

Throws:

Throwable