Finnish medical data is available for researchers, unless if you specifically opt-out. I have, you should, too.
https://findata.fi/en/about-findata/your-data-rights/#how-can-I-exercise-my-rights
| PGP | https://sintonen.fi/pgpkey.txt |
| Research | https://sintonen.fi/advisories/ |
| Github | https://github.com/piru |
Finnish medical data is available for researchers, unless if you specifically opt-out. I have, you should, too.
https://findata.fi/en/about-findata/your-data-rights/#how-can-I-exercise-my-rights
If you upgraded to #OpenSSH 10.1 or later and suddenly have trouble connecting to a server, try: ssh -o ipqos=af21 user@host
If that works, then the network is unhappy about the Expedited Forwarding IP QoS (this is the new default IPQoS for interactive connections with OpenSSH 10.1 and later. -o ipqos=af21 restores the IPQoS used by earlier OpenSSH versions).
#OpenSSL 4.0.0 removed all traces of SSL3 support - including the OPENSSL_NO_SSL3_METHOD define that indicates that SSL3 methods are not available.
This define is used by a lot of code to see if they should try to use SSLv3_client_method() or not. Example: https://github.com/mirror/wget/blob/8775506f632f14404e4755dbae679dea07abf12a/src/openssl.c#L229
I've tried to report a security vulnerability to @signalapp for months now (first attempt was 2025-11-23 to the official security-at email address). I haven't gotten any response from them, even after repeated attempts. This is highly frustrating.
Is there a way to reach them? I don't need any kind of special treatment, just someone acknowledging that the message has been received would be okay.