net.rim.device.api.crypto.tls
Interface AlertProtocol


public interface AlertProtocol

Defines the common constants for the alert protocol.

It is important to note that any of the defined integers in the RFCs for WTLS or TLS or SSL are used here. That is, if you want a NO_CERTIFICATE alert description it is 41 as defined in the WTLS specification. The same also applies to the alert levels.

Category:
Signed: This element is only accessible by signed applications. If you intend to use this element, please visit http://www.blackberry.com/go/codesigning to obtain a set of code signing keys. Code signing is only required for applications running on BlackBerry smartphones; development on BlackBerry Smartphone Simulators can occur without code signing.
Since:
BlackBerry API 3.6.0

Field Summary
Category: Signed static byte ACCESS_DENIED
          Indicates that a valid certificate was received, but when access control was applied, the sender decided not to proceed with negotiation.
Category: Signed static byte BAD_CERTIFICATE
          Indicates that a certificate was corrupt, contained signatures that did not verify correctly, etc.
Category: Signed static byte BAD_RECORD_MAC
          This alert is returned if a record is received with an incorrect Message Authentication Code (MAC).
Category: Signed static byte CERTIFICATE_EXPIRED
          Indicates that a certificate has expired or is not currently valid.
Category: Signed static byte CERTIFICATE_REVOKED
          Indicates that a certificate was revoked by its signer.
Category: Signed static byte CERTIFICATE_UNKNOWN
          Indicates that another (unspecified) issue arose in processing the certificate, rendering it unacceptable.
Category: Signed static byte CLOSE_NOTIFY
          Notifies the recipient that the sender will not send any more messages using this connection state.
Category: Signed static byte CRITICAL
          Represents a CRITICAL error.
Category: Signed static byte DECODE_ERROR
          Indicates that a message could not be decoded because some field was out of the specified range or the length of the message was incorrect.
Category: Signed static byte DECOMPRESSION_FAILURE
          Indicates that decompression function received improper input (e.g. data that would expand to excessive length).
Category: Signed static byte DECRYPTION_FAILED
          A WTLSCiphertext decrypted in an invalid way: either it wasn`t an even multiple of the block length or its padding values, when checked, weren`t correct.
Category: Signed static byte DECRYPT_ERROR
          Indicates that a handshake cryptographic operation failed, including being unable to correctly verify a signature, decrypt a key exchange, or validate a finished message.
Category: Signed static byte DISABLED_KEY_ID
          Indicates that all the client_key_id's listed in ClientHello.client_key_ids are disabled administratively.
Category: Signed static byte DUPLICATE_FINISHED_RECEIVED
          Indicates that an abbreviated or optimised handshake, the client has sent a second (resent) finished message.
Category: Signed static byte EXPORT_RESTRICTION
          Indicates that a negotiation not in compliance with export restrictions was detected; for example, attempting to transfer a 1024 bit ephemeral RSA key for the RSA_EXPORT handshake method.
Category: Signed static byte FATAL
          Represents a FATAL error.
Category: Signed static byte HANDSHAKE_FAILURE
          Indicates that the sender was unable to negotiate an acceptable set of security parameters given the options available.
Category: Signed static byte ILLEGAL_PARAMETER
          Indicates that a field in the handshake was out of range or inconsistent with other fields.
Category: Signed static byte INSUFFICIENT_SECURITY
          Returned instead of handshake_failure when a negotiation has failed specifically because the server requires ciphers more secure than those supported by the client.
Category: Signed static byte INTERNAL_ERROR
          Indicates that an internal error unrelated to the peer or the correctness of the protocol makes it impossible to continue (such as a memory allocation failure).
Category: Signed static byte KEY_EXCHANGE_DISABLED
          To protect the outcome of the anonymous key exchange from being overriding by the undesirable subsequent anonymous key exchanges, key exchange is administratively disabled.
