3 ms·
How is an encryption backend supposed to fix this? It’s not really clear to me how it could be even expected to do so, or what gives the impression that the go
by FiloSottile 5y ago
How is an encryption backend supposed to fix this?
It’s not really clear to me how it could be even expected to do so, or what gives the impression that the goal of a 650-lines bash script would be to scale “from 1 to enterprise”.
Still, asserting that only your problems are real world problems and worth solving is pretty reductive.
- emptysongglass 5y agoWith Mozilla's SOPS, one can simply swap out GPG or age for AWS KMS or Vault as its encryption backend as one matures. SOPS is more or less ideal but doesn't have the ecosystem built around it pass does (Password Store for Android just one example of easily using your pass secrets everywhere). So, yes, it is possible and we don't need yet another encryption backend that already does what the existing backend does just because it's "lighter/sexier". What we should be doing with GPG is building abstractions (Keybase) and contributing to modernization efforts like Sequoia. Age is disruptive without showing its value to that disruption.