2 ms·
tl;didn't watch (because it is, after all, an hour): * best you can do for secrets if you don't control the secret consuming service (such as an API) is to use
by mooreds 3y ago
tl;didn't watch (because it is, after all, an hour):
* best you can do for secrets if you don't control the secret consuming service (such as an API) is to use a key management service, encrypt your secret and check that into git. Then, when you need to use the secret, call into the key management service, decrypt it, and present it to the service.
* if you do control the service consuming secret, then you can have the production server create a public private keypair, send the public key up to the service, and encrypt and store the private key in a KMS. Then, when you need to access the service, decrypt the private key, use it to sign something (like a JWT), and present it to the service. The service can verify the caller is who gave them the public key.
Slides here: https://docs.google.com/presentation/d/e/2PACX-1vSlrYb8nmtlH8HcVgBRhCnF3-A-Av8WG5YHe6Nte5ly49uL-Ug2JK7wQnPJ6FYi5VZ69vt49y3emLtj/pub?start=false&loop=false&delayms=30000&slide=id.p https://docs.google.com/presentation/d/e/2PACX-1vSlrYb8nmtlH...
Disclosure: I work for a competitor of the presenter.