|
Joe "The Boss" MasseriaJoe had little man's syndrome. He was never above biting and groin punching his quarry. In fact, at 5'2", he was never above anything. Yet this little Sicilian maniac ran much of New York during the late 1920's, mainly thanks to his brutality and unpredictable temper.Born in 1879 as Guiseppe Masseria, he was a racist, bigoted, old school mobster. Almost everything about the man is apocryphal because Joe spoke very little English, and was extremely cantankerous. It's thought he came to the US in 1903 after he stabbed a man to death in Palermo, Italy. In New York, Joe joined the Ciro Terranova gang, an up and coming group of thugs that had moved their way up the east side of New York. Oddly enough, the most common practice of this gang was a strategy known as "Black Handing." In practice, it wasn't the brightest of rackets: Sicilian gangsters would target Sicilian businesses for extortion, protection, and black mail.
The Artichoke King of New YorkCiro Terranova was not a particularly gifted gangster. He kept his rackets confined to what he knew. Evidently, he knew a lot about artichokes, because by 1913, he was dubbed the Artichoke king of New York. Every 'choke that was sold in Manhattan had to get there through Terranova's gang, leaving a hefty pile of cash in their hands.Soon, the Morello gang wanted to muscle in on this vast artichoke empire and began killing Terranova men at will. Masseria, as Terranova's top enforcer, lead a number of raids on the Morello head quarters, killing around a dozen henchmen with the help of some Terranova gorillas. The Morello gang was topped by a band of brothers, the most powerful of which was named Peter. Peter had one of the best nicknames of the early mafia world: The Clutching Hand.  Masseria never went anywhere without two gorillas, at the time, but Valenti managed to kill both of them in six seconds, thanks to his dual handgun kung-fu.
Run, Bitch!Valenti chased Masseria around the streets of New York, cornering him in a dry cleaning outfit. Inside, he pumped round after round into racks of clothes. After using up all of his ammo, Masseria was no closer to death, and Valenti was cursing and stamping his feet. When the cops arrived, Valenti gave up and Masseria went home.Joe took Valenti out for his transgressions. He sent Joe Adonis and Lucky Luciano to do it, and the pair dropped him at an ambush in a local restaurant. Adonis and Luciano were the golden boys of Masseria's empire afterwards, members of the privileged few he considered trusted allies.  He clung to all the old school ideals that the new crowd of the underworld were trying to forget. He only used Italian bodyguards, and preferred to hire Sicilians when they were available. Joe constantly demanded that Luciano stop hanging around with Jews, like Meyer Lansky, Louis Buchalter, and Bugsy Siegel. Through the 20's, Masseria's empire grew. He gathered thousands of thugs around him, including such notables as Albert Anastasia, Carlo Gambino, Vito Genovese, Frank Costello, and Paul Castellano. One of Masseria's largest short comings was his inability to understand the power of a bribe. Masseria was so old school that he never even tipped his waiters, an unforgivable sin by modern gangster standards. Joe hoarded his money. Luciano, always keen to offer new ideas, suggested that Joe might offer some sort of profit sharing for his boys, clients, and officials. But Joe never even considered it. It was simply not done in the old world, so it would not be done here.
Oh Hidey Hidey Hidey Hidey Hidey HoWhen Salvatore Maranzano began shuffling into Masseria's bootlegging territory, that Joe immediately declared open war. He sent his thugs out on the streets to gun down anyone associated with Maranzano's gang. Maranzano did the same, enlisting the help of an ethnically mixed group of gangsters, such as Irishmen, Jews, and Germans.The war would come to be known as the Castellmarise war, and it would claim hundreds of lives between 1928 and 1931. The whole time, Luciano tried to stop the fighting so everyone could simply focus on stealing, extorting, and smuggling. Masseria wouldn't hear of it. So, after Luciano was abducted and almost killed by Maranzano's men, he decided to stop the war the only way he knew how.
Feed, THEN KillLucky set up a date with his boss. He told Masseria to meet him at their favorite restaurant: Nuova Villa Tammaro, on Coney Island. There, Masseria gorged himself on a seven course Italian meal. After the food was gone, Luciano started a game of cards with his boss. The two talked and played for a while, then Lucky excused himself to go piss.As soon as Lucky left, five of Masseria's own men walked in and pumped him full of lead. It was tax day, April 15, 1931, and Masseria died holding the ace of spades. The moment Masseria hit the floor, the Castellmarese war ended. Luciano told police the truth: he was pissing when he heard the shots, and when he came out of the bathroom, he found his boss dead on the floor. No one went to Joe's funeral. Not even his own wife. He was buried in a little bitty coffin. |


