search

bettybop68 / android-rcs-ims-stack

Automatically exported from code.google.com/p/android-rcs-ims-stack
0 stars 1 forks source link

mplementation Server Name Identification from Transport Layer Security (TLS) Extensions for Configuration #170

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Trying to auto-provision the client
2.
3.

What is the expected output? What do you see instead?
Client should be provisioned. However not provisioned

What version of the product are you using? On what operating system?
app latest v2.5.11  .. android 4.x version

Please provide any additional information below.
Implementation Server Name Identification from Transport Layer Security (TLS) 
Extensions for Configuration:

For Configuration, the client sends a DNS request to its FQDN.

Once it’s got DNS response the mobiles sends a the blank Get request and then 
it starts the TLS session.

In the handshake message the mobile is not indicating the server name. In case 
of two different host running in one machine (for example config.00101.rcse and 
config.rcs.mnc001.mcc001.pub.3gppnetwork.org) then the SSL server has no clue 
about which server certificate to use for handshake. 

On implementing the Server Name Indication from RFC 4366, the SSL server can 
identify the server client is requesting and respond back accordingly.

Can anyone please confirm, if this  feature is available, if not is it in 
roadmap?

Original issue reported on code.google.com by sharique...@gmail.com on 17 Oct 2013 at 3:31

GoogleCodeExporter commented 8 years ago 
Thanks for this information, we don't have a lot of feedback on TLS part...
Unfortunately,  not implemented and not in roadmap...

The HTTPs provisioning use classes org.apache.http in 
HttpsProvisioningManager.java.
If you want contribute, we will be very happy to integrate a modification.

Original comment by benoit.j...@gmail.com on 12 Nov 2013 at 2:26