Package org.conscrypt

Class OpenSSLMessageDigestJDK

java.lang.Object
java.security.MessageDigestSpi
java.security.MessageDigest
org.conscrypt.OpenSSLMessageDigestJDK
All Implemented Interfaces:
Cloneable
Direct Known Subclasses:
OpenSSLMessageDigestJDK.MD5, OpenSSLMessageDigestJDK.SHA1, OpenSSLMessageDigestJDK.SHA256, OpenSSLMessageDigestJDK.SHA384, OpenSSLMessageDigestJDK.SHA512
public class OpenSSLMessageDigestJDK
extends MessageDigest
implements Cloneable
Implements the JDK MessageDigest interface using OpenSSL's EVP API.

  • Method Details

    • engineReset

      protected void engineReset()
      Description copied from class: MessageDigestSpi
      Puts this MessageDigestSpi back in an initial state, such that it is ready to compute a one way hash value.
      Specified by:
      engineReset in class MessageDigestSpi

    • engineGetDigestLength

      protected int engineGetDigestLength()
      Description copied from class: MessageDigestSpi
      Returns the engine digest length in bytes. If the implementation does not implement this function 0 is returned.
      Overrides:
      engineGetDigestLength in class MessageDigestSpi
      Returns:
      the digest length in bytes, or 0.

    • engineUpdate

      protected void engineUpdate​(byte input)
      Description copied from class: MessageDigestSpi
      Updates this MessageDigestSpi using the given byte.
      Specified by:
      engineUpdate in class MessageDigestSpi
      Parameters:
      input - the byte to update this MessageDigestSpi with.
      See Also:
      MessageDigestSpi.engineReset()

    • engineUpdate

      protected void engineUpdate​(byte[] input, int offset, int len)
      Description copied from class: MessageDigestSpi
      Updates this MessageDigestSpi using the given byte[].
      Specified by:
      engineUpdate in class MessageDigestSpi
      Parameters:
      input - the byte array.
      offset - the index of the first byte in input to update from.
      len - the number of bytes in input to update from.

    • engineDigest

      protected byte[] engineDigest()
      Description copied from class: MessageDigestSpi
      Computes and returns the final hash value for this MessageDigestSpi. After the digest is computed the receiver is reset.
      Specified by:
      engineDigest in class MessageDigestSpi
      Returns:
      the computed one way hash value.
      See Also:
      MessageDigestSpi.engineReset()

    • clone

      public Object clone() throws CloneNotSupportedException
      Description copied from class: Object
      Creates and returns a copy of this Object. The default implementation returns a so-called "shallow" copy: It creates a new instance of the same class and then copies the field values (including object references) from this instance to the new instance. A "deep" copy, in contrast, would also recursively clone nested objects. A subclass that needs to implement this kind of cloning should call super.clone() to create the new instance and then create deep copies of the nested, mutable objects.
      Overrides:
      clone in class MessageDigest
      Returns:
      a copy of this object.
      Throws:
      CloneNotSupportedException - if this object's class does not implement the Cloneable interface.

    • 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