patch_cable

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.

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.

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.

This is very insightful. I always wonder what the gradients are that we can’t see.

I think the argument is for changing what is legally required.

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.)

I don’t think it is so binary.

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.

That’s a bit uncharitable. It made perfect sense to me. I also learned something about Japanese lacquer.

In the exact same configuration? Yes.

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.)

The books are also physically really pleasant to hold and look at.

I’ve read each book they’ve published and enjoyed them all.

I think they’re saying anyone could order “secure” checks with your account number on them.

Excited to say I worked on this feature! (Standard disclaimer: thoughts and opinions are my own and may or may not be shared by my employer.)

To give an idea of the kinds of things you can do now:

  - Keys or other secrets can only be decrypted (via KMS) by an EC2 instance if it is running an approved AMI. 
  - You could build a certificate authority (CA) which only issues a certificate to an instance running an approved AMI. 

This is similar to the functionality that was available in Nitro Enclaves. However, enclaves came with restrictions (such as only being able to communicate through a vsock) that made them not a great fit for all use cases.