lstoll
Joined 16 years ago
Karma
350
Submissions
27
Member since
Mar 22
twitter/github/etc: lstoll
View on Hacker NewsRecent submissions
Comment · 4 years ago
We use an AWS KMS asymmetric key for the CA keys, they're cheap and avoids exposing the private key material in an any way.
For signing SSH certificates, we run a small service (prototype code dump at https://github.com/pardot/sshsigner) that uses this key to sign short lived certificates. Auth to the service is via OIDC issued ID tokens.
On the client side we have a custom SSH agent that uses an ephemeral in-memory private key. The agent manages the OIDC web flow and calling out to the service for signing on demand. This lets us keep the cert duration small and scoped, and allows us to force re-auth for sudo etc. via the web flow.
We also do a similar thing for host keys, IAM auth the instances and sign certificates.
Altogether works well, provides a nice user experience, and keeps long-lived/leakable creds out of out environment.
Comment · 5 years ago
I migrated from the EU to the US, but then realised that once everything was factored in (medical, car, housing, cost of living) the taxes were actually worth it, so I moved back to the EU.
Comment · 5 years ago
you don't have to predict that exact scenario to know that domestic semiconductor manufacturing is a good idea.
Comment · 5 years ago
This is fine while you're employed, but what if you lose your position or decide to take a couple years off? Then it becomes a different equation.
Spread out over time, in the places I lived outside of the US that was not really a concern. Same with most other "social care" situations. In the US, it all felt a lot more tenuous which was a source of constant low-key anxiety.
Comment · 6 years ago
Git also supports S/MIME, and GitHub provides a tool to sign commits with this directly https://github.blog/changelog/2018-09-10-smime-signature-ver...
Comment · 11 years ago
It used to use RubyEncoder, now it uses something custom. The overhead is very minimal, and it's only when the source is read off disk.
Comment · 11 years ago
We just keep all our go code in one repo.
Comment · 11 years ago
Heroku already does this pretty well, not sure what the benefit would be?
Comment · 13 years ago
There's already a `goenv` https://github.com/wfarr/goenv, that I've been using for a bit. Also can do go version management.