What is handshaking and how is it optimized for supporting Wireless Environment?
Handshaking is used to determine key exchange suite, bulk encryption and MAC algorithm. 

How many types of authentication Jataayu supports (class I, II, III)?
Jataayu supports both class I and class II types of authentication. The class III type of authentication is also supported by WAP standard. The specifications are for Client Certificates and client authentication. It is for the devices to support the specifications and not the WAP gateway. 

How does Class I authentication takes place i.e. how can you say that message sent is secure?
In the Class I authentication, keys are generated randomly and the handshake happens using the same. Though, there is no authentication happening here, the messages sent are still encrypted and hence secure. Class I takes care of both confidentiality and integrity. 

How does Class II & Class III authentication take place?
Class II authentication takes place when the server gets authenticated by the client. It is achieved using Server Certificates. Class III authentication takes place when both the server and the client get authenticated. It is achieved using both server and Client Certificates. 

How are the Server Certificates sent on the air for server authentication?
Server certificates are sent as a part of the handshake. This is dependent on the algorithm which gets decided during the initial part of handshake and accordingly, the Server Certificate is sent. 

Is only the certificate ID sent for authentication? 
No, the entire certificate is sent for authentication. 

How does the Server Certificate get validated at the handset?
The Public Key of the ROOT should be known to the client. In case the Server Certificate is issued by an authorized agent of the ROOT, the Remote Agent (RA) gets authenticated by the Public Key of the ROOT. Then using the Public Key of RA, the Server Certificate gets validated. 

Is it necessary to store the trusted certificates on the handset?
For client authentication, the Client Certificates must be stored on the handset. Currently, this is not supported by the devices. 

What happens if the Server Certificate sent is not installed in the handset?
It is not necessary to install the Server Certificates on the handset. Only the public key of the CA is needed on the handset. 

What will happen if the CA Root certificate of the Server Certificate sent is not installed on the handset?
In this case, the client warns the user with a message to continue the session without ROOT Certificate validation.

How does Jataayu take care of confidentiality? 
Confidentiality is maintained by encrypting the data using symmetric key algorithm. Certicom's WTLS libraries which are integrated with our Gateway, encrypt data as per the WAP specifications. 

What algorithms are supported by Jataayu?
Jataayu supports the following types of algorithms:

Key Exchange Algorithms 
RSA 
Diffie-Hellman 
Elliptic Curve Diffie-Hellman 
Elliptic Curve Digital Signature Algorithm 
Encryption and Hash Algorithms 
DES_CBC_SHA_0 
3DES_CBC_SHA_0 
NULL_SHA_40 
DES_CBC_SHA_40 
3DES_CBC_SHA_40 
NULL_SHA_80 
DES_CBC_SHA_80 
3DES_CBC_SHA_80 
NULL_SHA 
DES_CBC_SHA 
3DES_CBC_SHA 
NULL_MD5_40 
DES_CBC_MD5_40 
3DES_CBC_MD5_40 
NULL_MD5_80 
DES_CBC_MD5_80 
3DES_CBC_MD5_80 
NULL_MD5 
DES_CBC_MD5 
3DES_CBC_MD5 
RC5_CBC_56_SHA_0 
RC5_CBC_56_SHA_40 
RC5_CBC_56_SHA_80 
RC5_CBC_56_SHA 
RC5_CBC_SHA_0 
RC5_CBC_SHA_40 
RC5_CBC_SHA_80 
RC5_CBC_SHA 

 

General FAQ
Carrier WAP Server FAQ
Enterprise WAP Server FAQ