HN user

HiHelloBolke

0 karma
Posts0
Comments9
View on HN
No posts found.

IMHO better write automation as much possible to rotate passwords firsts. Then remove ability for humans to set passwords (if possible). Your automations should store it vault (for machines) or write to 1Password directly (for humans).

Thank you for this, I just used this to create a rust based cli tool to create j2 yamls. This was motivated because we want to not use ansible j2 yaml generation instead to a standalone binary for it.

Now it feel like helm but it’s j2 and outputs a directory of yamls with base and overlays in kustomization way. So they can be iverriden in gitops by sre if needed

Moreover it's interesting to see how Apple is marketing durability with new iPhones... some of this is a byproduct of their environment strategy, i.e to reuse parts and thus generate less waste and perhaps is economically sound in the long run. But as a consumer, when you are spending that much money, you are going to decide on durability rather than how environmentally friendly it is - although for apple both mean same thing.

When the market is already saturated with smartphones, the new features and technology in each new release have become incremental. Also it's easier to do much more with the software.

Adding more hardware in a already complex, miniaturized device is difficult and may take more than the 2 year cycle...

One way we reduce the risk of CA key compromise is to intermediaries for signing most of our stuff. Our implementation has Vault that's using intermediates certs to sign user's ssh keys, these ssh cert are short lived and we use it for signing in to ephemeral app hosts.

One day we had bit of time skew because of bad ntpd & lo we couldn't login because of our short lived certs :-)