Category: Signed static byte NO_CERTIFICATE
          Indicates that the certificate could not be found.
Category: Signed static byte NO_CONNECTION
          indicates that a message was received while there is no secure connection with the sender.
Category: Signed static byte NO_RENEGOTIATION
          Sent by the client in response to a hello request or by the server in response to a client hello after initial handshaking.
Category: Signed static byte PROTOCOL_VERSION
          Indicates that the protocol version the client has attempted to negotiate is recognized, but not supported.
Category: Signed static byte RECORD_OVERFLOW
          Indicates that a WTLSCiphertext record was received which had a length more than 2^14+2048 bytes, or a record decrypted to a WTLSCompressed record with more than 2^14+1024 bytes.
Category: Signed static byte SESSION_CLOSE_NOTIFY
          Notifies the recipient that the sender will not send any more messages using this connection state or the secure session.
Category: Signed static byte SESSION_NOT_READY
          Indicates that the secure session is not ready to resume new secure connections due to administrative reasons such as that the session is temporarily not available due to maintenance in the server.
Category: Signed static byte TIME_REQUIRED
          This alert is a warning sent by the server, to inform the client that more time is required for a certain handshake operation, than would be expected for the client retransmission timer.
Category: Signed static byte UNEXPECTED_MESSAGE
          Represents an inappropriate message.