public class Cipher extends Object
In order to create a Cipher object, the application calls the
Cipher's getInstance
method, and passes the name of the
requested transformation to it. Optionally, the name of a provider
may be specified.
A transformation is a string that describes the operation (or set of operations) to be performed on the given input, to produce some output. A transformation always includes the name of a cryptographic algorithm (e.g., DES), and may be followed by a feedback mode and padding scheme.
A transformation is of the form:
(in the latter case, provider-specific default values for the mode and padding scheme are used). For example, the following is a valid transformation:
Cipher c = Cipher.getInstance("DES/CBC/PKCS5Padding");Using modes such as
CFB
and OFB
, block
ciphers can encrypt data in units smaller than the cipher's actual
block size. When requesting such a mode, you may optionally specify
the number of bits to be processed at a time by appending this number
to the mode name as shown in the "DES/CFB8/NoPadding
" and
"DES/OFB32/PKCS5Padding
" transformations. If no such
number is specified, a provider-specific default is used. (For
example, the SunJCE provider uses a default of 64 bits for DES.)
Thus, block ciphers can be turned into byte-oriented stream ciphers by
using an 8 bit mode such as CFB8 or OFB8.
Modes such as Authenticated Encryption with Associated Data (AEAD)
provide authenticity assurances for both confidential data and
Additional Associated Data (AAD) that is not encrypted. (Please see
RFC 5116 for more
information on AEAD and AEAD algorithms such as GCM/CCM.) Both
confidential and AAD data can be used when calculating the
authentication tag (similar to a Mac
). This tag is appended
to the ciphertext during encryption, and is verified on decryption.
AEAD modes such as GCM/CCM perform all AAD authenticity calculations
before starting the ciphertext authenticity calculations. To avoid
implementations having to internally buffer ciphertext, all AAD data
must be supplied to GCM/CCM implementations (via the updateAAD
methods) before the ciphertext is processed (via
the update
and doFinal
methods).
GCMParameterSpec s = new GCMParameterSpec(...); cipher.init(..., s); // If the GCMParameterSpec is needed again cipher.getParameters().getParameterSpec(GCMParameterSpec.class)); cipher.updateAAD(...); // AAD cipher.update(...); // Multi-part update cipher.doFinal(...); // conclusion of operationEvery implementation of the Java platform is required to support the following standard
Cipher
transformations with the keysizes
in parentheses:
KeyGenerator
,
SecretKey
| Modifier and Type | Field and Description |
|---|---|
static int |
DECRYPT_MODE
Constant used to initialize cipher to decryption mode.
|
static int |
ENCRYPT_MODE
Constant used to initialize cipher to encryption mode.
|
static int |
PRIVATE_KEY
Constant used to indicate the to-be-unwrapped key is a "private key".
|
static int |
PUBLIC_KEY
Constant used to indicate the to-be-unwrapped key is a "public key".
|
static int |
SECRET_KEY
Constant used to indicate the to-be-unwrapped key is a "secret key".
|
static int |
UNWRAP_MODE
Constant used to initialize cipher to key-unwrapping mode.
|
static int |
WRAP_MODE
Constant used to initialize cipher to key-wrapping mode.
|
| Modifier | Constructor and Description |
|---|---|
protected |
Cipher(CipherSpi cipherSpi,
Provider provider,
String transformation)
Creates a Cipher object.
|
| Modifier and Type | Method and Description |
|---|---|
byte[] |
doFinal()
Finishes a multiple-part encryption or decryption operation, depending
on how this cipher was initialized.
|
byte[] |
doFinal(byte[] input)
Encrypts or decrypts data in a single-part operation, or finishes a
multiple-part operation.
|
int |
doFinal(byte[] output,
int outputOffset)
Finishes a multiple-part encryption or decryption operation, depending
on how this cipher was initialized.
|
byte[] |
doFinal(byte[] input,
int inputOffset,
int inputLen)
Encrypts or decrypts data in a single-part operation, or finishes a
multiple-part operation.
|
int |
doFinal(byte[] input,
int inputOffset,
int inputLen,
byte[] output)
Encrypts or decrypts data in a single-part operation, or finishes a
multiple-part operation.
|
int |
doFinal(byte[] input,
int inputOffset,
int inputLen,
byte[] output,
int outputOffset)
Encrypts or decrypts data in a single-part operation, or finishes a
multiple-part operation.
|
int |
doFinal(ByteBuffer input,
ByteBuffer output)
Encrypts or decrypts data in a single-part operation, or finishes a
multiple-part operation.
|
String |
getAlgorithm()
Returns the algorithm name of this
Cipher object. |
int |
getBlockSize()
Returns the block size (in bytes).
|
ExemptionMechanism |
getExemptionMechanism()
Returns the exemption mechanism object used with this cipher.
|
static Cipher |
getInstance(String transformation)
Returns a
Cipher object that implements the specified
transformation. |
static Cipher |
getInstance(String transformation,
Provider provider)
Returns a
Cipher object that implements the specified
transformation. |
static Cipher |
getInstance(String transformation,
String provider)
Returns a
Cipher object that implements the specified
transformation. |
byte[] |
getIV()
Returns the initialization vector (IV) in a new buffer.
|
static int |
getMaxAllowedKeyLength(String transformation)
Returns the maximum key length for the specified transformation
according to the installed JCE jurisdiction policy files.
|
static AlgorithmParameterSpec |
getMaxAllowedParameterSpec(String transformation)
Returns an AlgorithmParameterSpec object which contains
the maximum cipher parameter value according to the
jurisdiction policy file.
|
int |
getOutputSize(int inputLen)
Returns the length in bytes that an output buffer would need to be in
order to hold the result of the next
update or
doFinal operation, given the input length
inputLen (in bytes). |
AlgorithmParameters |
getParameters()
Returns the parameters used with this cipher.
|
Provider |
getProvider()
Returns the provider of this
Cipher object. |
void |
init(int opmode,
Certificate certificate)
Initializes this cipher with the public key from the given certificate.
|
void |
init(int opmode,
Certificate certificate,
SecureRandom random)
Initializes this cipher with the public key from the given certificate
and
a source of randomness.
|
void |
init(int opmode,
Key key)
Initializes this cipher with a key.
|
void |
init(int opmode,
Key key,
AlgorithmParameters params)
Initializes this cipher with a key and a set of algorithm
parameters.
|
void |
init(int opmode,
Key key,
AlgorithmParameterSpec params)
Initializes this cipher with a key and a set of algorithm
parameters.
|
void |
init(int opmode,
Key key,
AlgorithmParameterSpec params,
SecureRandom random)
Initializes this cipher with a key, a set of algorithm
parameters, and a source of randomness.
|
void |
init(int opmode,
Key key,
AlgorithmParameters params,
SecureRandom random)
Initializes this cipher with a key, a set of algorithm
parameters, and a source of randomness.
|
void |
init(int opmode,
Key key,
SecureRandom random)
Initializes this cipher with a key and a source of randomness.
|
Key |
unwrap(byte[] wrappedKey,
String wrappedKeyAlgorithm,
int wrappedKeyType)
Unwrap a previously wrapped key.
|
byte[] |
update(byte[] input)
Continues a multiple-part encryption or decryption operation
(depending on how this cipher was initialized), processing another data
part.
|
byte[] |
update(byte[] input,
int inputOffset,
int inputLen)
Continues a multiple-part encryption or decryption operation
(depending on how this cipher was initialized), processing another data
part.
|
int |
update(byte[] input,
int inputOffset,
int inputLen,
byte[] output)
Continues a multiple-part encryption or decryption operation
(depending on how this cipher was initialized), processing another data
part.
|
int |
update(byte[] input,
int inputOffset,
int inputLen,
byte[] output,
int outputOffset)
Continues a multiple-part encryption or decryption operation
(depending on how this cipher was initialized), processing another data
part.
|
int |
update(ByteBuffer input,
ByteBuffer output)
Continues a multiple-part encryption or decryption operation
(depending on how this cipher was initialized), processing another data
part.
|
void |
updateAAD(byte[] src)
Continues a multi-part update of the Additional Authentication
Data (AAD).
|
void |
updateAAD(byte[] src,
int offset,
int len)
Continues a multi-part update of the Additional Authentication
Data (AAD), using a subset of the provided buffer.
|
void |
updateAAD(ByteBuffer src)
Continues a multi-part update of the Additional Authentication
Data (AAD).
|
byte[] |
wrap(Key key)
Wrap a key.
|
public static final int ENCRYPT_MODE
public static final int DECRYPT_MODE
public static final int WRAP_MODE
public static final int UNWRAP_MODE
public static final int PUBLIC_KEY
public static final int PRIVATE_KEY
public static final int SECRET_KEY
public static final Cipher getInstance(String transformation) throws NoSuchAlgorithmException, NoSuchPaddingException
Cipher
object that implements the specified
transformation.
This method traverses the list of registered security Providers, starting with the most preferred Provider. A new Cipher object encapsulating the CipherSpi implementation from the first Provider that supports the specified algorithm is returned.
Note that the list of registered providers may be retrieved via
the Security.getProviders()
method.
transformation
- the name of the transformation, e.g.,
DES/CBC/PKCS5Padding.
See the Cipher section in the
Java Cryptography Architecture Standard Algorithm Name Documentation
for information about standard transformation names.NoSuchAlgorithmException
- if transformation
is null, empty, in an invalid format,
or if no Provider supports a CipherSpi implementation for the
specified algorithm.NoSuchPaddingException
- if transformation
contains a padding scheme that is not available.Provider
public static final Cipher getInstance(String transformation, String provider) throws NoSuchAlgorithmException, NoSuchProviderException, NoSuchPaddingException
Cipher
object that implements the specified
transformation.
A new Cipher object encapsulating the CipherSpi implementation from the specified provider is returned. The specified provider must be registered in the security provider list.
Note that the list of registered providers may be retrieved via
the Security.getProviders()
method.
transformation
- the name of the transformation,
e.g., DES/CBC/PKCS5Padding.
See the Cipher section in the
Java Cryptography Architecture Standard Algorithm Name Documentation
for information about standard transformation names.provider
- the name of the provider.NoSuchAlgorithmException
- if transformation
is null, empty, in an invalid format,
or if a CipherSpi implementation for the specified algorithm
is not available from the specified provider.NoSuchProviderException
- if the specified provider is not
registered in the security provider list.NoSuchPaddingException
- if transformation
contains a padding scheme that is not available.IllegalArgumentException
- if the provider
is null or empty.Provider
public static final Cipher getInstance(String transformation, Provider provider) throws NoSuchAlgorithmException, NoSuchPaddingException
Cipher
object that implements the specified
transformation.
A new Cipher object encapsulating the CipherSpi implementation from the specified Provider object is returned. Note that the specified Provider object does not have to be registered in the provider list.
transformation
- the name of the transformation,
e.g., DES/CBC/PKCS5Padding.
See the Cipher section in the
Java Cryptography Architecture Standard Algorithm Name Documentation
for information about standard transformation names.provider
- the provider.NoSuchAlgorithmException
- if transformation
is null, empty, in an invalid format,
or if a CipherSpi implementation for the specified algorithm
is not available from the specified Provider object.NoSuchPaddingException
- if transformation
contains a padding scheme that is not available.IllegalArgumentException
- if the provider
is null.Provider
public final Provider getProvider()
Cipher
object.Cipher
objectpublic final String getAlgorithm()
Cipher
object.
This is the same name that was specified in one of the
getInstance
calls that created this Cipher
object..
Cipher
object.public final int getBlockSize()
public final int getOutputSize(int inputLen)
update
or
doFinal
operation, given the input length
inputLen
(in bytes).
This call takes into account any unprocessed (buffered) data from a
previous update
call, padding, and AEAD tagging.
The actual output length of the next update
or
doFinal
call may be smaller than the length returned by
this method.
inputLen
- the input length (in bytes)IllegalStateException
- if this cipher is in a wrong state
(e.g., has not yet been initialized)public final byte[] getIV()
This is useful in the case where a random IV was created, or in the context of password-based encryption or decryption, where the IV is derived from a user-supplied password.
public final AlgorithmParameters getParameters()
The returned parameters may be the same that were used to initialize this cipher, or may contain a combination of default and random parameter values used by the underlying cipher implementation if this cipher requires algorithm parameters but was not initialized with any.
public final ExemptionMechanism getExemptionMechanism()
public final void init(int opmode, Key key) throws InvalidKeyException
The cipher is initialized for one of the following four operations:
encryption, decryption, key wrapping or key unwrapping, depending
on the value of opmode
.
If this cipher requires any algorithm parameters that cannot be
derived from the given key
, the underlying cipher
implementation is supposed to generate the required parameters itself
(using provider-specific default or random values) if it is being
initialized for encryption or key wrapping, and raise an
InvalidKeyException
if it is being
initialized for decryption or key unwrapping.
The generated parameters can be retrieved using
getParameters
or
getIV
(if the parameter is an IV).
If this cipher requires algorithm parameters that cannot be derived from the input parameters, and there are no reasonable provider-specific default values, initialization will necessarily fail.
If this cipher (including its underlying feedback or padding scheme)
requires any random bytes (e.g., for parameter generation), it will get
them using the
implementation of the highest-priority
installed provider as the source of randomness.
(If none of the installed providers supply an implementation of
SecureRandom, a system-provided source of randomness will be used.)
SecureRandom
Note that when a Cipher object is initialized, it loses all previously-acquired state. In other words, initializing a Cipher is equivalent to creating a new instance of that Cipher and initializing it.
opmode
- the operation mode of this cipher (this is one of
the following:
ENCRYPT_MODE
, DECRYPT_MODE
,
WRAP_MODE
or UNWRAP_MODE
)key
- the keyInvalidKeyException
- if the given key is inappropriate for
initializing this cipher, or requires
algorithm parameters that cannot be
determined from the given key, or if the given key has a keysize that
exceeds the maximum allowable keysize (as determined from the
configured jurisdiction policy files).public final void init(int opmode, Key key, SecureRandom random) throws InvalidKeyException
The cipher is initialized for one of the following four operations:
encryption, decryption, key wrapping or key unwrapping, depending
on the value of opmode
.
If this cipher requires any algorithm parameters that cannot be
derived from the given key
, the underlying cipher
implementation is supposed to generate the required parameters itself
(using provider-specific default or random values) if it is being
initialized for encryption or key wrapping, and raise an
InvalidKeyException
if it is being
initialized for decryption or key unwrapping.
The generated parameters can be retrieved using
getParameters
or
getIV
(if the parameter is an IV).
If this cipher requires algorithm parameters that cannot be derived from the input parameters, and there are no reasonable provider-specific default values, initialization will necessarily fail.
If this cipher (including its underlying feedback or padding scheme)
requires any random bytes (e.g., for parameter generation), it will get
them from random
.
Note that when a Cipher object is initialized, it loses all previously-acquired state. In other words, initializing a Cipher is equivalent to creating a new instance of that Cipher and initializing it.
opmode
- the operation mode of this cipher (this is one of the
following:
ENCRYPT_MODE
, DECRYPT_MODE
,
WRAP_MODE
or UNWRAP_MODE
)key
- the encryption keyrandom
- the source of randomnessInvalidKeyException
- if the given key is inappropriate for
initializing this cipher, or requires
algorithm parameters that cannot be
determined from the given key, or if the given key has a keysize that
exceeds the maximum allowable keysize (as determined from the
configured jurisdiction policy files).public final void init(int opmode, Key key, AlgorithmParameterSpec params) throws InvalidKeyException, InvalidAlgorithmParameterException
The cipher is initialized for one of the following four operations:
encryption, decryption, key wrapping or key unwrapping, depending
on the value of opmode
.
If this cipher requires any algorithm parameters and
params
is null, the underlying cipher implementation is
supposed to generate the required parameters itself (using
provider-specific default or random values) if it is being
initialized for encryption or key wrapping, and raise an
InvalidAlgorithmParameterException
if it is being
initialized for decryption or key unwrapping.
The generated parameters can be retrieved using
getParameters
or
getIV
(if the parameter is an IV).
If this cipher requires algorithm parameters that cannot be derived from the input parameters, and there are no reasonable provider-specific default values, initialization will necessarily fail.
If this cipher (including its underlying feedback or padding scheme)
requires any random bytes (e.g., for parameter generation), it will get
them using the
implementation of the highest-priority
installed provider as the source of randomness.
(If none of the installed providers supply an implementation of
SecureRandom, a system-provided source of randomness will be used.)
SecureRandom
Note that when a Cipher object is initialized, it loses all previously-acquired state. In other words, initializing a Cipher is equivalent to creating a new instance of that Cipher and initializing it.
opmode
- the operation mode of this cipher (this is one of the
following:
ENCRYPT_MODE
, DECRYPT_MODE
,
WRAP_MODE
or UNWRAP_MODE
)key
- the encryption keyparams
- the algorithm parametersInvalidKeyException
- if the given key is inappropriate for
initializing this cipher, or its keysize exceeds the maximum allowable
keysize (as determined from the configured jurisdiction policy files).InvalidAlgorithmParameterException
- if the given algorithm
parameters are inappropriate for this cipher,
or this cipher requires
algorithm parameters and params
is null, or the given
algorithm parameters imply a cryptographic strength that would exceed
the legal limits (as determined from the configured jurisdiction
policy files).public final void init(int opmode, Key key, AlgorithmParameterSpec params, SecureRandom random) throws InvalidKeyException, InvalidAlgorithmParameterException
The cipher is initialized for one of the following four operations:
encryption, decryption, key wrapping or key unwrapping, depending
on the value of opmode
.
If this cipher requires any algorithm parameters and
params
is null, the underlying cipher implementation is
supposed to generate the required parameters itself (using
provider-specific default or random values) if it is being
initialized for encryption or key wrapping, and raise an
InvalidAlgorithmParameterException
if it is being
initialized for decryption or key unwrapping.
The generated parameters can be retrieved using
getParameters
or
getIV
(if the parameter is an IV).
If this cipher requires algorithm parameters that cannot be derived from the input parameters, and there are no reasonable provider-specific default values, initialization will necessarily fail.
If this cipher (including its underlying feedback or padding scheme)
requires any random bytes (e.g., for parameter generation), it will get
them from random
.
Note that when a Cipher object is initialized, it loses all previously-acquired state. In other words, initializing a Cipher is equivalent to creating a new instance of that Cipher and initializing it.
opmode
- the operation mode of this cipher (this is one of the
following:
ENCRYPT_MODE
, DECRYPT_MODE
,
WRAP_MODE
or UNWRAP_MODE
)key
- the encryption keyparams
- the algorithm parametersrandom
- the source of randomnessInvalidKeyException
- if the given key is inappropriate for
initializing this cipher, or its keysize exceeds the maximum allowable
keysize (as determined from the configured jurisdiction policy files).InvalidAlgorithmParameterException
- if the given algorithm
parameters are inappropriate for this cipher,
or this cipher requires
algorithm parameters and params
is null, or the given
algorithm parameters imply a cryptographic strength that would exceed
the legal limits (as determined from the configured jurisdiction
policy files).public final void init(int opmode, Key key, AlgorithmParameters params) throws InvalidKeyException, InvalidAlgorithmParameterException
The cipher is initialized for one of the following four operations:
encryption, decryption, key wrapping or key unwrapping, depending
on the value of opmode
.
If this cipher requires any algorithm parameters and
params
is null, the underlying cipher implementation is
supposed to generate the required parameters itself (using
provider-specific default or random values) if it is being
initialized for encryption or key wrapping, and raise an
InvalidAlgorithmParameterException
if it is being
initialized for decryption or key unwrapping.
The generated parameters can be retrieved using
getParameters
or
getIV
(if the parameter is an IV).
If this cipher requires algorithm parameters that cannot be derived from the input parameters, and there are no reasonable provider-specific default values, initialization will necessarily fail.
If this cipher (including its underlying feedback or padding scheme)
requires any random bytes (e.g., for parameter generation), it will get
them using the
implementation of the highest-priority
installed provider as the source of randomness.
(If none of the installed providers supply an implementation of
SecureRandom, a system-provided source of randomness will be used.)
SecureRandom
Note that when a Cipher object is initialized, it loses all previously-acquired state. In other words, initializing a Cipher is equivalent to creating a new instance of that Cipher and initializing it.
opmode
- the operation mode of this cipher (this is one of the
following: ENCRYPT_MODE
,
DECRYPT_MODE
, WRAP_MODE
or UNWRAP_MODE
)key
- the encryption keyparams
- the algorithm parametersInvalidKeyException
- if the given key is inappropriate for
initializing this cipher, or its keysize exceeds the maximum allowable
keysize (as determined from the configured jurisdiction policy files).InvalidAlgorithmParameterException
- if the given algorithm
parameters are inappropriate for this cipher,
or this cipher requires
algorithm parameters and params
is null, or the given
algorithm parameters imply a cryptographic strength that would exceed
the legal limits (as determined from the configured jurisdiction
policy files).public final void init(int opmode, Key key, AlgorithmParameters params, SecureRandom random) throws InvalidKeyException, InvalidAlgorithmParameterException
The cipher is initialized for one of the following four operations:
encryption, decryption, key wrapping or key unwrapping, depending
on the value of opmode
.
If this cipher requires any algorithm parameters and
params
is null, the underlying cipher implementation is
supposed to generate the required parameters itself (using
provider-specific default or random values) if it is being
initialized for encryption or key wrapping, and raise an
InvalidAlgorithmParameterException
if it is being
initialized for decryption or key unwrapping.
The generated parameters can be retrieved using
getParameters
or
getIV
(if the parameter is an IV).
If this cipher requires algorithm parameters that cannot be derived from the input parameters, and there are no reasonable provider-specific default values, initialization will necessarily fail.
If this cipher (including its underlying feedback or padding scheme)
requires any random bytes (e.g., for parameter generation), it will get
them from random
.
Note that when a Cipher object is initialized, it loses all previously-acquired state. In other words, initializing a Cipher is equivalent to creating a new instance of that Cipher and initializing it.
opmode
- the operation mode of this cipher (this is one of the
following: ENCRYPT_MODE
,
DECRYPT_MODE
, WRAP_MODE
or UNWRAP_MODE
)key
- the encryption keyparams
- the algorithm parametersrandom
- the source of randomnessInvalidKeyException
- if the given key is inappropriate for
initializing this cipher, or its keysize exceeds the maximum allowable
keysize (as determined from the configured jurisdiction policy files).InvalidAlgorithmParameterException
- if the given algorithm
parameters are inappropriate for this cipher,
or this cipher requires
algorithm parameters and params
is null, or the given
algorithm parameters imply a cryptographic strength that would exceed
the legal limits (as determined from the configured jurisdiction
policy files).public final void init(int opmode, Certificate certificate) throws InvalidKeyException
The cipher is initialized for one of the following four operations:
encryption, decryption, key wrapping or key unwrapping, depending
on the value of opmode
.
If the certificate is of type X.509 and has a key usage
extension field marked as critical, and the value of the key usage
extension field implies that the public key in
the certificate and its corresponding private key are not
supposed to be used for the operation represented by the value
of opmode
,
an InvalidKeyException
is thrown.
If this cipher requires any algorithm parameters that cannot be
derived from the public key in the given certificate, the underlying
cipher
implementation is supposed to generate the required parameters itself
(using provider-specific default or random values) if it is being
initialized for encryption or key wrapping, and raise an
InvalidKeyException
if it is being initialized for decryption or
key unwrapping.
The generated parameters can be retrieved using
getParameters
or
getIV
(if the parameter is an IV).
If this cipher requires algorithm parameters that cannot be derived from the input parameters, and there are no reasonable provider-specific default values, initialization will necessarily fail.
If this cipher (including its underlying feedback or padding scheme)
requires any random bytes (e.g., for parameter generation), it will get
them using the
SecureRandom
implementation of the highest-priority
installed provider as the source of randomness.
(If none of the installed providers supply an implementation of
SecureRandom, a system-provided source of randomness will be used.)
Note that when a Cipher object is initialized, it loses all previously-acquired state. In other words, initializing a Cipher is equivalent to creating a new instance of that Cipher and initializing it.
opmode
- the operation mode of this cipher (this is one of the
following:
ENCRYPT_MODE
, DECRYPT_MODE
,
WRAP_MODE
or UNWRAP_MODE
)certificate
- the certificateInvalidKeyException
- if the public key in the given
certificate is inappropriate for initializing this cipher, or this
cipher requires algorithm parameters that cannot be determined from the
public key in the given certificate, or the keysize of the public key
in the given certificate has a keysize that exceeds the maximum
allowable keysize (as determined by the configured jurisdiction policy
files).public final void init(int opmode, Certificate certificate, SecureRandom random) throws InvalidKeyException
The cipher is initialized for one of the following four operations:
encryption, decryption, key wrapping
or key unwrapping, depending on
the value of opmode
.
If the certificate is of type X.509 and has a key usage
extension field marked as critical, and the value of the key usage
extension field implies that the public key in
the certificate and its corresponding private key are not
supposed to be used for the operation represented by the value of
opmode
,
an InvalidKeyException
is thrown.
If this cipher requires any algorithm parameters that cannot be
derived from the public key in the given certificate
,
the underlying cipher
implementation is supposed to generate the required parameters itself
(using provider-specific default or random values) if it is being
initialized for encryption or key wrapping, and raise an
InvalidKeyException
if it is being
initialized for decryption or key unwrapping.
The generated parameters can be retrieved using
getParameters
or
getIV
(if the parameter is an IV).
If this cipher requires algorithm parameters that cannot be derived from the input parameters, and there are no reasonable provider-specific default values, initialization will necessarily fail.
If this cipher (including its underlying feedback or padding scheme)
requires any random bytes (e.g., for parameter generation), it will get
them from random
.
Note that when a Cipher object is initialized, it loses all previously-acquired state. In other words, initializing a Cipher is equivalent to creating a new instance of that Cipher and initializing it.
opmode
- the operation mode of this cipher (this is one of the
following:
ENCRYPT_MODE
, DECRYPT_MODE
,
WRAP_MODE
or UNWRAP_MODE
)certificate
- the certificaterandom
- the source of randomnessInvalidKeyException
- if the public key in the given
certificate is inappropriate for initializing this cipher, or this
cipher
requires algorithm parameters that cannot be determined from the
public key in the given certificate, or the keysize of the public key
in the given certificate has a keysize that exceeds the maximum
allowable keysize (as determined by the configured jurisdiction policy
files).public final byte[] update(byte[] input)
The bytes in the input
buffer are processed, and the
result is stored in a new buffer.
If input
has a length of zero, this method returns
null
.
input
- the input bufferIllegalStateException
- if this cipher is in a wrong state
(e.g., has not been initialized)public final byte[] update(byte[] input, int inputOffset, int inputLen)
The first inputLen
bytes in the input
buffer, starting at inputOffset
inclusive, are processed,
and the result is stored in a new buffer.
If inputLen
is zero, this method returns
null
.
input
- the input bufferinputOffset
- the offset in input
where the input
startsinputLen
- the input lengthIllegalStateException
- if this cipher is in a wrong state
(e.g., has not been initialized)public final int update(byte[] input, int inputOffset, int inputLen, byte[] output) throws ShortBufferException
The first inputLen
bytes in the input
buffer, starting at inputOffset
inclusive, are processed,
and the result is stored in the output
buffer.
If the output
buffer is too small to hold the result,
a ShortBufferException
is thrown. In this case, repeat this
call with a larger output buffer. Use
getOutputSize
to determine how big
the output buffer should be.
If inputLen
is zero, this method returns
a length of zero.
Note: this method should be copy-safe, which means the
input
and output
buffers can reference
the same byte array and no unprocessed input data is overwritten
when the result is copied into the output buffer.
input
- the input bufferinputOffset
- the offset in input
where the input
startsinputLen
- the input lengthoutput
- the buffer for the resultoutput
IllegalStateException
- if this cipher is in a wrong state
(e.g., has not been initialized)ShortBufferException
- if the given output buffer is too small
to hold the resultpublic final int update(byte[] input, int inputOffset, int inputLen, byte[] output, int outputOffset) throws ShortBufferException
The first inputLen
bytes in the input
buffer, starting at inputOffset
inclusive, are processed,
and the result is stored in the output
buffer, starting at
outputOffset
inclusive.
If the output
buffer is too small to hold the result,
a ShortBufferException
is thrown. In this case, repeat this
call with a larger output buffer. Use
getOutputSize
to determine how big
the output buffer should be.
If inputLen
is zero, this method returns
a length of zero.
Note: this method should be copy-safe, which means the
input
and output
buffers can reference
the same byte array and no unprocessed input data is overwritten
when the result is copied into the output buffer.
input
- the input bufferinputOffset
- the offset in input
where the input
startsinputLen
- the input lengthoutput
- the buffer for the resultoutputOffset
- the offset in output
where the result
is storedoutput
IllegalStateException
- if this cipher is in a wrong state
(e.g., has not been initialized)ShortBufferException
- if the given output buffer is too small
to hold the resultpublic final int update(ByteBuffer input, ByteBuffer output) throws ShortBufferException
All input.remaining()
bytes starting at
input.position()
are processed. The result is stored
in the output buffer.
Upon return, the input buffer's position will be equal
to its limit; its limit will not have changed. The output buffer's
position will have advanced by n, where n is the value returned
by this method; the output buffer's limit will not have changed.
If output.remaining()
bytes are insufficient to
hold the result, a ShortBufferException
is thrown.
In this case, repeat this call with a larger output buffer. Use
getOutputSize
to determine how big
the output buffer should be.
Note: this method should be copy-safe, which means the
input
and output
buffers can reference
the same block of memory and no unprocessed input data is overwritten
when the result is copied into the output buffer.
input
- the input ByteBufferoutput
- the output ByteByfferoutput
IllegalStateException
- if this cipher is in a wrong state
(e.g., has not been initialized)IllegalArgumentException
- if input and output are the
same objectReadOnlyBufferException
- if the output buffer is read-onlyShortBufferException
- if there is insufficient space in the
output bufferpublic final byte[] doFinal() throws IllegalBlockSizeException, BadPaddingException
Input data that may have been buffered during a previous
update
operation is processed, with padding (if requested)
being applied.
If an AEAD mode such as GCM/CCM is being used, the authentication
tag is appended in the case of encryption, or verified in the
case of decryption.
The result is stored in a new buffer.
Upon finishing, this method resets this cipher object to the state
it was in when previously initialized via a call to init
.
That is, the object is reset and available to encrypt or decrypt
(depending on the operation mode that was specified in the call to
init
) more data.
Note: if any exception is thrown, this cipher object may need to be reset before it can be used again.
IllegalStateException
- if this cipher is in a wrong state
(e.g., has not been initialized)IllegalBlockSizeException
- if this cipher is a block cipher,
no padding has been requested (only in encryption mode), and the total
input length of the data processed by this cipher is not a multiple of
block size; or if this encryption algorithm is unable to
process the input data provided.BadPaddingException
- if this cipher is in decryption mode,
and (un)padding has been requested, but the decrypted data is not
bounded by the appropriate padding bytesAEADBadTagException
- if this cipher is decrypting in an
AEAD mode (such as GCM/CCM), and the received authentication tag
does not match the calculated valuepublic final int doFinal(byte[] output, int outputOffset) throws IllegalBlockSizeException, ShortBufferException, BadPaddingException
Input data that may have been buffered during a previous
update
operation is processed, with padding (if requested)
being applied.
If an AEAD mode such as GCM/CCM is being used, the authentication
tag is appended in the case of encryption, or verified in the
case of decryption.
The result is stored in the output
buffer, starting at
outputOffset
inclusive.
If the output
buffer is too small to hold the result,
a ShortBufferException
is thrown. In this case, repeat this
call with a larger output buffer. Use
getOutputSize
to determine how big
the output buffer should be.
Upon finishing, this method resets this cipher object to the state
it was in when previously initialized via a call to init
.
That is, the object is reset and available to encrypt or decrypt
(depending on the operation mode that was specified in the call to
init
) more data.
Note: if any exception is thrown, this cipher object may need to be reset before it can be used again.
output
- the buffer for the resultoutputOffset
- the offset in output
where the result
is storedoutput
IllegalStateException
- if this cipher is in a wrong state
(e.g., has not been initialized)IllegalBlockSizeException
- if this cipher is a block cipher,
no padding has been requested (only in encryption mode), and the total
input length of the data processed by this cipher is not a multiple of
block size; or if this encryption algorithm is unable to
process the input data provided.ShortBufferException
- if the given output buffer is too small
to hold the resultBadPaddingException
- if this cipher is in decryption mode,
and (un)padding has been requested, but the decrypted data is not
bounded by the appropriate padding bytesAEADBadTagException
- if this cipher is decrypting in an
AEAD mode (such as GCM/CCM), and the received authentication tag
does not match the calculated valuepublic final byte[] doFinal(byte[] input) throws IllegalBlockSizeException, BadPaddingException
The bytes in the input
buffer, and any input bytes that
may have been buffered during a previous update
operation,
are processed, with padding (if requested) being applied.
If an AEAD mode such as GCM/CCM is being used, the authentication
tag is appended in the case of encryption, or verified in the
case of decryption.
The result is stored in a new buffer.
Upon finishing, this method resets this cipher object to the state
it was in when previously initialized via a call to init
.
That is, the object is reset and available to encrypt or decrypt
(depending on the operation mode that was specified in the call to
init
) more data.
Note: if any exception is thrown, this cipher object may need to be reset before it can be used again.
input
- the input bufferIllegalStateException
- if this cipher is in a wrong state
(e.g., has not been initialized)IllegalBlockSizeException
- if this cipher is a block cipher,
no padding has been requested (only in encryption mode), and the total
input length of the data processed by this cipher is not a multiple of
block size; or if this encryption algorithm is unable to
process the input data provided.BadPaddingException
- if this cipher is in decryption mode,
and (un)padding has been requested, but the decrypted data is not
bounded by the appropriate padding bytesAEADBadTagException
- if this cipher is decrypting in an
AEAD mode (such as GCM/CCM), and the received authentication tag
does not match the calculated valuepublic final byte[] doFinal(byte[] input, int inputOffset, int inputLen) throws IllegalBlockSizeException, BadPaddingException
The first inputLen
bytes in the input
buffer, starting at inputOffset
inclusive, and any input
bytes that may have been buffered during a previous update
operation, are processed, with padding (if requested) being applied.
If an AEAD mode such as GCM/CCM is being used, the authentication
tag is appended in the case of encryption, or verified in the
case of decryption.
The result is stored in a new buffer.
Upon finishing, this method resets this cipher object to the state
it was in when previously initialized via a call to init
.
That is, the object is reset and available to encrypt or decrypt
(depending on the operation mode that was specified in the call to
init
) more data.
Note: if any exception is thrown, this cipher object may need to be reset before it can be used again.
input
- the input bufferinputOffset
- the offset in input
where the input
startsinputLen
- the input lengthIllegalStateException
- if this cipher is in a wrong state
(e.g., has not been initialized)IllegalBlockSizeException
- if this cipher is a block cipher,
no padding has been requested (only in encryption mode), and the total
input length of the data processed by this cipher is not a multiple of
block size; or if this encryption algorithm is unable to
process the input data provided.BadPaddingException
- if this cipher is in decryption mode,
and (un)padding has been requested, but the decrypted data is not
bounded by the appropriate padding bytesAEADBadTagException
- if this cipher is decrypting in an
AEAD mode (such as GCM/CCM), and the received authentication tag
does not match the calculated valuepublic final int doFinal(byte[] input, int inputOffset, int inputLen, byte[] output) throws ShortBufferException, IllegalBlockSizeException, BadPaddingException
The first inputLen
bytes in the input
buffer, starting at inputOffset
inclusive, and any input
bytes that may have been buffered during a previous update
operation, are processed, with padding (if requested) being applied.
If an AEAD mode such as GCM/CCM is being used, the authentication
tag is appended in the case of encryption, or verified in the
case of decryption.
The result is stored in the output
buffer.
If the output
buffer is too small to hold the result,
a ShortBufferException
is thrown. In this case, repeat this
call with a larger output buffer. Use
getOutputSize
to determine how big
the output buffer should be.
Upon finishing, this method resets this cipher object to the state
it was in when previously initialized via a call to init
.
That is, the object is reset and available to encrypt or decrypt
(depending on the operation mode that was specified in the call to
init
) more data.
Note: if any exception is thrown, this cipher object may need to be reset before it can be used again.
Note: this method should be copy-safe, which means the
input
and output
buffers can reference
the same byte array and no unprocessed input data is overwritten
when the result is copied into the output buffer.
input
- the input bufferinputOffset
- the offset in input
where the input
startsinputLen
- the input lengthoutput
- the buffer for the resultoutput
IllegalStateException
- if this cipher is in a wrong state
(e.g., has not been initialized)IllegalBlockSizeException
- if this cipher is a block cipher,
no padding has been requested (only in encryption mode), and the total
input length of the data processed by this cipher is not a multiple of
block size; or if this encryption algorithm is unable to
process the input data provided.ShortBufferException
- if the given output buffer is too small
to hold the resultBadPaddingException
- if this cipher is in decryption mode,
and (un)padding has been requested, but the decrypted data is not
bounded by the appropriate padding bytesAEADBadTagException
- if this cipher is decrypting in an
AEAD mode (such as GCM/CCM), and the received authentication tag
does not match the calculated valuepublic final int doFinal(byte[] input, int inputOffset, int inputLen, byte[] output, int outputOffset) throws ShortBufferException, IllegalBlockSizeException, BadPaddingException
The first inputLen
bytes in the input
buffer, starting at inputOffset
inclusive, and any input
bytes that may have been buffered during a previous
update
operation, are processed, with padding
(if requested) being applied.
If an AEAD mode such as GCM/CCM is being used, the authentication
tag is appended in the case of encryption, or verified in the
case of decryption.
The result is stored in the output
buffer, starting at
outputOffset
inclusive.
If the output
buffer is too small to hold the result,
a ShortBufferException
is thrown. In this case, repeat this
call with a larger output buffer. Use
getOutputSize
to determine how big
the output buffer should be.
Upon finishing, this method resets this cipher object to the state
it was in when previously initialized via a call to init
.
That is, the object is reset and available to encrypt or decrypt
(depending on the operation mode that was specified in the call to
init
) more data.
Note: if any exception is thrown, this cipher object may need to be reset before it can be used again.
Note: this method should be copy-safe, which means the
input
and output
buffers can reference
the same byte array and no unprocessed input data is overwritten
when the result is copied into the output buffer.
input
- the input bufferinputOffset
- the offset in input
where the input
startsinputLen
- the input lengthoutput
- the buffer for the resultoutputOffset
- the offset in output
where the result
is storedoutput
IllegalStateException
- if this cipher is in a wrong state
(e.g., has not been initialized)IllegalBlockSizeException
- if this cipher is a block cipher,
no padding has been requested (only in encryption mode), and the total
input length of the data processed by this cipher is not a multiple of
block size; or if this encryption algorithm is unable to
process the input data provided.ShortBufferException
- if the given output buffer is too small
to hold the resultBadPaddingException
- if this cipher is in decryption mode,
and (un)padding has been requested, but the decrypted data is not
bounded by the appropriate padding bytesAEADBadTagException
- if this cipher is decrypting in an
AEAD mode (such as GCM/CCM), and the received authentication tag
does not match the calculated valuepublic final int doFinal(ByteBuffer input, ByteBuffer output) throws ShortBufferException, IllegalBlockSizeException, BadPaddingException
All input.remaining()
bytes starting at
input.position()
are processed.
If an AEAD mode such as GCM/CCM is being used, the authentication
tag is appended in the case of encryption, or verified in the
case of decryption.
The result is stored in the output buffer.
Upon return, the input buffer's position will be equal
to its limit; its limit will not have changed. The output buffer's
position will have advanced by n, where n is the value returned
by this method; the output buffer's limit will not have changed.
If output.remaining()
bytes are insufficient to
hold the result, a ShortBufferException
is thrown.
In this case, repeat this call with a larger output buffer. Use
getOutputSize
to determine how big
the output buffer should be.
Upon finishing, this method resets this cipher object to the state
it was in when previously initialized via a call to init
.
That is, the object is reset and available to encrypt or decrypt
(depending on the operation mode that was specified in the call to
init
) more data.
Note: if any exception is thrown, this cipher object may need to be reset before it can be used again.
Note: this method should be copy-safe, which means the
input
and output
buffers can reference
the same byte array and no unprocessed input data is overwritten
when the result is copied into the output buffer.
input
- the input ByteBufferoutput
- the output ByteBufferoutput
IllegalStateException
- if this cipher is in a wrong state
(e.g., has not been initialized)IllegalArgumentException
- if input and output are the
same objectReadOnlyBufferException
- if the output buffer is read-onlyIllegalBlockSizeException
- if this cipher is a block cipher,
no padding has been requested (only in encryption mode), and the total
input length of the data processed by this cipher is not a multiple of
block size; or if this encryption algorithm is unable to
process the input data provided.ShortBufferException
- if there is insufficient space in the
output bufferBadPaddingException
- if this cipher is in decryption mode,
and (un)padding has been requested, but the decrypted data is not
bounded by the appropriate padding bytesAEADBadTagException
- if this cipher is decrypting in an
AEAD mode (such as GCM/CCM), and the received authentication tag
does not match the calculated valuepublic final byte[] wrap(Key key) throws IllegalBlockSizeException, InvalidKeyException
key
- the key to be wrapped.IllegalStateException
- if this cipher is in a wrong
state (e.g., has not been initialized).IllegalBlockSizeException
- if this cipher is a block
cipher, no padding has been requested, and the length of the
encoding of the key to be wrapped is not a
multiple of the block size.InvalidKeyException
- if it is impossible or unsafe to
wrap the key with this cipher (e.g., a hardware protected key is
being passed to a software-only cipher).public final Key unwrap(byte[] wrappedKey, String wrappedKeyAlgorithm, int wrappedKeyType) throws InvalidKeyException, NoSuchAlgorithmException
wrappedKey
- the key to be unwrapped.wrappedKeyAlgorithm
- the algorithm associated with the wrapped
key.wrappedKeyType
- the type of the wrapped key. This must be one of
SECRET_KEY
, PRIVATE_KEY
, or
PUBLIC_KEY
.IllegalStateException
- if this cipher is in a wrong state
(e.g., has not been initialized).NoSuchAlgorithmException
- if no installed providers
can create keys of type wrappedKeyType
for the
wrappedKeyAlgorithm
.InvalidKeyException
- if wrappedKey
does not
represent a wrapped key of type wrappedKeyType
for
the wrappedKeyAlgorithm
.public static final int getMaxAllowedKeyLength(String transformation) throws NoSuchAlgorithmException
transformation
- the cipher transformation.NullPointerException
- if transformation
is null.NoSuchAlgorithmException
- if transformation
is not a valid transformation, i.e. in the form of "algorithm" or
"algorithm/mode/padding".public static final AlgorithmParameterSpec getMaxAllowedParameterSpec(String transformation) throws NoSuchAlgorithmException
transformation
- the cipher transformation.NullPointerException
- if transformation
is null.NoSuchAlgorithmException
- if transformation
is not a valid transformation, i.e. in the form of "algorithm" or
"algorithm/mode/padding".public final void updateAAD(byte[] src)
Calls to this method provide AAD to the cipher when operating in
modes such as AEAD (GCM/CCM). If this cipher is operating in
either GCM or CCM mode, all AAD must be supplied before beginning
operations on the ciphertext (via the update
and doFinal
methods).
src
- the buffer containing the Additional Authentication DataIllegalArgumentException
- if the src
byte array is nullIllegalStateException
- if this cipher is in a wrong state
(e.g., has not been initialized), does not accept AAD, or if
operating in either GCM or CCM mode and one of the update
methods has already been called for the active
encryption/decryption operationUnsupportedOperationException
- if the corresponding method
in the CipherSpi
has not been overridden by an
implementationpublic final void updateAAD(byte[] src, int offset, int len)
Calls to this method provide AAD to the cipher when operating in
modes such as AEAD (GCM/CCM). If this cipher is operating in
either GCM or CCM mode, all AAD must be supplied before beginning
operations on the ciphertext (via the update
and doFinal
methods).
src
- the buffer containing the AADoffset
- the offset in src
where the AAD input startslen
- the number of AAD bytesIllegalArgumentException
- if the src
byte array is null, or the offset
or length
is less than 0, or the sum of the offset
and
len
is greater than the length of the
src
byte arrayIllegalStateException
- if this cipher is in a wrong state
(e.g., has not been initialized), does not accept AAD, or if
operating in either GCM or CCM mode and one of the update
methods has already been called for the active
encryption/decryption operationUnsupportedOperationException
- if the corresponding method
in the CipherSpi
has not been overridden by an
implementationpublic final void updateAAD(ByteBuffer src)
Calls to this method provide AAD to the cipher when operating in
modes such as AEAD (GCM/CCM). If this cipher is operating in
either GCM or CCM mode, all AAD must be supplied before beginning
operations on the ciphertext (via the update
and doFinal
methods).
All src.remaining()
bytes starting at
src.position()
are processed.
Upon return, the input buffer's position will be equal
to its limit; its limit will not have changed.
src
- the buffer containing the AADIllegalArgumentException
- if the src ByteBuffer
is nullIllegalStateException
- if this cipher is in a wrong state
(e.g., has not been initialized), does not accept AAD, or if
operating in either GCM or CCM mode and one of the update
methods has already been called for the active
encryption/decryption operationUnsupportedOperationException
- if the corresponding method
in the CipherSpi
has not been overridden by an
implementation Submit a bug or feature
For further API reference and developer documentation, see Java SE Documentation. That documentation contains more detailed, developer-targeted descriptions, with conceptual overviews, definitions of terms, workarounds, and working code examples.
Copyright © 1993, 2015, Oracle and/or its affiliates. All rights reserved.


