Comment #1 on issue 93 by [email protected]: NioTlsMessageChannel tries
to parse TLS_CLIENT_PROTOCOLS on its own and fails
http://code.google.com/p/jain-sip/issues/detail?id=93
Attached proposed patch. Changes in two files:
- SipStackImpl: character " as a valid tokenizer to parse
TLS_CLIENT_PROTOCOLS
- NioTlsMessageChannel relies on SipStackImpl parsing instead of parsing on
its own
With this patch, all these options are accepted and processed:
gov.nist.javax.sip.TLS_CLIENT_PROTOCOLS = SSLv3, TLSv1
gov.nist.javax.sip.TLS_CLIENT_PROTOCOLS = SSLv3 TLSv1
gov.nist.javax.sip.TLS_CLIENT_PROTOCOLS = "SSLv3, TLSv1"
Attachments:
patch.issue.93.patch 1.7 KB
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
---
You received this message because you are subscribed to the Google Groups "mobicents-all-issues-changes" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
