On Mon, Jan 27, 2014 at 2:22 PM, wrote:
> In case anyone is keeping a list, while helping a relative I determined
> that timewarnercable.com's login server (wayfarer.timewarnercable.com)
> will not work with tls 1.1 or 1.2. The connection fails after the client
> right after the client hello.
>
Julien Vehent writes:
>> I had to set security.tls.version.max to 1 to get ff (26) or sm (2.23)
>> to get her (relevant) profile to log in to their site.
>
> Are you saying that the default settings were failing entirely, and
> you had to force tls1 for this site?
I thought that profile had the
On 2014-01-27 17:22, cl...@jhcloos.com wrote:
In case anyone is keeping a list, while helping a relative I determined
that timewarnercable.com's login server (wayfarer.timewarnercable.com)
will not work with tls 1.1 or 1.2. The connection fails after the client
right after the client hello.
A
On Monday, January 27, 2014 4:35:34 PM UTC-7, Brian Smith wrote:
> On Mon, Jan 27, 2014 at 10:49 AM, wrote:
>
> > On Monday, January 27, 2014 10:52:44 AM UTC-7, Brian Smith wrote:
>
> >> On Mon, Jan 27, 2014 at 9:26 AM, wrote:
Thanks much Brian and Alan for the links - and the 800-52 referen
Le lundi 27 janvier 2014 19:28:51 UTC+1, Kathleen Wilson a écrit :
> Draft Design Doc posted by Ryan Sleevi regarding Chrome migrating from
>
> NSS to OpenSSL:
>
>
>
> https://docs.google.com/document/d/1ML11ZyyMpnAr6clIAwWrXD53pQgNR-DppMYwt9XvE6s/edit?pli=1
>
> "Switching to OpenSSL, however
5 matches
Mail list logo