Re:How to manage any kind of secret with AWS Secrets Manager
by viraptor on Saturday July 07, 2018 @10:39PM
(#17481880)
> No open source product will meet the requirement, because you often need FIPS validated crypto.
What do you mean? Redhat has FIPS mode. Openssl has FIPS object module. You can create a secrets storage product out of those blocks. Do you mean some specific requirements for the project you were working on?
Re:How to manage any kind of secret with AWS Secrets Manager
by Spooky23 on Sunday July 08, 2018 @03:41PM
(#17485752)
Rolling your own is expensive if you’re getting audited for compliance that includes FIPS or other things.
You need to have a Dev who understands and documents everything, your ops guys need to be careful to not fix a security bug in OpenSSL that leaves you with a non-validated version, etc.
Or you can give AWS $5/secret/year. It’s the path of least resistance.
Re:How to manage any kind of secret with AWS Secrets Manager
by viraptor on Sunday July 08, 2018 @07:39PM
(#17486935)
I agree it's simple to use aws in this case. I meant specifically the claim that "No open source product will meet the requirement". It may not be the financially optimal solution, but that's not "open source" specific.
Re:How to manage any kind of secret with AWS Secrets Manager
by Spooky23 on Tuesday July 10, 2018 @10:16PM
(#17503949)
I see your POV, but I think the distinction is that RHEL
or OpenSSL aren’t vaults. They are components or tools. If RHEL includes a vault product, that would be different.
If I need to sit, I need a chair can support my weight. A box containing 2x4s, a hammer and box of nails doesn’t meet the need.
I’m not disparaging OSS — it just isn’t a good fit for use cases like this when you need to deal with bullshit like FIPS 140-2.
No open source product will meet the requirement, because you often need FIPS validated crypto.