Disabling TLS 1.0 and 1.1 on RIPE Atlas anchors
Dear RIPE Atlas users, We received reports that the availability of TLS 1.0 and 1.1 on RIPE Atlas anchors triggers some security alarms for some anchor hosts. Since the anchors don't host anything sensitive, and the measurment code is not expected to be affected by this, we will stop supporting these protocols on the anchors (*) as of *1 September*. We'll carry on with supporting TLS 1.2 (*) the RIPE Atlas website/UI will be unchanged for the time being although we expect similar changes in the near future Regards, Robert Kisteleki RIPE NCC
Update: this work has been completed. Regards, Robert On 2020-08-10 11:55, Robert Kisteleki wrote:
Dear RIPE Atlas users,
We received reports that the availability of TLS 1.0 and 1.1 on RIPE Atlas anchors triggers some security alarms for some anchor hosts. Since the anchors don't host anything sensitive, and the measurment code is not expected to be affected by this, we will stop supporting these protocols on the anchors (*) as of *1 September*. We'll carry on with supporting TLS 1.2
(*) the RIPE Atlas website/UI will be unchanged for the time being although we expect similar changes in the near future
Regards, Robert Kisteleki RIPE NCC
On 1 Sep 2020, at 13:40, Robert Kisteleki wrote:
Update: this work has been completed.
Hi Robert, atlas-stream.ripe.net seems to be broken on HTTP. Is that related to this change? Best regards, -- Teun Vink BIT | teun@bit.nl | +31 318 648 688 KvK: 09090351 | GPG: 0xFC8B25D6 | RIPE: TEUN-RIPE
On 01/09/2020 14:07, Teun Vink wrote:
Hi Robert,
atlas-stream.ripe.net seems to be broken on HTTP. Is that related to this change?
Hi Teun, This is an unrelated issue that we are looking into. I'll let you know when the solution is ready. Regards, Chris
This issue is now resolved, atlas-stream.ripe.net should work correctly again over plain HTTP. On 01/09/2020 15:26, Chris Amin wrote:
On 01/09/2020 14:07, Teun Vink wrote:
Hi Robert,
atlas-stream.ripe.net seems to be broken on HTTP. Is that related to this change?
Hi Teun,
This is an unrelated issue that we are looking into. I'll let you know when the solution is ready.
Regards,
Chris
On 1 Sep 2020, at 15:50, Chris Amin <camin@ripe.net> wrote:
This issue is now resolved, atlas-stream.ripe.net should work correctly again over plain HTTP.
Confirmed: https://bit.org/network/ is showing dots again :) Thanks for the quick fix! cheers, -- Teun Vink BIT | teun@bit.nl | +31 318 648 688 KvK: 09090351 | GPG: 0xFC8B25D6 | RIPE: TEUN-RIPE
participants (3)
-
Chris Amin -
Robert Kisteleki -
Teun Vink