javax.crypto.spec
public class RC2ParameterSpec extends Object implements AlgorithmParameterSpec
Constructor and Description |
---|
RC2ParameterSpec(int effectiveKeyBits)
Create RC2 parameters without an IV.
|
RC2ParameterSpec(int effectiveKeyBits,
byte[] iv)
Create RC2 parameters with an IV.
|
RC2ParameterSpec(int effectiveKeyBits,
byte[] iv,
int offset)
Create RC2 parameters with an IV.
|
Modifier and Type | Method and Description |
---|---|
boolean |
equals(Object o)
Determine whether this Object is semantically equal
to another Object.
|
int |
getEffectiveKeyBits()
Get the number of effective key bits.
|
byte[] |
getIV()
Return the initialization vector, or
null if none was
specified. |
int |
hashCode()
Get a value that represents this Object, as uniquely as
possible within the confines of an int.
|
public RC2ParameterSpec(int effectiveKeyBits)
effectiveKeyBits
- The number of effective key bits.public RC2ParameterSpec(int effectiveKeyBits, byte[] iv)
effectiveKeyBits
- The number of effective key bits.iv
- The IV; the first eight bytes of this array
are used.public RC2ParameterSpec(int effectiveKeyBits, byte[] iv, int offset)
effectiveKeyBits
- The number of effective key bits.iv
- The IV; the first eight bytes of this array
after offset
are used.offset
- From whence to start in the array.public int getEffectiveKeyBits()
public byte[] getIV()
null
if none was
specified.public boolean equals(Object o)
Object
There are some fairly strict requirements on this
method which subclasses must follow:
a.equals(b)
and
b.equals(c)
, then a.equals(c)
must be true as well.a.equals(b)
and
b.equals(a)
must have the same value.a.equals(a)
must
always be true.a.equals(null)
must be false.a.equals(b)
must imply
a.hashCode() == b.hashCode()
.
The reverse is not true; two objects that are not
equal may have the same hashcode, but that has
the potential to harm hashing performance.This is typically overridden to throw a ClassCastException
if the argument is not comparable to the class performing
the comparison, but that is not a requirement. It is legal
for a.equals(b)
to be true even though
a.getClass() != b.getClass()
. Also, it
is typical to never cause a NullPointerException
.
In general, the Collections API (java.util
) use the
equals
method rather than the ==
operator to compare objects. However, IdentityHashMap
is an exception to this rule, for its own good reasons.
The default implementation returns this == o
.
equals
in class Object
o
- the Object to compare toObject.hashCode()
public int hashCode()
Object
There are some requirements on this method which
subclasses must follow:
a.equals(b)
is true, then
a.hashCode() == b.hashCode()
must be as well.
However, the reverse is not necessarily true, and two
objects may have the same hashcode without being equal.Notice that since hashCode
is used in
Hashtable
and other hashing classes,
a poor implementation will degrade the performance of hashing
(so don't blindly implement it as returning a constant!). Also,
if calculating the hash is time-consuming, a class may consider
caching the results.
The default implementation returns
System.identityHashCode(this)
hashCode
in class Object
Object.equals(Object)
,
System.identityHashCode(Object)