Category: Signed static byte UNKNOWN_CA
          Indicates that a valid certificate chain or partial chain was received, but the certificate was not accepted because the CA certificate could not be located or couldn`t be matched with a known, trusted CA.
Category: Signed static byte UNKNOWN_KEY_ID
          Indicates that none of the client key_id's listed in ClientHello.client_key_ids is known or recognized to the server, or the client did not supply any items, if the server has the policy that requires recognition of client_key_id's.
Category: Signed static byte UNKNOWN_PARAMETER_INDEX
          Indicates that the client has suggested a key exchange suite that could be supported by the server, but the server does not know the key exchange parameter index supplied.
Category: Signed static byte UNSUPPORTED_CERTIFICATE
          Indicates that a certificate was of an unsupported type.
Category: Signed static byte USER_CANCELLED
          Indicates that this handshake is being canceled for some reason unrelated to a protocol failure.
Category: Signed static byte WARNING
          The severity of the alert.
 



Field Detail

WARNING

static final byte WARNING
The severity of the alert.

See Also:
Constant Field Values
Category:
Signed: This element is only accessible by signed applications. If you intend to use this element, please visit http://www.blackberry.com/go/codesigning to obtain a set of code signing keys. Code signing is only required for applications running on BlackBerry smartphones; development on BlackBerry Smartphone Simulators can occur without code signing.
Since:
BlackBerry API 3.6.0

CRITICAL

static final byte CRITICAL
Represents a CRITICAL error.

See Also:
Constant Field Values
Category:
Signed: This element is only accessible by signed applications. If you intend to use this element, please visit http://www.blackberry.com/go/codesigning to obtain a set of code signing keys. Code signing is only required for applications running on BlackBerry smartphones; development on BlackBerry Smartphone Simulators can occur without code signing.
Since:
BlackBerry API 3.6.0

FATAL

static final byte FATAL
Represents a FATAL error.

See Also:
Constant Field Values
Category:
Signed: This element is only accessible by signed applications. If you intend to use this element, please visit http://www.blackberry.com/go/codesigning to obtain a set of code signing keys. Code signing is only required for applications running on BlackBerry smartphones; development on BlackBerry Smartphone Simulators can occur without code signing.
Since:
BlackBerry API 3.6.0

CLOSE_NOTIFY

static final byte CLOSE_NOTIFY
Notifies the recipient that the sender will not send any more messages using this connection state.

See Also:
Constant Field Values
Category:
Signed: This element is only accessible by signed applications. If you intend to use this element, please visit http://www.blackberry.com/go/codesigning to obtain a set of code signing keys. Code signing is only required for applications running on BlackBerry smartphones; development on BlackBerry Smartphone Simulators can occur without code signing.
Since:
BlackBerry API 3.6.0

SESSION_CLOSE_NOTIFY

static final byte SESSION_CLOSE_NOTIFY
Notifies the recipient that the sender will not send any more messages using this connection state or the secure session.

See Also:
Constant Field Values
Category:
Signed: This element is only accessible by signed applications. If you intend to use this element, please visit http://www.blackberry.com/go/codesigning to obtain a set of code signing keys. Code signing is only required for applications running on BlackBerry smartphones; development on BlackBerry Smartphone Simulators can occur without code signing.
Since:
BlackBerry API 3.6.0

NO_CONNECTION

static final byte NO_CONNECTION
indicates that a message was received while there is no secure connection with the sender. This message is fatal or critical.The message is sent in cleartext. This alert SHOULD be accepted regardless of the sequence number in the record which carries this alert. The sender SHOULD use the value 2^16 - 1.

See Also:
Constant Field Values
Category:
Signed: This element is only accessible by signed applications. If you intend to use this element, please visit http://www.blackberry.com/go/codesigning to obtain a set of code signing keys. Code signing is only required for applications running on BlackBerry smartphones; development on BlackBerry Smartphone Simulators can occur without code signing.
Since:
BlackBerry API 3.6.0

UNEXPECTED_MESSAGE

static final byte UNEXPECTED_MESSAGE
Represents an inappropriate message.

This alert is always fatal and should never be observed in communication between proper implementations.

See Also:
Constant Field Values
Category:
Signed: This element is only accessible by signed applications. If you intend to use this element, please visit http://www.blackberry.com/go/codesigning to obtain a set of code signing keys. Code signing is only required for applications running on BlackBerry smartphones; development on BlackBerry Smartphone Simulators can occur without code signing.
Since:
BlackBerry API 3.6.0

TIME_REQUIRED

static final byte TIME_REQUIRED
This alert is a warning sent by the server, to inform the client that more time is required for a certain handshake operation, than would be expected for the client retransmission timer.

When receiving this alert, the client should clear its retransmission timer.

See Also:
Constant Field Values
Category:
Signed: This element is only accessible by signed applications. If you intend to use this element, please visit http://www.blackberry.com/go/codesigning to obtain a set of code signing keys. Code signing is only required for applications running on BlackBerry smartphones; development on BlackBerry Smartphone Simulators can occur without code signing.
Since:
BlackBerry API 3.6.0

BAD_RECORD_MAC

static final byte BAD_RECORD_MAC
This alert is returned if a record is received with an incorrect Message Authentication Code (MAC).

This message is always fatal.

See Also:
Constant Field Values
Category:
Signed: This element is only accessible by signed applications. If you intend to use this element, please visit http://www.blackberry.com/go/codesigning to obtain a set of code signing keys. Code signing is only required for applications running on BlackBerry smartphones; development on BlackBerry Smartphone Simulators can occur without code signing.
Since:
BlackBerry API 3.6.0

DECRYPTION_FAILED

static final byte DECRYPTION_FAILED
A WTLSCiphertext decrypted in an invalid way: either it wasn`t an even multiple of the block length or its padding values, when checked, weren`t correct. This message is generally a warning.

The message is sent in cleartext.

See Also:
Constant Field Values
Category:
Signed: This element is only accessible by signed applications. If you intend to use this element, please visit http://www.blackberry.com/go/codesigning to obtain a set of code signing keys. Code signing is only required for applications running on BlackBerry smartphones; development on BlackBerry Smartphone Simulators can occur without code signing.
Since:
BlackBerry API 3.6.0

RECORD_OVERFLOW

static final byte RECORD_OVERFLOW
Indicates that a WTLSCiphertext record was received which had a length more than 2^14+2048 bytes, or a record decrypted to a WTLSCompressed record with more than 2^14+1024 bytes. This message is generally a warning.

The message is sent in cleartext.

See Also:
Constant Field Values
Category:
Signed: This element is only accessible by signed applications. If you intend to use this element, please visit http://www.blackberry.com/go/codesigning to obtain a set of code signing keys. Code signing is only required for applications running on BlackBerry smartphones; development on BlackBerry Smartphone Simulators can occur without code signing.
Since:
BlackBerry API 3.6.0

DECOMPRESSION_FAILURE

static final byte DECOMPRESSION_FAILURE
Indicates that decompression function received improper input (e.g. data that would expand to excessive length).

This message is always fatal( in SSL and TLS). This message is generally a warning in WTLS and is sent in the cleartext for that protocol.

See Also:
Constant Field Values
Category:
Signed: This element is only accessible by signed applications. If you intend to use this element, please visit http://www.blackberry.com/go/codesigning to obtain a set of code signing keys. Code signing is only required for applications running on BlackBerry smartphones; development on BlackBerry Smartphone Simulators can occur without code signing.
Since:
BlackBerry API 3.6.0

HANDSHAKE_FAILURE

static final byte HANDSHAKE_FAILURE
Indicates that the sender was unable to negotiate an acceptable set of security parameters given the options available.

This is a fatal error.

See Also:
Constant Field Values
Category:
Signed: This element is only accessible by signed applications. If you intend to use this element, please visit http://www.blackberry.com/go/codesigning to obtain a set of code signing keys. Code signing is only required for applications running on BlackBerry smartphones; development on BlackBerry Smartphone Simulators can occur without code signing.
Since:
BlackBerry API 3.6.0

NO_CERTIFICATE

static final byte NO_CERTIFICATE
Indicates that the certificate could not be found.

See Also:
Constant Field Values
Category:
Signed: This element is only accessible by signed applications. If you intend to use this element, please visit http://www.blackberry.com/go/codesigning to obtain a set of code signing keys. Code signing is only required for applications running on BlackBerry smartphones; development on BlackBerry Smartphone Simulators can occur without code signing.
Since:
BlackBerry API 3.6.0

BAD_CERTIFICATE

static final byte BAD_CERTIFICATE
Indicates that a certificate was corrupt, contained signatures that did not verify correctly, etc.

See Also:
Constant Field Values
Category:
Signed: This element is only accessible by signed applications. If you intend to use this element, please visit http://www.blackberry.com/go/codesigning to obtain a set of code signing keys. Code signing is only required for applications running on BlackBerry smartphones; development on BlackBerry Smartphone Simulators can occur without code signing.
Since:
BlackBerry API 3.6.0

UNSUPPORTED_CERTIFICATE

static final byte UNSUPPORTED_CERTIFICATE
Indicates that a certificate was of an unsupported type.

See Also:
Constant Field Values
Category:
Signed: This element is only accessible by signed applications. If you intend to use this element, please visit http://www.blackberry.com/go/codesigning to obtain a set of code signing keys. Code signing is only required for applications running on BlackBerry smartphones; development on BlackBerry Smartphone Simulators can occur without code signing.
Since:
BlackBerry API 3.6.0

CERTIFICATE_REVOKED

static final byte CERTIFICATE_REVOKED
Indicates that a certificate was revoked by its signer.

See Also:
Constant Field Values
Category:
Signed: This element is only accessible by signed applications. If you intend to use this element, please visit http://www.blackberry.com/go/codesigning to obtain a set of code signing keys. Code signing is only required for applications running on BlackBerry smartphones; development on BlackBerry Smartphone Simulators can occur without code signing.
Since:
BlackBerry API 3.6.0

CERTIFICATE_EXPIRED

static final byte CERTIFICATE_EXPIRED
Indicates that a certificate has expired or is not currently valid.

See Also:
Constant Field Values
Category:
Signed: This element is only accessible by signed applications. If you intend to use this element, please visit http://www.blackberry.com/go/codesigning to obtain a set of code signing keys. Code signing is only required for applications running on BlackBerry smartphones; development on BlackBerry Smartphone Simulators can occur without code signing.
Since:
BlackBerry API 3.6.0

CERTIFICATE_UNKNOWN

static final byte CERTIFICATE_UNKNOWN
Indicates that another (unspecified) issue arose in processing the certificate, rendering it unacceptable.

See Also:
Constant Field Values
Category:
Signed: This element is only accessible by signed applications. If you intend to use this element, please visit http://www.blackberry.com/go/codesigning to obtain a set of code signing keys. Code signing is only required for applications running on BlackBerry smartphones; development on BlackBerry Smartphone Simulators can occur without code signing.
Since:
BlackBerry API 3.6.0

ILLEGAL_PARAMETER

static final byte ILLEGAL_PARAMETER
Indicates that a field in the handshake was out of range or inconsistent with other fields.

This is always fatal.

See Also:
Constant Field Values
Category:
Signed: This element is only accessible by signed applications. If you intend to use this element, please visit http://www.blackberry.com/go/codesigning to obtain a set of code signing keys. Code signing is only required for applications running on BlackBerry smartphones; development on BlackBerry Smartphone Simulators can occur without code signing.
Since:
BlackBerry API 3.6.0

UNKNOWN_CA

static final byte UNKNOWN_CA
Indicates that a valid certificate chain or partial chain was received, but the certificate was not accepted because the CA certificate could not be located or couldn`t be matched with a known, trusted CA.

