If you have one backed by a HSM (Hardware Security Module) then you could be in a good spot. Similar set up to what AWS KMS does.

https://aws.amazon.com/kms/details/

Could this mean that Flock will be making a return?

https://signal.org/blog/flock/

My only regret is that when we started our current project, I did not commit 100% to gRPC, so now we have a mix of services. If I had of gone all in, it would be easier to integrate upcoming things like conduit [1], and I would not have to generate Swagger files but could just ship the proto files.

[1] https://conduit.io/

I believe conduit is going to support HTTP1.1 by the time it's done.

The http2 and grpc focus was just to get the alpha release out there.

It does work, very well. We have been using it for over a year without issue. It is not ideal, but it is good to have an option for when clients dont support gRPC.

That does not do empty folders, sadly.

In my old firm we managed to get ceph running on coreos using ceph in docker. The storage was exposed using a s3 gateway.

https://github.com/ceph/ceph-docker

Docker supports native RBD since version 1.8. Which should be both faster and more reliable than using the S3 gateway (though that has other benefits and becoming pretty good too).

iTunes?

On iTunes you can buy movies. As in, to watch multiple times whenever you want. For instance, for NZ$18.99 I can buy Me, Earl and the Dying Girl.

That's ludicrously expensive if you just want to watch it once.

The point is that any salt, even a hard coded salt, would mean that an attacker would need to regenerate the rainbow tables using the known salt.

Very interesting. Thanks for posting this. I have been using TigerTonic, but will give Gin a go after reading this.

I hope to not disappoint you, or us as a matter of fact :) hit us up on @hellodebug we will be building this open sourced.