And problem causers
Natanael
joined 1 year ago
Turkey says they have flying drones who already have done that, so ...
But it's harder to detect spoken slang when people make it talk in mixed accents and more, you would have to run a talk to text engine too many different times with different filters and parameters against many different languages' lists of slang words with multiple recognizable pronunciations.
And then somebody names themselves ChatGPT and the French will laugh because that sounds like "cat farted" in their language
P256 isn't known to be insecure if implemented right, it's just harder to implement right
I run a cryptography forum, I know this stuff, and the problem isn't algorithmic weakness but complexity of implementation.
All major browsers and similar networking libraries now have safe implementations after experts have taken great care to handle the edge cases.
It's not a fault with let's encrypt. If they allowed nonstandard curves then almost nothing would be compatible with it, even the libraries which technically have the code for it because anything not in the TLS spec is disabled.
https://cabforum.org/baseline-requirements-certificate-contents/
CAB is the consortium of Certificate Authorities (TLS x509 certificate issuers)
With that said curve25519 is on its way into the standards
You can't use arbitrary curves with certificates, only those which are standardized because the CA will not implement anything which isn't unambiguously defined in a standard with support by clients.
On the contrary, these tools only work when the phone has been unlocked since boot on any modern phone, so you can turn it off or reboot it
Good luck in court
They even brag about it
https://m.slashdot.org/story/418156
Make sure your devices are up to date
Lots of lemmy clients have keyword filters
Bluesky has federation in testing with 3rd party clients already existing
Especially if the compiler optimization options inlined code from 5 different places into one blob