This message is always fatal.

See Also:
Constant Field Values
Category:
Signed: This element is only accessible by signed applications. If you intend to use this element, please visit http://www.blackberry.com/go/codesigning to obtain a set of code signing keys. Code signing is only required for applications running on BlackBerry smartphones; development on BlackBerry Smartphone Simulators can occur without code signing.
Since:
BlackBerry API 3.6.0

ACCESS_DENIED

static final byte ACCESS_DENIED
Indicates that a valid certificate was received, but when access control was applied, the sender decided not to proceed with negotiation.

This message is always fatal.

See Also:
Constant Field Values
Category:
Signed: This element is only accessible by signed applications. If you intend to use this element, please visit http://www.blackberry.com/go/codesigning to obtain a set of code signing keys. Code signing is only required for applications running on BlackBerry smartphones; development on BlackBerry Smartphone Simulators can occur without code signing.
Since:
BlackBerry API 3.6.0

DECODE_ERROR

static final byte DECODE_ERROR
Indicates that a message could not be decoded because some field was out of the specified range or the length of the message was incorrect.

This message is always fatal.

See Also:
Constant Field Values
Category:
Signed: This element is only accessible by signed applications. If you intend to use this element, please visit http://www.blackberry.com/go/codesigning to obtain a set of code signing keys. Code signing is only required for applications running on BlackBerry smartphones; development on BlackBerry Smartphone Simulators can occur without code signing.
Since:
BlackBerry API 3.6.0