| Sr | Fieldname | Type | Label | Options |
|---|---|---|---|---|
| 1 | send_autonotification_for |
Section Break |
Prompt for Email on Submission of
When any of the checked transactions are "Submitted", an email pop-up automatically opened to send an email to the associated "Contact" in that transaction, with the transaction as an attachment. The user may or may not send the email. |
|
| 2 | sales |
Column Break | Sales | |
| 3 | quotation |
Check | Quotation | |
| 4 | sales_order |
Check | Sales Order | |
| 5 | delivery_note |
Check | Delivery Note | |
| 6 | sales_invoice |
Check | Sales Invoice | |
| 7 | purchase |
Column Break | Purchase | |
| 8 | purchase_order |
Check | Purchase Order | |
| 9 | purchase_receipt |
Check | Purchase Receipt | |
| 10 | expense_claim |
Check | Expense Claim | |
| 11 | customize_the_notification |
Section Break |
Customize the Notification
Customize the introductory text that goes as a part of that email. Each transaction has a separate introductory text. |
|
| 12 | select_transaction |
Select | Select Transaction |
Quotation Sales Order Delivery Note Sales Invoice Purchase Order Purchase Receipt Expense Claim Expense Claim Approved Expense Claim Rejected |
| 13 | custom_message |
Text Editor | Custom Message | |
| 14 | quotation_message |
Text | Quotation Message | |
| 15 | sales_order_message |
Text | Sales Order Message | |
| 16 | delivery_note_message |
Text | Delivery Note Message | |
| 17 | sales_invoice_message |
Text | Sales Invoice Message | |
| 18 | purchase_order_message |
Text | Purchase Order Message | |
| 19 | purchase_receipt_message |
Text | Purchase Receipt Message | |
| 20 | expense_claim_approved_message |
Text | Expense Claim Approved Message | |
| 21 | expense_claim_rejected_message |
Text | Expense Claim Rejected Message |
Inherits from frappe.model.document.Document


