HN user

alphager

643 karma
Posts1
Comments208
View on HN

I work as a security architect in a major European company. We're currently demanding a full cryptographic inventory of every new product purchased or service built in-house and will start demanding PQC in 2028.

Not because we expect a workable quantum computer by 2030 (current estimates are around 2035-2040), but because stuff survives for decades in large enterprises (especially if it touches hardware in any way. Think OT, think controllers for all kinds of machines).

Now that PQC is standardized, there's no gain not to demand it (it's basically a demand to use a current openSSL/libreSSL/$library), but not demanding it now will cause a major headache once/if quantum computers work.

TLS connection speed matter only for a very tiny niche of applications; those will choose according to their needs. For the general case, it just doesn't matter.

If your threat model includes store-now-decrypt-later, you should have been demanding PQC for years.

ZFS on Linux works great, but with most distributions, it will compile the kernel module on device upon installation. Only Ubuntu distributes binaries.

As a consequence, you don't necessarily want a rolling distro, as the ZFS module can get out of sync with the kernel.

ZFS itself is build for both BSD and Linux from the same source, so there's feature parity there.

It is absolutely bonkers to think about using UV to disinfect human skin, let alone the inside of the human body.

Any UV radiation strong enough to destroy the cells of bacteria is strong enough to destroy human cells. We know that UV-radiaton that's not strong enough to kill bacteria is already harmful to human skin (we call the phenomenon sunburn).

Absolutely true in the real world; I was part of a real team that explored quantum optimization algorithms as part of a strategic initiative (my day job is algorithmic optimization on classical computers).

Our problem is similar (but not identical) to the traveling salesman problem. We run on a tight time constraint (measured in days for the complex type and measured in minutes for the simple type).

We're running approximations on classic computers but estimate that we'd save billions if we could reach optimum.

It's in all kinds of medicine. People take some pills and then add a cough syrup, not noticing that the syrup also contains it as an active ingredient.

Stealing is one possible problem (transactions out of country are really hard to claw back), but the major fear is probably stability. You won't like the consequences if a significant percentage of your countries banks are down for a few days...

I've seen this happen with both juniors and seniors. They do come back with a working solution /for the happy path/. Because the happy path is easy. It turns out that most of the complexity sits in the unhappy paths.

The 30 seconds (+30-60 seconds to account for clock drift) are long enough to exploit.

TOTP is primarily a defense against password reuse (3rd party site gets popped and leaks passwords, thanks to TOTP my site isn't overrun by adversaries) and password stuffing attacks.