DECRYPT_ERROR

static final byte DECRYPT_ERROR
Indicates that a handshake cryptographic operation failed, including being unable to correctly verify a signature, decrypt a key exchange, or validate a finished message.

See Also:
Constant Field Values
Category:
Signed: This element is only accessible by signed applications. If you intend to use this element, please visit http://www.blackberry.com/go/codesigning to obtain a set of code signing keys. Code signing is only required for applications running on BlackBerry smartphones; development on BlackBerry Smartphone Simulators can occur without code signing.
Since:
BlackBerry API 3.6.0

UNKNOWN_KEY_ID

static final byte UNKNOWN_KEY_ID
Indicates that none of the client key_id's listed in ClientHello.client_key_ids is known or recognized to the server, or the client did not supply any items, if the server has the policy that requires recognition of client_key_id's. This is generally a fatal alert. disabled_key_id All the client_key_id's listed in ClientHello.client_key_ids are disabled administratively. This is generally a critical alert.

See Also:
Constant Field Values
Category:
Signed: This element is only accessible by signed applications. If you intend to use this element, please visit http://www.blackberry.com/go/codesigning to obtain a set of code signing keys. Code signing is only required for applications running on BlackBerry smartphones; development on BlackBerry Smartphone Simulators can occur without code signing.
Since:
BlackBerry API 3.6.0