Unit DTPlot
Description
This unit facilitates the bridging between darkteal and Gnuplot
Overview
Classes, Interfaces, Objects and Records
Record TPlotStyle |
A record containing plot style |
Class TPlot |
A class that holds information of data points to plot, including its style |
Class TFigure |
A class that holds information of a single figure |
Functions and Procedures
Types
Variables
Description
Functions and Procedures
procedure DTPlotInit(GNUplotPath: string); |
|
Initialize plotting functionality by passing gnuplot executable path
|
Types
TPlotType = (...); |
Values
-
ptLines
-
ptPoints
-
ptHistogram
|
Variables
GlobalPlotCount: integer; |
|
Hold global count of created plots
|
Generated by PasDoc 0.15.0.
|


|
JavaTM 2 Platform Standard Ed. 5.0 |
|||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
java.lang.Object java.awt.GridLayout
public class GridLayout
The GridLayout
class is a layout manager that
lays out a container's components in a rectangular grid.
The container is divided into equal-sized rectangles,
and one component is placed in each rectangle.
For example, the following is an applet that lays out six buttons
into three rows and two columns:
import java.awt.*; import java.applet.Applet; public class ButtonGrid extends Applet { public void init() { setLayout(new GridLayout(3,2)); add(new Button("1")); add(new Button("2")); add(new Button("3")); add(new Button("4")); add(new Button("5")); add(new Button("6")); } }
If the container's ComponentOrientation
property is horizontal
and left-to-right, the above example produces the output shown in Figure 1.
If the container's ComponentOrientation
property is horizontal
and right-to-left, the example produces the output shown in Figure 2.
| Figure 1: Horizontal, Left-to-Right | Figure 2: Horizontal, Right-to-Left |
When both the number of rows and the number of columns have been set to non-zero values, either by a constructor or by the setRows and setColumns methods, the number of columns specified is ignored. Instead, the number of columns is determined from the specified number or rows and the total number of components in the layout. So, for example, if three rows and two columns have been specified and nine components are added to the layout, they will be displayed as three rows of three columns. Specifying the number of columns affects the layout only when the number of rows is set to zero.
| Constructor Summary | |
|---|---|
GridLayout()
Creates a grid layout with a default of one column per component, in a single row. |
|
GridLayout(int rows,
int cols)
Creates a grid layout with the specified number of rows and columns. |
|
GridLayout(int rows,
int cols,
int hgap,
int vgap)
Creates a grid layout with the specified number of rows and columns. |
| Method Summary | |
|---|---|
void |
addLayoutComponent(String name,
Component comp)
Adds the specified component with the specified name to the layout. |
int |
getColumns()
Gets the number of columns in this layout. |
int |
getHgap()
Gets the horizontal gap between components. |
int |
getRows()
Gets the number of rows in this layout. |
int |
getVgap()
Gets the vertical gap between components. |
void |
layoutContainer(Container parent)
Lays out the specified container using this layout. |
Dimension |
minimumLayoutSize(Container parent)
Determines the minimum size of the container argument using this grid layout. |
Dimension |
preferredLayoutSize(Container parent)
Determines the preferred size of the container argument using this grid layout. |
void |
removeLayoutComponent(Component comp)
Removes the specified component from the layout. |
void |
setColumns(int cols)
Sets the number of columns in this layout to the specified value. |
void |
setHgap(int hgap)
Sets the horizontal gap between components to the specified value. |
void |
setRows(int rows)
Sets the number of rows in this layout to the specified value. |
void |
setVgap(int vgap)
Sets the vertical gap between components to the specified value. |
String |
toString()
Returns the string representation of this grid layout's values. |
| Methods inherited from class java.lang.Object |
|---|
clone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait |
| Constructor Detail |
|---|
public GridLayout()
public GridLayout(int rows, int cols)
One, but not both, of rows
and cols
can
be zero, which means that any number of objects can be placed in a
row or in a column.
rows
- the rows, with the value zero meaning
any number of rows.cols
- the columns, with the value zero meaning
any number of columns.public GridLayout(int rows, int cols, int hgap, int vgap)
In addition, the horizontal and vertical gaps are set to the specified values. Horizontal gaps are placed between each of the columns. Vertical gaps are placed between each of the rows.
One, but not both, of rows
and cols
can
be zero, which means that any number of objects can be placed in a
row or in a column.
All GridLayout
constructors defer to this one.
rows
- the rows, with the value zero meaning
any number of rowscols
- the columns, with the value zero meaning
any number of columnshgap
- the horizontal gapvgap
- the vertical gap
IllegalArgumentException
- if the value of both
rows
and cols
is
set to zero| Method Detail |
|---|
public int getRows()
public void setRows(int rows)
rows
- the number of rows in this layout
IllegalArgumentException
- if the value of both
rows
and cols
is set to zeropublic int getColumns()
public void setColumns(int cols)
cols
- the number of columns in this layout
IllegalArgumentException
- if the value of both
rows
and cols
is set to zeropublic int getHgap()
public void setHgap(int hgap)
hgap
- the horizontal gap between componentspublic int getVgap()
public void setVgap(int vgap)
vgap
- the vertical gap between componentspublic void addLayoutComponent(String name, Component comp)
addLayoutComponent
in interface LayoutManager
name
- the name of the componentcomp
- the component to be addedpublic void removeLayoutComponent(Component comp)
removeLayoutComponent
in interface LayoutManager
comp
- the component to be removedpublic Dimension preferredLayoutSize(Container parent)
The preferred width of a grid layout is the largest preferred width of all of the components in the container times the number of columns, plus the horizontal padding times the number of columns minus one, plus the left and right insets of the target container.
The preferred height of a grid layout is the largest preferred height of all of the components in the container times the number of rows, plus the vertical padding times the number of rows minus one, plus the top and bottom insets of the target container.
preferredLayoutSize
in interface LayoutManager
parent
- the container in which to do the layout
minimumLayoutSize(java.awt.Container)
,
Container.getPreferredSize()
public Dimension minimumLayoutSize(Container parent)
The minimum width of a grid layout is the largest minimum width of all of the components in the container times the number of columns, plus the horizontal padding times the number of columns minus one, plus the left and right insets of the target container.
The minimum height of a grid layout is the largest minimum height of all of the components in the container times the number of rows, plus the vertical padding times the number of rows minus one, plus the top and bottom insets of the target container.
minimumLayoutSize
in interface LayoutManager
parent
- the container in which to do the layout
preferredLayoutSize(java.awt.Container)
,
Container.doLayout()
public void layoutContainer(Container parent)
This method reshapes the components in the specified target
container in order to satisfy the constraints of the
GridLayout
object.
The grid layout manager determines the size of individual components by dividing the free space in the container into equal-sized portions according to the number of rows and columns in the layout. The container's free space equals the container's size minus any insets and any specified horizontal or vertical gap. All components in a grid layout are given the same size.
layoutContainer
in interface LayoutManager
parent
- the container in which to do the layoutContainer
,
Container.doLayout()
public String toString()
toString
in class Object
|
JavaTM 2 Platform Standard Ed. 5.0 |
|||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
Copyright © 2004, 2010 Oracle and/or its affiliates. All rights reserved. Use is subject to license terms. Also see the documentation redistribution policy.


