Having worked around these types of devices and their interfaces, I doubt they intended to create weak keys.
It is more likely they had a script which placed a parameter in the wrong field, due to something like using positional arguments. Or they misread the documentation for some interface.
Still incompetence. And I would love to see my theory confirmed or refuted.
The previous discussion advanced the theory that they fucked up the string handling. Eg in Python, output = key[0] would result in one-byte keys like "4" if you expect "key" to be an array, but it's actually a string.
I hear you in terms of how these kinds of mistakes typically happen. But why did the script ever produce two sets of keys? The initial root cause was somebody picked the weak key not the strong key. But what was the reason for ever producing a weak key in the first place? They say the script produced two outputs - what on earth for??
> 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).
You'd generate the wrapping key on the HSM you're importing to, and then you'd load it into the HSM you're exporting from. I suspect it is that loading that they messed up.
I mean, why have the ability to generate weak keys to begin with? Serious question, I've never done this sort of work. What sort of utility does that bring to the procedures and workflows one does in that line of work?
If you didn't know better, you'd think this had been done on purpose by some three-letter agency.
The description of the issue I read I believe said they were exporting the keys and then re-importing them. I suspect they made a mistake when re-importing the keys. Certainly sounds like a major weakness in the tooling or API though.
What testing would require it? I've done plenty of testing setting up internal CAs & HSMs, and none of it required weak keys. Generating a key with the same parameters as a real key is trivially easy, and has the benefit of testing your key generation at the same time!
I have this same discussion with folks applying formal methods to prove the correctness of software where I work. Often the "proof" is harder to read than the original code and I certainly don't feel anyone has proven anything to me.
It’s my choice to use (or not use) Gmail. What data I share with them in exchange for their service is non of Amazon’s business. (If Amazon wanted to make this feature opt-in, sure, whatever.)
It was absolutely formative for my later tastes in science fiction. For a while, I thought it was something from a fever dream until I found a DVD on eBay.
If there is more friction to communicate with me I expect to hear from people less often.
As an example, my friends that only use Discord and not SMS or Signal definitely hear from me less frequently. It doesn’t mean we’re not friends, but we do communicate less frequently.
The date of the notice is October 28th. The separation dates given in the letter are 90 days out from the date of the notice (for some technical reasons, some employees had a separation dates a bit further out.)
It is more likely they had a script which placed a parameter in the wrong field, due to something like using positional arguments. Or they misread the documentation for some interface.
Still incompetence. And I would love to see my theory confirmed or refuted.