I'm pretty sure the answer here is no. I can think of nothing which exposes 
that session key, I can believe that it's something an API would not lightly 
expose and I do wonder what you could possibly need it for, especially on iOS, 
I can almost think of ways to use it on OSX, almost, but on iOS I'm struggling 
a bit. 

If you modified openssl you could write a function to get that information over 
an openssl-configured link. That path is pretty fraught with difficulty. 

On 26 Mar, 2014, at 6:30 pm, Bastian Hafer <[email protected]> wrote:

> Hey everyone,
> 
> I am trying to get the session key of an existing, working and tested 
> connection secured via SSL/TLS. The connection is set up using first 
> CFReadStream and CFWriteStream then casted to NSInputStream and 
> NSOutputStream as common. Before I open them I set the properties and values 
> for SSL/TLS. The device I am working on is an iOS-device with the newest iOS 
> 7 installed.
> 
> Now, when the connection is established and working, is there any way to get 
> hands on the session key that is negotiated in the SSL/TLS handshake 
> protocol? I need this key for my app. Maybe via the socket, the stream itself 
> or any object I have not thought about yet?
> 
> Any help appreciated!!
> 
> Cheers,
>  Bastian
> _______________________________________________
> 
> Cocoa-dev mailing list ([email protected])
> 
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
> 
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/cocoa-dev/rols%40rols.org
> 
> This email sent to [email protected]


_______________________________________________

Cocoa-dev mailing list ([email protected])

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to