Look here to see how this website was made!
This Website uses various frameworks like Materialize.css, Normalize, smoothscroll and
JQuery!

Platforms: (The Internet!)
TuneSync is a beautiful game app synced to music.
It is Quad³ Studios' first attempt, at creating a game.
So far, we've started it out, and found music for it.
Stay Tuned for more amazing updates!
Platforms:


211 Massachusetts Avenue
Map | Photo | What's Here
Scroll: N | S | E | W Zoom: In | Out
Campus Map Help
0: MIT Mobile Web Home 1: Campus Map Home
Campus map provided by Department of Facilities and Information Services & Technology


|
Contiki 2.5
|
Handles the control of the USART for communication with the ATmega1284p for sending commands. More...
Go to the source code of this file.
Functions | |
| void | uart_init_circ_buf (tcirc_buf *cbuf) |
| This will intialize the circular buffer head and tail of tcirc_buf struct. | |
| void | uart_add_to_circ_buf (tcirc_buf *cbuf, uint8_t ch) |
| This will add a new character to the circular buffer. | |
| uint8_t | uart_get_from_circ_buf (tcirc_buf *cbuf) |
| This will get a character from the buffer requested. | |
| void | uart_clear_rx_buf (void) |
| This will clear the RX buffer. | |
| uint8_t | uart_circ_buf_has_char (tcirc_buf *cbuf) |
| This will check for a character in the requested buffer. | |
| uint8_t | uip_ntohex (uint8_t val) |
| This will convert a nibble to a hex value. | |
| void | itohex (uint8_t val, char *str) |
| Convert integer to hex value. | |
| uint8_t | uart_get_char_rx (void) |
| This will wait for a new character from the ATmega1284p and timeout if no new character is received. | |
| void | uart_init (void) |
| Initialize UART to 38400 Baud Rate and only enable UART for transmission. | |
| void | uart_deinit (void) |
| Turn off UART for sleep mode. | |
| void | uart_send_byte (uint8_t byte) |
| Send one byte over the uart. | |
| ISR (USART_RX_vect) | |
| This is the USART RX complete interrupt. | |
| void | uart_serial_send_frame (uint8_t cmd, uint8_t payload_length, uint8_t *payload) |
| This function builds and sends a binary command frame to the ATmega1284p. | |
| void | uart_timeout_msg (uint8_t x) |
| This displays a time out message to the user based on the parameter reason x. | |
| void | uart_serial_rcv_frame (uint8_t wait_for_ack) |
| This will receive a frame from the ATmega1284p and parse the incoming data. | |
Variables | |
| tcirc_buf | rxbuf |
| The RX circular buffer, for storing characters from serial port. |
Handles the control of the USART for communication with the ATmega1284p for sending commands.
Definition in file uart.c.


