https://substack.com/home/post/p-150426450

FYI. They had a stab at both.

FYI you’re at the mercy of the linux heap manager still no matter what you use.. Also, nothing gcc offers protects from COOP and some types of heap based exploits.. You basically got to compartmentalize and encrypt..

Oh, but they’re still out there today.

In August, a security researcher found that GivEnergy, a home solar power management system used in the UK, had used a 512 bit key to secure their administrative account. Ryan was able to factor the key in about 24 hours using $70 of cloud compute time, and was then in a position where they were able to control the power generation of 60,000 customers. (They didn’t, of course.)

GivEnergy stated that their system had been built years earlier by a tiny startup team of two developers (one junior), who knew nothing of cryptography and so they generated keys from the defaults of whatever options the library offered them.

Now, multiply that by the number of other cryptographically clueless developer teams from the early 2000s and imagine that a lot of them are still running whatever default crypto their developers picked.

https://arstechnica.com/security/2024/08/home-energy-system-gives-researcher-control-of-virtual-power-plant/

AES is symmetric so will always be quantum resistant. I heard somewhere that quantum computers could somehow halve the apparent strength of AES (take 1 bit off the key length), but this is just halving the multiple-times-the-age-of-the-universe needed to defeat AES. Symmetrric crypto is under no threat from quantum computing, the trouble is that it isn’t as parctical for use in real-world scenarios as assymmetric crypto is.

I also imagine “…on the boarder…” was meant to be “border”, unless Linux boxes are now taking on passengers.

It really is RSA. AES is still considered quantum resistant. Let me add one of the other sources I was looking at as a second link.