On Friday 18 September 2009 15:29:29 tensy joseph wrote:
> but this all extensions are not supported in openssl 9.8k.
> I have another query .
>
> If my server is using older openssl version like 9.8d which does not
> support tls extension by default and my client is using openssl 9.8k which
> s
Hi Daniel,
I have gone through tls.h header file and i can see this
/* ExtensionType values from RFC 3546 */
#define TLSEXT_TYPE_server_name 0
#define TLSEXT_TYPE_max_fragment_length 1
#define TLSEXT_TYPE_client_certificate_url 2
#define TLSEXT_TYPE_trusted_ca_keys 3
#define TLSEXT_TYPE_trun
Hi Daniel,
I have gone through tls.h header file and i can see this
/* ExtensionType values from RFC 3546 */
#define TLSEXT_TYPE_server_name 0
#define TLSEXT_TYPE_max_fragment_length 1
#define TLSEXT_TYPE_client_certificate_url 2
#define TLSEXT_TYPE_trusted_ca_keys 3
#define TLSEXT_TYPE_trun
On Wednesday 05 August 2009 17:09:54 rajanchittil wrote:
> Hi ALL,
Hi rajanchittil
> I was trying to figure out the TLS extension supported by openssl. I have
> gone thorough RFC 3546 (http://www.faqs.org/rfcs/rfc3546.html) .It mentions
> 6 TLS extension
could look at the updated rfc4366 too
>
.Truncated HMAC
6.Certificate Status Request
But i was able to figure out only Server name and certificate status
request supported in Openssl.
Is other extension is supported too .
Please Help.
Thanks In Advance
Rajan
--
View this message in context:
http://www.nabble.com/TLS-extension
Hi All,
Can any one tell me when "SessionTicket TLS Extension" support will be
included in openssl library?
Thanks in advance.
Regards,
Jaya.
__
OpenSSL Project http://www.openss
Dear OpenSSL developpers,
I have put a version of openssl that supports the TLS servername extension
into our web server. It is based on a openssl development snapshot of
last week.
We have split of and simplified the code that was done together with SRP
last year, an,d corrected known bugs.
S
Hi,
While discussing the proper implementation for TLS support for (open)ser SIP proxy (currently using OpenSSL), we came up with somehow a showstopper: when the server serves multiple domains, we'd like to present a different certificate depending on which domain the incoming message is directed