DISABLED_KEY_ID

static final byte DISABLED_KEY_ID
Indicates that all the client_key_id's listed in ClientHello.client_key_ids are disabled administratively.

This is generally a critical alert.

See Also:
Constant Field Values
Category:
Signed: This element is only accessible by signed applications. If you intend to use this element, please visit http://www.blackberry.com/go/codesigning to obtain a set of code signing keys. Code signing is only required for applications running on BlackBerry smartphones; development on BlackBerry Smartphone Simulators can occur without code signing.
Since:
BlackBerry API 3.6.0

KEY_EXCHANGE_DISABLED

static final byte KEY_EXCHANGE_DISABLED
To protect the outcome of the anonymous key exchange from being overriding by the undesirable subsequent anonymous key exchanges, key exchange is administratively disabled.

See Also:
Constant Field Values
Category:
Signed: This element is only accessible by signed applications. If you intend to use this element, please visit http://www.blackberry.com/go/codesigning to obtain a set of code signing keys. Code signing is only required for applications running on BlackBerry smartphones; development on BlackBerry Smartphone Simulators can occur without code signing.
Since:
BlackBerry API 3.6.0

SESSION_NOT_READY

static final byte SESSION_NOT_READY
Indicates that the secure session is not ready to resume new secure connections due to administrative reasons such as that the session is temporarily not available due to maintenance in the server.

This is generally a critical alert.

See Also:
Constant Field Values
Category:
Signed: This element is only accessible by signed applications. If you intend to use this element, please visit http://www.blackberry.com/go/codesigning to obtain a set of code signing keys. Code signing is only required for applications running on BlackBerry smartphones; development on BlackBerry Smartphone Simulators can occur without code signing.
Since:
BlackBerry API 3.6.0

UNKNOWN_PARAMETER_INDEX

static final byte UNKNOWN_PARAMETER_INDEX
Indicates that the client has suggested a key exchange suite that could be supported by the server, but the server does not know the key exchange parameter index supplied. When receiving this alert, the client may initiate a new handshake and suggest another parameter index, supply the parameters explicitly or let the server supply the parameters.

See Also:
Constant Field Values
Category:
Signed: This element is only accessible by signed applications. If you intend to use this element, please visit http://www.blackberry.com/go/codesigning to obtain a set of code signing keys. Code signing is only required for applications running on BlackBerry smartphones; development on BlackBerry Smartphone Simulators can occur without code signing.
Since:
BlackBerry API 3.6.0

DUPLICATE_FINISHED_RECEIVED

static final byte DUPLICATE_FINISHED_RECEIVED
Indicates that an abbreviated or optimised handshake, the client has sent a second (resent) finished message.

This message is generally a warning.

See Also:
Constant Field Values
Category:
Signed: This element is only accessible by signed applications. If you intend to use this element, please visit http://www.blackberry.com/go/codesigning to obtain a set of code signing keys. Code signing is only required for applications running on BlackBerry smartphones; development on BlackBerry Smartphone Simulators can occur without code signing.
Since:
BlackBerry API 3.6.0

EXPORT_RESTRICTION

static final byte EXPORT_RESTRICTION
Indicates that a negotiation not in compliance with export restrictions was detected; for example, attempting to transfer a 1024 bit ephemeral RSA key for the RSA_EXPORT handshake method.

This message is always fatal.