7 CosNaming Service
7.1 Overview of the CosNaming Service
The CosNaming Service is a service developed to help users and programmers identify objects by human readable names rather than by a reference. By binding a name to a naming context (another object), a contextual reference is formed. This is helpful when navigating in the object space. In addition, identifying objects by name allows you to evolve and/or relocate objects without client code modification.
The CosNaming service has some concepts that are important:
-
name binding - a name to object association.
-
naming context - is an object that contains a set of name bindings in which each name is unique. Different names can be bound to the same object.
-
to bind a name - is to create a name binding in a given context.
-
to resolve a name - is to determine the object associated with the name in a given context.
A name is always resolved in a context, there no absolute names exist. Because a context is like any other object, it can also be bound to a name in a naming context. This will result in a naming graph (a directed graph with notes and labeled edges). The graph allows more complex names to refer to an object. Given a context, you can use a sequence to reference an object. This sequence is henceforth referred to as name and the individual elements in the sequence as name components. All but the last name component are bound to naming contexts.
The diagram in figure 1 illustrates how the Naming Service provides a contextual relationship between objects, NamingContexts and NameBindings to create an object locality, as the object itself, has no name.
The naming contexts provide a directory of contextual reference and naming for objects (an object can appear to have more than one name).
In figure 1 the object to the right can either be called alpha from one context or gamma from another.
The Naming Service has an initial naming context, which is shown in the diagram as the top-most object in the naming graph. It has two names beta and epsilon, which are bound to other naming contexts. The initial naming context is a well known location used to share a common name space between multiple programs. You can traverse the naming graph until you reach a name, which is bound to an object, which is not a naming context.
We recommend reading chapter 12, CORBA Fundamentals and Programming, for detailed information regarding the Naming Service.
7.2 The Basic Use-cases of the Naming Service
The basic use-cases of the Naming Service are:
- Fetch initial reference to the naming service.
- Creating a naming context.
- Binding and unbinding names to objects.
- Resolving a name to an object.
- Listing the bindings of a naming context.
- Destroying a naming context.
Fetch Initial Reference to the Naming Service
In order to use the naming service you have to fetch an initial reference to it. This is done with:
NS = corba:resolve_initial_references("NameService").
NS in the other use-cases refers to this initial reference.
Creating a Naming Context
There are two functions for creating a naming context. The first function, which only creates a naming context object is:
NC = 'CosNaming_NamingContext':new_context(NS).
The other function creates a naming context and binds it to a name in an already existing naming context (the initial context in this example):
NC = 'CosNaming_NamingContext':bind_new_context(NS, lname:new(["new"])).
Binding and Unbinding Names to Objects
The following steps illustrate how to bind/unbind an object reference to/from a name. For the example below, assume that the NamingContexts in the path are already bound to the name /workgroup/services, and that reference to the services context are in the variable Sc.
-
Use the naming library functions to create a name
Name = lname:new(["object"]).
-
Use CosNaming::NamingContext::bind() to bind a name to an object
'CosNaming_NamingContext':bind(Sc, Name, Object).
-
Use CosNaming::NamingContext::unbind() to remove the NameBinding from an object
'CosNaming_NamingContext':unbind(Sc, Name).
Objects can have more than one name, to indicate different paths to the same object.
Resolving a Name to an Object
The following steps show how to retrieve the object reference to the service context above (/workgroup/services).
-
Use the naming library functions to create a name path:
Name = lname:new(["workgroup", "services"]).
-
Use CosNaming::NamingContext::resolve() to to resolve the name to an object
Sc = 'CosNaming_NamingContext':resolve(NS, Name).
An alternative is to use:
Sc = corba:string_to_object("corbaname:rir:/NameService#workgroup/services/").
The corbaname schema is described further in the Interoperable Naming Service section.
Listing the Bindings in a NamingContext
-
Use CosNaming::NamingContext::list() to list all the bindings in a context
The following code retrieves and lists up to 10 bindings from a context.
{BList, BIterator} = 'CosNaming_NamingContext':list(Sc, 10). lists:foreach(fun({{Id, Kind},BindingType}) -> case BindingType of nobject -> io:format("id: %s, kind: %s, type: object~n", [Id, Kind]); _ -> io:format("id: %s, kind: %s, type: ncontext~n", [Id, Kind]) end end, Blist).
Normally a BindingIteratoris helpful in situations where you have a large number of objects in a list, as the programmer then can traverse it more easily. In Erlang it is not needed, because lists are easily handled in the language itself.
Remember that the BindingIterator (BIterator in the example) is an object and therefore must be removed otherwise dangling processes will occur. Use CosNaming::BindingIterator::destroy() to remove it.
'CosNaming_NamingContext':destroy(BIterator).
Destroying a Naming Context
The naming contexts are persistent and must be explicitly removed. (they are also removed if all Orber nodes in the domain are stopped).
-
Use CosNaming::NamingContext::destroy() to remove a NamingContext
'CosNaming_NamingContext':destroy(Sc).
7.3 Interoperable Naming Service
The OMG specifies URL schemes, which represent a CORBA object and a CORBA object bound in a NamingContext, for resolving references from other ORB:s. As of today, three schemes are defined:
- IOR
- corbaloc
- corbaname
IOR
A stringified IOR is a valid URL format but difficult for humans to handle through non-electronic means. This URL format does not depend on a specific Name Service and, thus, is robust and insulates the client from the encapsulated transport information and object key used to reference the object.
corbaloc
The notation of this scheme is similar to the more well known URL HTTP, and the full corbaloc BNF is:
<corbaloc> = "corbaloc:"<obj_addr_list>["/"<key_string>] <obj_addr_list> = [<obj_addr>","]*<obj_addr> <obj_addr> = <prot_addr> | <future_prot_addr> <prot_addr> = <rir_prot_addr> | <iiop_prot_addr> <rir_prot_addr> = <rir_prot_token>":" <rir_prot_token> = rir <future_prot_addr> = <future_prot_id><future_prot_addr> <future_prot_id> = <future_prot_token>":" <iiop_prot_addr> = <iiop_id><iiop_addr> <iiop_id> = <iiop_default> | <iiop_prot_token>":" <iiop_default> = ":" <iiop_prot_token> = "iiop" <iiop_addr> = <version><host>[":"<port>] <host> = <DNS-style Host Name> | <ip_v4_address> | "["<ip_v6_address>"]" <version> = <major>"."<minor>"@" | empty_string <port> = number <major> = number <minor> = number <DNS-style Host Name> = string <ip_v4_address> = string <ip_v6_address> = string <key_string> = for example NameService
The corbaloc scheme consists of 3 parts:
- Protocol - as of today iiop or rir is supported. Using rir means that we will resolve the given Key locally, i.e., the same as using corba:resolve_initial_references("NameService").
- IIOP address - this address can be divided into Version, Host and Port. If the version or port are left out they will be set to the default values 1.0 and 2809 respectively.
- KeyString - an object key, e.g., "NameService". If no Key is supplied the default value "NameService" will be used.
A corbaloc can be passed used together with corba:string_to_object("corbaloc::1.0@erlang.org:4001/NameService") or set as the configuration variables orbInitilRef or orbDefaultInitilRef and calling corba:resolve_initial_references("NameService"). For more information see the Orber installation chapter. corbaloc can also be used together with corbaname to gain an easy access to a Name Service.
Currently, the OMG defines a set of reserved keys and the type of object, listed below, they should be associated with. The NameService key may not be changed in Orber. If you want to add one of the reserved keys as an initial service, simply use:
1> Factory = cosNotificationApp:start_global_factory(). 2> corba:add_initial_service("NotificationService", Factory).
This object can then be easily resolved by any other ORB, supporting the Interoperable Naming Service, by using:
3> NF = corba:string_to_object("corbaloc::1.0@erlang.org:4001/NotificationService").
| String Name | Object Type |
| RootPOA | PortableServer::POA |
| POACurrent | PortableServer::Current |
| InterfaceRepository | CORBA::Repository |
| NameService | CosNaming::NamingContext |
| TradingService | CosTrading::Lookup |
| SecurityCurrent | SecurityLevel1::Current/SecurityLevel2::Current |
| TransactionCurrent | CosTransaction::Current |
| DynAnyFactory | DynamicAny::DynAnyFactory |
| ORBPolicyManager | CORBA::PolicyManager |
| PolicyCurrent | CORBA::PolicyCurrent |
| NotificationService | CosNotifyChannelAdmin::EventChannelFactory |
| TypedNotificationService | CosTypedNotifyChannelAdmin::TypedEventChannelFactory |
| CodecFactory | IOP::CodecFactory |
| PICurrent | PortableInterceptors::Current |
corbaname
The corbaname URL scheme is an extension of the corbaloc scheme, and the full corbaname BNF is:
<corbaname> = "corbaname:"<obj_addr_list>["/"<key_string>]["#"<string_name>] <obj_addr_list> = as described above. <key_string> = as described above.
The string_name, concatenated to the corbaloc string, identifies a binding in a naming context. A name component consists of two parts, i.e., id and kind, which is represented as follows:
| String Name | Name Sequence | Comment |
| "id1/./id3.kind3" | [{"id1",""},{"",""},{"id3","kind3"}] | The first component has no kind defined while the second component's both fields are empty. |
| "id1//id3.kind3" | ERROR | Not allowed, must insert a '.' between the '//'. |
| "id1.kind1/." | [{"id1","kind1"},{"",""}] | The first component's fields are both set while the second component's both fields are empty. |
| "id1.kind1/id2." | ERROR | An Id with a trailing '.' is not allowed. |
| "i\\/d1/i\\.d2" | [{"i/d1",""},{"i.d2",""}] | Since '.' and '/' are used to separate the components, these tokens must be escaped to be correctly converted. |
After creating a stringified Name we can either use:
NameStr = "org.erlang", NS = corba:resolve_initial_references("NameService"), Obj = 'CosNaming_NamingContextExt':resolve_str(NS, NameStr),
or concatenate the Name String using:
NameStr = "Swedish/Soccer/Champions", Address = "corbaname:iiop:1.0@www.aik.se:2000/NameService", NS = corba:resolve_initial_references("NameService"), URLStr = 'CosNaming_NamingContextExt':to_url(NS, Address, NameStr), Obj = corba:string_to_object(URLStr),
Using the first alternative, the configuration variables orbInitilRef and orbDefaultInitilRef, will determine which other ORB's or the local Name Service Orber will try to resolve the given string from. The second alternative allows us to override any settings of the configuration variables.
The function to_url/3 will perform any necessary escapes compliant with IETF/RFC 2396. US-ASCII alphanumeric characters and "," | "/" | ":" | "?" | "@" | "&" | "=" | "+" | "$" | ";" | "-" | "_" | "." | "!" | "~" | "*" | "'" | "(" | ")" are not escaped.


