Viewing profile — linuxhackerman

This is indeed a useful approach to limiting the scope of environment variables, and I try to use that rather than exporting when possible. Using files (especially "special" files …

As pointed out by evgpbfhnr, I do avoid using environment variables and justify it (though with different reasoning than yours). Your justification is the kind of thing I mention a…

Process substitution (the ` What you've hinted at and what I didn't mention in the post is that this is indeed a good way to avoid even having the secret ever be a shell variable. …

I touch on this possibility with the `rbw` example: >`$ token=$(rbw get gitlab-access-token) # get the token from a command-line password manager`

It's definitely a powerful approach; I don't think it's particularly viable for the sort of use cases where you're throwing secrets around in a shell: - It's not supported natively…

As I mention in the post: >One way to avoid this is to prevent the command from being written to history. Bash has a configuration variable named HISTCONTROL, which when set to inc…

"reproducible" means you get the same result, bit-for-bit, when running a build in different circumstances. It's trivial to write non-reproducible Nix derivations by placing timest…

I've been planning to implement NixOS tests based on virtiofs instead of 9p for a while, but haven't got it working yet (at the time I tried, the available uid mapping strategies d…

Great job, me. I fixed it in the source but didn't deploy it to the site. Thanks for pointing it out!

It doesn't actually go through a "real network" at all, the VM speaks 9p to the host via a virtio pipe (not sure what the technically correct term for this is) so there's none of t…