Changes between Version 1 and Version 2 of TLS_on_Symbian


Ignore:
Timestamp:
Aug 31, 2009 3:14:59 PM (10 years ago)
Author:
nanang
Comment:

Highlighted few words and fixed typos.

Legend:

Unmodified
Added
Removed
Modified
  • TLS_on_Symbian

    v1 v2  
    44[[PageOutline(2-3,,inline)]] 
    55 
    6 PJSIP provides SSL/TLS via secure socket abstraction, {{{pj_ssl_sock_*}}}, which can be used by the higher level applications, such as SSL/TLS SIP transport. On Symbian platforms, the secure socket implementation is done natively using {{{CSecureSocket}}} class. 
     6PJSIP provides secure communications via secure socket abstraction, {{{pj_ssl_sock_*}}}, which can be used by the higher level applications, such as SSL/TLS SIP transport to perform secure SIP signaling. On Symbian platforms, the secure socket implementation is done natively using {{{CSecureSocket}}} class. 
    77 
    88[[BR]] 
     
    1010== Scope == 
    1111Secure socket implementation on Symbian provides: 
    12  1. Transparent SSL/TLS operations, application uses the secure socket basically the same way as normal socket, e.g: when connection completion status is reported (via callback) as successful, it means that both the underlying socket connection and the SSL/TLS handshake are successful. 
     12 1. Transparent SSL/TLS operations, application uses the secure socket basically the same way as using normal socket, e.g: when connection completion status is reported (via callback) as successful, it means that both the underlying socket connection and the SSL/TLS handshake are successful. 
    1313 1. Active socket operations as provided by [[http://www.pjsip.org/pjlib/docs/html/group__PJ__ACTIVESOCK.htm Active Socket I/O]]. 
    1414 1. List of trusted Certificate Authorities (CA) is based on Symbian Certificate Management, e.g: in E65, Main Menu > Tools > Settings > Security > Certificates Management. 
     
    1818 1. Only support for client mode ({{{CSecureSocket}}} limitation). 
    1919 1. Specifying client credential (e.g: certificate and the corresponding private key) is not supported ({{{CSecureSocket}}} limitation), so secure socket may not be able to connect to server that requires client certificate. 
    20  1. Currently, server certificate verification is only done internally by {{{CSecureSocket}}}, further verification mechanism by application (e.g: via callback) is not supported. Note that untrusted server certificates result in a user dialog. 
     20 1. Currently, server certificate verification is only done internally by {{{CSecureSocket}}}, further verification mechanism by application (e.g: via callback) is not supported. '''Note''' that untrusted server certificates result in a user dialog. 
    2121 1. Managing (adding/editing/deleting) entry of trusted CA list should be handled by application. 
    2222 
     
    3434#define SIP_PROXY       "<sip:some_proxy;transport=tls;lr>" 
    3535}}} 
    36 Note that without registering an account into a registrar, symbian_ua will not be able to be contacted (e.g: receive calls), as the secure socket backend ({{{CSecureSocket}}}) can only work as client. 
     36'''Note''' that without registering an account into a registrar, symbian_ua will not be able to be contacted (e.g: receive calls), as the secure socket backend ({{{CSecureSocket}}}) can only work as client. 
    3737 
    3838== Building your own application using SSL/TLS on Symbian == 
    39  1. If the low level secure socket is needed, include {{{ssl_sock.h}}}: 
     39 1. If the '''low level''' secure socket is needed, include {{{ssl_sock.h}}}: 
    4040{{{ 
    4141#include<pj/ssl_sock.h> 
    4242}}} 
    43  1. When using PJSUA-LIB, SIP transport TLS can be enabled by instantiating SIP transport type {{{PJSIP_TRANSPORT_TLS}}}, e.g (captured from symbian_ua {{{ua.cpp}}}): 
     43 1. When '''using PJSUA-LIB''', SIP transport TLS can be enabled by instantiating SIP transport type {{{PJSIP_TRANSPORT_TLS}}}, e.g (captured from symbian_ua {{{ua.cpp}}}): 
    4444{{{ 
    4545pjsua_transport_config tcfg; 
     
    5353// e.g: "<sip:some_proxy;transport=tls>" 
    5454}}} 
    55  1. Link the application to {{{securesocket.lib}}}, by specifying the library in the application MMP: 
     55 1. '''Link''' the application to {{{securesocket.lib}}}, by specifying the library in the application MMP: 
    5656{{{ 
    5757LIBRARY securesocket.lib