I have many years experience as a web developer. After taking time off to pursue a graduate degree, I am getting up to date with new technologies such as React.js, Node.js, CSS3, and HTML5. View my portfolio.
Verge PDX
I am the owner of Verge PDX, a curatorial practice which manages rotatins of great, emerging artists in Portland businesses. Visit Vergepdx.com
Installation Art
I create large, immersive, playful installations that employ technology either through sound, video or micro controllers. View some of my installation projects.


#include <Bitbuf.h>
Public Members | |||
| void | CreateOSPalette () | ||
| void | DestroyOSPalette () |
After the SColorInfo object is valid, CreateOSPalette gets called, allowing OS dependant code to be inserted.
DestroyOSPalette gets called before the SColorInfo structure is destroyed.


--- layout: default title: "Forms" subtitle: Text menu: form submenu: text ---
.form-spinner-hide
.form-group


Hello
I have failed over and over again at being able to create material or a website that clearly articulates what Crema is and does and why I am proud to see my team grow wildly successful products for our clients.
We have grown from my freelance work ten years ago as a user experience designer to a full stack digital agency twenty plus and growing. We’ve hired user interface and product designers that continue to design incredible products. We’ve hired developers and engineers that can build just about anything with the right resources and time. We’ve hired project managers that can navigate the toughest schedules and biggest outcomes.  They can take just an idea and boil it down into a true product vision with our clients and production team in the course of days.
“You guys do amazing work!……… But what do you actually do?”
I can’t tell you how many times we’ve heard this. Especially after handing someone a business card or someone looks at our website for the first time. Most of our clients could tell you “Crema helped us design an awesome app experience. They built the entire thing!” or “they are amazing at working with our team to pull it all together!” “.. they pushed me to think through the business model, and helped test our ideas, and oh yea, they help interview and train our first hires to this team.”
Context is everything
Today we say, “Crema is an innovation and technology firm.” This was after many other approaches of the years. (see down below for few) Each person comes to our content with a different context. Launched a tech product before? You get how design, development, and business must align. Inside a large old-school IT driven enterprise? You might wonder if that means that we offer IT resources to manage servers. In sales? You might think that we are a creative digital communications firm to build your next landing page. If you’re most of my family, then you think that means you do computers, and can help trouble shoot your iphone photos app.
In person, we’re gold!
Give me five minutes and I can talk anyone through the story of Crema. I tweak the language a bit each time, but the plot line is pretty much the same. In meetings it usually goes something like this:
Share your story with us
I always lead first with the person telling us about their company. About the challenges, they are facing and ideas they have around how technology might be a useful tool for them. We talk through what they’ve tried so far. Have they used another team? Did they hit their outcomes or timelines? Do they have a group in-house? How backlogged is that group? What technologies have they tried? Have they found any off-the-shelf solutions? Etc. At this point, many of them think we do something with apps, but they are not exactly sure what or how.
“Tell me about Crema!” they often turn it back to us.
I’d be happy to. Long story short (but actually long)
I started Crema as a design agency about 8 years ago with my business partner Dan. My skills were in user experience design and product discovery, and Dan offered project management and operations. To this day, our heart-beat is still rooted in great design and management, but we have grown to be a full-stack digital product agency. We started to refer away the marketing and communication projects a few years back in an effort to focus on building products for both funded entrepreneurs and as an innovation partner to large enterprises.
People come through one of three doors when they learn about Crema.
Photo by Verne Ho on Unsplash
They know Crema for our design. They were told we design incredible user interfaces. That we can design fast and that we are one of the top digital design shops they know.
More often than not, they think of Crema as a dev shop. We build apps and websites. We have people that can code things, if they are pretty savvy they might know we do it with open-source solutions.
Photo by Luca Bravo on Unsplash
Finally, they might think of us as a technology and business consultants. Seeking our feedback on their tech idea or on a current challenge that they have with current technology solution.
Our Approach
Out of the gate, we help companies to align around what problem they are solving, name the customer and users, and then prototype solutions to validate a direction. We explore new ideas or help to bring a fresh perspective on existing ideas.
All engagements kick off with a strategy session and rapid design prototyping sprints. We have full design mockups in the course of days, not weeks, to start putting in front of users and customers to gather feedback and refine our directions.
Our teams move through agile sprints trying to release a build as early as the first sprint. Which often surprises clients when they see themselves holding even a simple build in the first couple weeks of development. All this is so that you can see your solution faster and make an informed decision about how constraints and user feedback will change how we move forward.
Photo by rawpixel.com on Unsplash
We work to a get a release out to users in the first three months. Controlling how fast we release and gathering feedback. As we iterate, our goal is to grow traction and automate what we are doing manually today. Constantly looking to make the experience better, and listen to the customers as we aim for our client’s metrics.
The journey is not a project. It’s a company. We help our clients scale their solutions until the product needs a full-time in-house dedicated team. Together we transition by helping out client interview and hire their developers and designers. We work alongside them as we train them on our architecture, design systems, and long-term considerations.
Often our clients keep us on retainer to help with strategy, design, and management, and we spin our teams back up to test new ideas and concepts as their teams grow.
Some of the companies we have collaborated with have gone on to be wildly successful. Startups we’ve help launch are worth millions even reaching “unicorn” status as billion dollar companies. To make it very clear: we were only one part of that journey. Product is not the only factor to success. Enterprises that we’ve worked with have grown their platforms to have tens of thousands of users, and used our tools to aid multi-million dollar contracts.
Many of our clients have us as silent partners. It’s their success stories. We don’t win awards for their latest ad campaigns. We don’t brag about their SEO vanity stats. We focus on product, and build incredible experiences that help companies grow value for their teams and for the customers
I’ve built one of the most incredible teams I’ve ever seen. We have little to no turnover even with most of the recruiters around attempting to poach.
Our clients are completely integrated and have full transparency to their team. They know most of them personally. We are your product team. Like a startup team for hire. Want to talk to some of our references? They’ll tell you that we challenged them. That we were honest, and that we do our best to help them succeed.
Not everyone succeeds. That’s the nature of business. We know product, and product experience. We partner and consult for customer growth, change management, marketing and growth hacking. We know that we have a lot to learn, but my team learns fast.
Ready to see your product idea become a great product experience?
So how do I boil all that into a tagline?
We have tried many different approaches here. I know what motivates our internal team. “We turn good ideas into great product experiences.”
What are the statements that help you understand who we are. To help you to understand that we are a creative product agency with a heart-beat for creating amazing product experiences.
A few statements we’ve tried.
Your startup team for hire.
We design, build and launch tech products.
We are a technology and innovation firm.
We build custom software with local teams that become successful companies.
We craft great product experiences.
We build incredible product teams.
We help funded startups and innovative enterprises
YOU TELL US!
Comment below and tell us what you think we should use. Clap for the ones that you think would drive home my amazing team!
Give us a clap and subscribe below.
Thanks to Alexa Huston.


