IT. Expert System.

Android Reference

OpenSSLSignature


org.apache.harmony.xnet.provider.jsse

Class OpenSSLSignature

    • Method Detail

      • engineUpdate

        protected void engineUpdate(byte input)
        Description copied from class: SignatureSpi
        Updates the data to be verified or to be signed, using the specified byte.
        Specified by:
        engineUpdate in class SignatureSpi
        Parameters:
        input - the byte to update with.
      • engineUpdate

        protected void engineUpdate(byte[] input,
                        int offset,
                        int len)
        Description copied from class: SignatureSpi
        Updates the data to be verified or to be signed, using the given byte[], starting form the specified index for the specified length.
        Specified by:
        engineUpdate in class SignatureSpi
        Parameters:
        input - the byte array to update with.
        offset - the start index in b of the data.
        len - the number of bytes to use.
      • engineInitVerify

        protected void engineInitVerify(PublicKey publicKey)
                                 throws InvalidKeyException
        Description copied from class: SignatureSpi
        Initializes this SignatureSpi instance for signature verification, using the public key of the identity whose signature is going to be verified.
        Specified by:
        engineInitVerify in class SignatureSpi
        Parameters:
        publicKey - the public key.
        Throws:
        InvalidKeyException - if publicKey is not valid.
      • engineSign

        protected byte[] engineSign()
                             throws SignatureException
        Description copied from class: SignatureSpi
        Generates and returns the signature of all updated data.

        This SignatureSpi instance is reset to the state of its last initialization for signing and thus can be used for another signature from the same identity.

        Specified by:
        engineSign in class SignatureSpi
        Returns:
        the signature of all updated data.
        Throws:
        SignatureException - if this SignatureSpi instance is not initialized properly.
      • engineVerify

        protected boolean engineVerify(byte[] sigBytes)
                                throws SignatureException
        Description copied from class: SignatureSpi
        Indicates whether the given sigBytes can be verified using the public key or a certificate of the signer.

        This SignatureSpi instance is reset to the state of its last initialization for verifying and thus can be used to verify another signature of the same signer.

        Specified by:
        engineVerify in class SignatureSpi
        Parameters:
        sigBytes - the signature to verify.
        Returns:
        true if the signature was verified, false otherwise.
        Throws:
        SignatureException - if this SignatureSpi instance is not initialized properly.
      • 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


Content

Android Reference

Java basics

Java Enterprise Edition (EE)

Java Standard Edition (SE)

SQL

HTML

PHP

CSS

Java Script

MYSQL

JQUERY

VBS

REGEX

C

C++

C#

Design patterns

RFC (standard status)

RFC (proposed standard status)

RFC (draft standard status)

RFC (informational status)

RFC (experimental status)

RFC (best current practice status)

RFC (historic status)

RFC (unknown status)

IT dictionary

License.
All information of this service is derived from the free sources and is provided solely in the form of quotations. This service provides information and interfaces solely for the familiarization (not ownership) and under the "as is" condition.
Copyright 2016 © ELTASK.COM. All rights reserved.
Site is optimized for mobile devices.
Downloads: 730 / . Delta: 0.03046 с