Painfully slow and/or timing out again....

Is this issue with PHP the problem RyPN has been affected by: https://www.theguardian.com/technology/ ... -shutdowns I am not a tech dude so my eyes glazed over while reading it, but it seems plausible.

On top of all the other issues that have been discussed, now there's this massive PHP vulnerability wreaking havoc across the internet, and one can only imagine the threat that it represents for a website such as this running on very old architecture.

On a semi-related note, with all the functions that have one by one become disabled within RYPN, is the password manager still operating properly, or have we now been locked out from changing our p/w as well...?

PHP is server-side software and does not reside on your device so you won't be directly hacked. Patching it is entirely on the hosting company. RYPN would be at the mercy of a hacked server not being able to do what it's supposed to do but the RYPN domain doesn't hold any monetary value to a hacker. The hosting company's server could hold a treasure trove of data and therein lies the problem as the hackers can steal that data and even take down websites just because they can. RYPN doesn't hold any valuable personal data other than email addresses which are probably already in databases for sale by data brokers anyway. The only threat here is if a hacker trashes the website but like I said, there's no value here so why bother.

That fix has already been issued and it's up to the hosting companies to patch their systems with the latest stable PHP versions. I imagine that's going pretty quickly if not done already.

Yes, the password manager is still there, at least the GUI. Does it work? Dunno. I ain't gonna be that guinea pig and try it.

Mini rant: I believe RYPN's problems are due to old software (actually ancient as far as software goes) running on the latest versions of PHP. For an example of the missing functions such as emailing from within this software, support for the deprecated "mail" function in PHP ended quite a while ago and was replaced with a much more secure, standards compliant "phpmail" function. So rather than upgrade the software which is a pain in the a$$, just disable the function. Same with the other functions that are now gone.

Was well aware that PHP is entirely server-side, not client-side, and that RYPN is not a "target", other than if someone only wanted to "troll" us rail preservationists specifically.

But it is interesting, your theory that the PHP version "age" is not the issue with RYPN, but that the problem is actually the opposite, latest PHP trying to run a "grandfathered" website software.

And as far as the p/w question, I too was not going to test it on myself, but was curious if anyone else had successfully made a p/w change recently w/o issue.