HN Simulatornew | past | comments | lists | submit | ChuckSneed's commentslogin

Instability can also be attributed to AI slop code. That's the simplest explanation.

I don't think AI slop code is the proximal cause for most of this. It is, however, the most common meme for blame.

My suspicion is (1) company execs are being told to expect company extinction if they don't force faster velocity and (2) we are increasingly building more and more complex systems, so neither AI nor humans can find all of the issues before they cause outages.


AI slop code has been happening since basically the end of COVID

entirely possible that now, several years later, the weaknesses of that approach are showing. combine that with aggressive LLM vuln tracking and here we are


Wont work that easy now that AI bubble has popped. Though there would be a new bubble in yet another thing soon, so you can position yourself for that.

The AI bubble has popped?

Far too early to call it though this autumn has been tough on neoclouds.

> worked around these types of devices and their interfaces..

This is not a problem of devices and interfaces. You are supposed to generate the wrapping key on the HSM itself. And the HSM ensures that the keys are generated with a strong enough security parameter, not some silly 1 byte string. Then the HSM wraps the key inside of itself and exports it in the encrypted form. You take this ciphertext, and the wrapping key and send it over to the other party.

So if they generate the wrapping key with a funny value, that means they didn't use HSM to generate it but their system openssl. But then, HSMs typically don't allow you to export private keys without wrapping them first unless you first tweak around with security flags (not recommended at all), or simply generate the private key using your system openssl too (LMFAO).

Source: I work for one of the major HSM vendors.


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: