Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 11 submissions in the queue.
Meta
posted by NCommander on Wednesday July 05 2023, @02:23AM   Printer-friendly
from the ssl-negotations-are-complex dept.

So, I know its been a bit quiet here, but we're working through getting through the last few items relating to cutting over to newer infrastructure. As such, its been working through the bug list, and there's one issue I want to get some feedback on.

Back in November when the infrastructure was upgraded to Ubuntu 22.04, a few users with older devices stopped being able to connect to SoylentNews. This confused me, since we've been using the same NGINX SSL termination setup that has been in use since at least 2016. Well, I finally found the root cause, and as it turns out, Canonical bumped up the minimum OpenSSL security level, which disabled several ciphers, and broke devices not supporting TLS 1.2 or later.

By testing the site with the SSL Labs site checker, it appears anything older than Android 4.0, or iOS 5 is broken. This mostly seems to be devices that are over a decade old at this point, and won't be able to browse the vast majority of sites on the Internet as is. We discussed this internally a bit, and I'm of the opinion that its not worth re-enabling the older ciphers to allow these devices to reconnect, especially since we're working to modernize the stack, and get it as up to date as we can get it. I also believe we had very few users who were actually affected by this, however, as the editors did get a few emails about SN breaking after the site upgrade, I wanted to poll the community, and make sure this is not a more widespread issue than initially believed.

Ultimately, this is going to be part of a broader discussion on what we will and won't support on SoylentNews going forward, and this seems as good of place as any to get the ball rolling.

~ NCommander

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 2) by Rich on Wednesday July 05 2023, @01:25PM (1 child)

    by Rich (945) on Wednesday July 05 2023, @01:25PM (#1314536) Journal

    Having logins over https is not a good idea, for anon posting it shouldn't make much of a difference. Annoyers can post over https anyway and afterwards, the post is readable in the clear.

    Would it be a reasonable idea that users can get themselves a TAN (transaction number) sheet for logins from an https login to use those to login over http? They'd only have to use it when they want to post under a UID anyway. I don't think live spoofing would be much of a risk with this site's feature profile. It would require significant development effort, but might be considered once everything else is done. It'd probably best, though, to run a poll if anyone would use such a fringe feature before committing any effort...

    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2  
  • (Score: 3, Touché) by gnuman on Wednesday July 05 2023, @02:35PM

    by gnuman (5013) on Wednesday July 05 2023, @02:35PM (#1314548)

    HTTP is only good for reading, if you don't care if traffic is modified in the middle. With some ISPs inserting their stupid ads in middle of 3rd party websites; it's one of the main reasons that HTTPS-everywhere became the norm.

    Write access over HTTP is always a bad idea since any session is basically in clear text.