See Also:
Constant Field Values
Category:
Signed: This element is only accessible by signed applications. If you intend to use this element, please visit http://www.blackberry.com/go/codesigning to obtain a set of code signing keys. Code signing is only required for applications running on BlackBerry smartphones; development on BlackBerry Smartphone Simulators can occur without code signing.
Since:
BlackBerry API 3.6.0

PROTOCOL_VERSION

static final byte PROTOCOL_VERSION
Indicates that the protocol version the client has attempted to negotiate is recognized, but not supported. (For example, old protocol versions might be avoided for security reasons).

This message is always fatal.

See Also:
Constant Field Values
Category:
Signed: This element is only accessible by signed applications. If you intend to use this element, please visit http://www.blackberry.com/go/codesigning to obtain a set of code signing keys. Code signing is only required for applications running on BlackBerry smartphones; development on BlackBerry Smartphone Simulators can occur without code signing.
Since:
BlackBerry API 3.6.0

INSUFFICIENT_SECURITY

static final byte INSUFFICIENT_SECURITY
Returned instead of handshake_failure when a negotiation has failed specifically because the server requires ciphers more secure than those supported by the client.

This message is always fatal.

See Also:
Constant Field Values
Category:
Signed: This element is only accessible by signed applications. If you intend to use this element, please visit http://www.blackberry.com/go/codesigning to obtain a set of code signing keys. Code signing is only required for applications running on BlackBerry smartphones; development on BlackBerry Smartphone Simulators can occur without code signing.
Since:
BlackBerry API 3.6.0

INTERNAL_ERROR

static final byte INTERNAL_ERROR
Indicates that an internal error unrelated to the peer or the correctness of the protocol makes it impossible to continue (such as a memory allocation failure).

This message is always fatal.[WTLS2] or critical.

See Also:
Constant Field Values
Category:
Signed: This element is only accessible by signed applications. If you intend to use this element, please visit http://www.blackberry.com/go/codesigning to obtain a set of code signing keys. Code signing is only required for applications running on BlackBerry smartphones; development on BlackBerry Smartphone Simulators can occur without code signing.
Since:
BlackBerry API 3.6.0

USER_CANCELLED

static final byte USER_CANCELLED
Indicates that this handshake is being canceled for some reason unrelated to a protocol failure. If the user cancels an operation after the handshake is complete, just closing the connection by sending a close_notify is more appropriate. This alert should be followed by a close_notify.

This message is generally a warning.

See Also:
Constant Field Values
Category:
Signed: This element is only accessible by signed applications. If you intend to use this element, please visit http://www.blackberry.com/go/codesigning to obtain a set of code signing keys. Code signing is only required for applications running on BlackBerry smartphones; development on BlackBerry Smartphone Simulators can occur without code signing.
Since:
BlackBerry API 3.6.0

NO_RENEGOTIATION

static final byte NO_RENEGOTIATION
Sent by the client in response to a hello request or by the server in response to a client hello after initial handshaking. Either of these would normally lead to renegotiation; when that is not appropriate, the recipient should respond with this alert; at that point, the original requester can decide whether to proceed with the connection. One case where this would be appropriate would be where a server has spawned a process to satisfy a request; the process might receive security parameters (key length, authentication, etc.) at startup and it might be difficult to communicate changes to these parameters after that point. This message is always a warning.

See Also:
Constant Field Values
Category:
Signed: This element is only accessible by signed applications. If you intend to use this element, please visit http://www.blackberry.com/go/codesigning to obtain a set of code signing keys. Code signing is only required for applications running on BlackBerry smartphones; development on BlackBerry Smartphone Simulators can occur without code signing.
Since:
BlackBerry API 3.6.0





Copyright 1999-2011 Research In Motion Limited. 295 Phillip Street, Waterloo, Ontario, Canada, N2L 3W8. All Rights Reserved.
Java is a trademark of Oracle America Inc. in the US and other countries.
Legal