lstoll

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.

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.

you don't have to predict that exact scenario to know that domestic semiconductor manufacturing is a good idea.

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.

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...

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.

We just keep all our go code in one repo.

Heroku already does this pretty well, not sure what the benefit would be?

There's already a `goenv` https://github.com/wfarr/goenv, that I've been using for a bit. Also can do go version management.

There is, it's just not officially supported: https://github.com/heroku/heroku-buildpack-php . Github lists it as having 82 forks, so people are definitely playing around with this.

I'd rather see a benchmark of a more real-world case. These hello world microbenchmarks don't show anything.

I think if a new 'leader' in version control systems starts to make ground, github could easily adapt and support it. The github magic isn't just git, it's the network and collaboration tooling around your code.

It is however possibly the only obviously 'Java' experience that most non-techinal people have had.

If you're trying to prove to them that Java is everywhere, this is what's going to make them think "Oh yeah, it's on my computer too"

How is it flawed? According to the original report IE's handling is correct, it's the spec that's flawed.

Seems to work fine: http://smooth-stream-686.herokuapp.com/

(code at https://github.com/lstoll/heroku-playframework-scala , basically a simple hello world app)

I put 8GB in my 5,1 (Late 2008 Unibody 13") a few months ago, and it worked great. It's running 10.6 with the default 32bit kernel and was definitely using the full 8GB, so something has definitely changed at some point. For the record, I got the 8GB from OWC.

So, what makes that array so fancy? I mean, it's name is fancy, but that is about it. Is that really enough for it to deserve that name?