infamousjoeg

SPIFFE/SPIRE could work for the identity layer. The risk engine concept is cool. Would love to see that applied to machine identities that are working "on-behalf-of" humans.

Exactly this. They just need to validate the JWT signature against a JSON Web Key Set (JWKS). There's no need to store the data.

Love this minimalist approach!

Yes, well, now I'll be slacking off at work due to it... so you'll continue to see that trend. Thanks for this!

I developed go-keyconfig after realizing that almost every CLI that I use on a daily basis that requires authentication of some kind drops the secrets in a local filesystem config file in plain-text. As one could imagine, this is ripe for an accidental git commit or easy reading from an attacker.

Every OS comes with a secrets manager of some kind... MacOS has OSX Keychain, Linux has GNOME Keyring, KWallet, and secret-service, even Windows has Credential Manager.

This module is designed to help developers creating apps or CLIs needing to store configuration values in config files a secure means of doing so. It supports All the secret managers mentioned above.

I would love to hear everyone's feedback and thoughts!

CyberArk already does this... it's called Vendor Privileged Access.

I found this game to only be fun to play in VR (I have the Oculus Quest 2). On PC, it's hard to use KBAM as hands as adamredwoods said.

R.I.P. Red Hat

Which sucks when it's 2am and you start blowing up a majority of shard holders phones to unseal it because it sealed itself causing a critical outage.

THIS! EVERYTHING THIS!