WikiLeaks<EMAIL_ADDRESS>leaked emails, 2009 mail archive
This message is part of a
particular mailbox
provided at
WikiLeaks
and it should be
discussed here.
[
Date Prev
][
Date Next
][
Thread Prev
][
Thread Next
][
Date Index
][
Thread Index
]
[no subject]
To
:
<EMAIL_ADDRESS>From
: Ken Curriston <
<EMAIL_ADDRESS>>
Date
: Sat, 7 Feb 2009 20:57:47 -0800 (PST)
Domainkey-signature
: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:To:MIME-Version:Content-Type:Message-ID; b=HVqCVxwk2Esxtw0SPpPMNTDu7q3kMdc9VIisWdz9A99AWc55p8izRS/84hzU4lIN/Qvvxe6C08E7BIzmV0zp+i4dkhMZZiOzQhNpwb5woFYi/JXxGi5JBWyXjLfP5FS5y9uYaW1pKdc/ge8mgEAGWHkTiSNR9lfHLs+PoMFXoJg=;
Reply-to
:
<EMAIL_ADDRESS>right now i am waiting for 1 of my ex's to get in touch with a tattoist friend that can draw it. but it is slow going
Prev by Date:
THE NEW DAWN is back!
Next by Date:
Signed 8x10's of Lori's autopsy photos!! - $100
Previous by thread:
THE NEW DAWN is back!
Next by thread:
Signed 8x10's of Lori's autopsy photos!! - $100
Index(es):
Date
Thread
Entry for this page on WikiLeaks
|
Discussion page on WikiLeaks
|
wikileaks.org
Date Index
|
Thread Index
|
Author Index


Roman Numerals Converter
Welcome to the Roman Numeral Converter! Type in your first number below!
Enter number here.
Change it!