This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[atlas] TLS tests with login.live.com
- Previous message (by thread): [atlas] TLS tests with login.live.com
- Next message (by thread): [atlas] TLS tests with login.live.com
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Philip Homburg
philip.homburg at ripe.net
Mon May 29 13:58:13 CEST 2017
On 2017/05/29 13:53 , Stephane Bortzmeyer wrote: > On Mon, May 29, 2017 at 01:41:45PM +0200, > Stephane Bortzmeyer <bortzmeyer at nic.fr> wrote > a message of 5 lines which said: > >> TLS tests from the Atlas probes work for me, for every server... *but* >> login.live.com, for which I always get timeouts (it works with other >> TLS clients). > > Could it be related to this error > <https://twitter.com/wiganshale/status/869141059682660352> which is > reported by many people on the socnets today? > > The Atlas probe checks the OCSP answer? Hi Stephane, No, the Atlas code is nowhere near advanced enough to do that. My guess is that the measurement code sends something the other side doesn't like and then the server responds with something the Atlas code doesn't understand. Philip
- Previous message (by thread): [atlas] TLS tests with login.live.com
- Next message (by thread): [atlas] TLS tests with login.live.com
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]