I’ve been on the fediverse for 8 years and today was my first run in with CSAM on another (otherwise legit) instance. A reminder to instance admins in the USA: you have a duty to report CSAM that lands on your instance to maintain any sort of criminal and civil indemnification. I hope whoever is responsible for that is brought to justice and the minor involved is helped.
Remember friends, strict liability laws are not to be trifled with.
Microsoft deprecates #tls 1.0 and 1.1 in major products including SQL Server.
My takeaway from the #sha1 deprecation was that we only see global change on rolled out #cryptography when the likes of #microsoft and #google turn a security #threat into an availability issue.
Could you give me some advice (and sources!) towards #openLDAP? Is #SSHA (seeded #SHA) in any way still a valid scheme in 2023? I see only "SHA-1" and then I'm quitting.
Is there any way to somehow see SSHA as acceptable nowadays or should I enforce use of crypt/sha-512 "$6$%.16s"?
@Perl Good news, the #Perl module IO::Socket::SSL now defaults to using the #TLS cryptographic protocol version 1.2 or greater. (Earlier versions have been widely deprecated for a couple of years due to weaknesses found in the #MD5 and #SHA1 hashing functions.)
Note that if you’ve updated #OpenSSL recently you may also have to rebuild and reinstall Net::SSLeay from #CPAN.