FYI, fix checked into master, DOGTAG_10_1_BRANCH , and DOGTAG_10_2_0_BRANCH
commit info can be found in:
Yes, unlike browsers, who talk to random unknown ssl servers, our
cli's and java console clients only talk to Dogtag cs servers. We
just depend on the cs server settings for restrictions. The code
changes in the areas that affect cli's and java console are only to
make sure we can work within whatever tls ranges the cs servers set it
to, e.g. tls1_2 - tls1_2.
thanks,
Christina
On 11/24/2014 11:27 AM, John Magne wrote:
> ACK
>
> With the caveat that it might have been nice to have these settings
> to be configurable, but as I understand it,
> there is no need to because this code is talking to one of our own
> servers with well known requirements.
>
> ----- Original Message -----
> From: "Christina Fu" <cfu(a)redhat.com>
> To: pki-devel(a)redhat.com
> Sent: Friday, November 21, 2014 6:06:34 PM
> Subject: [Pki-devel] [PATCH]
> Ticket-1206-java-console-TLS-range-support-code-chan.patch
>
> attached is the java console part of client side changes for TLS range
> support:
>
https://fedorahosted.org/pki/ticket/1206 TLS range support: code change
> needed for cs when acting as client
>
> Please review.
> thanks,
> Christina
>
> _______________________________________________
> Pki-devel mailing list
> Pki-devel(a)redhat.com
>
https://www.redhat.com/mailman/listinfo/pki-devel
_______________________________________________
Pki-devel mailing list
Pki-devel(a)redhat.com
https://www.redhat.com/mailman/listinfo/pki-devel