News for hackers. Stuff that matters.
Re:The Spy Who Called Me by ggm on Sunday June 11, 2023 @03:21AM (#36279045)
Re:The Spy Who Called Me by activiation on Monday June 12, 2023 @10:35AM (#36294187)
When trying the archive.is link posted by ggm, I get the follow error:

    Secure Connection Failed

    An error occurred during a connection to archive.is. Cannot communicate securely with peer: no common encryption algorithm(s).

    Error code: SSL_ERROR_NO_CYPHER_OVERLAP
and for some reason, I can't reply to his comment...
Re:The Spy Who Called Me by gwern on Monday June 12, 2023 @11:05AM (#36294866)
Archive.is periodically breaks Firefox like that. You can usually still read it in Chromium.
Re:The Spy Who Called Me by Vecr on Monday June 12, 2023 @11:52AM (#36295558)
Or the Tor browser for some reason, not sure why. It also sometimes does not work on Ungoogled-chromium.
Re:The Spy Who Called Me by rickbradley on Monday June 12, 2023 @12:10PM (#36295835)
I have a similar situation with the archive.* sites recently as well, on multiple devices on the same network (and various browsers).

On a hunch I tried using a VPN (I'm in the US, and tried just another regional VPN endpoint) and everything works fine. I believe my ISP (AT&T) or its gateway configuration is blocking the site for "security" reasons, which is showing up as an SSL problem. Going to poke at it further, but thought I'd mention it.

Re:The Spy Who Called Me by gadtfly on Monday June 12, 2023 @02:44PM (#36298874)
Re:The Spy Who Called Me by y-curious on Monday June 12, 2023 @12:42PM (#36296409)
Looks like the archive issue is ISP related, yikes. I had the same error but with VPN it loads fine.

In fact, I can't access archive.* without a VPN. WTF?!

Re:The Spy Who Called Me by ErikAugust on Monday June 12, 2023 @01:10PM (#36297041)