Consider using gpg encryption #18
Comments
kergoth
added a commit
that referenced
this issue
Jan 16, 2024
Home Manager input changes:
• Updated input 'home-manager':
'github:nix-community/home-manager/e13aa9e287b3365473e5897e3667ea80a899cdfb' (2024-01-09)
→ 'github:nix-community/home-manager/37d6eeceee464adc03585404eebd68765b3c8615' (2024-01-16)
• Updated input 'nixpkgs':
'github:nixos/nixpkgs/317484b1ead87b9c1b8ac5261a8d2dd748a0492d' (2024-01-08)
→ 'github:NixOS/nixpkgs/9b19f5e77dd906cb52dade0b7bd280339d2a1f3d' (2024-01-13)
Home Manager packages changes:
<<< /nix/store/adzsk4a78z8m4nr5qbaanjpallq4lcmd-home-manager-generation
>>> /nix/store/rm2qnvwzhbxz901bg0ppfrqndxlh2py4-home-manager-generation
Version changes:
[U.] #1 aws-c-auth 0.7.0 -> 0.7.7
[U.] #2 aws-c-cal 0.6.0 -> 0.6.9
[U.] #3 aws-c-common 0.8.23 -> 0.9.10
[U.] #4 aws-c-event-stream 0.3.1 -> 0.3.2
[U.] #5 aws-c-http 0.7.11 -> 0.7.14
[U.] #6 aws-c-io 0.13.29 -> 0.13.36
[U.] #7 aws-c-mqtt 0.8.14 -> 0.9.10
[U.] #8 aws-c-s3 0.3.13 -> 0.4.0
[U.] #9 aws-crt-cpp 0.20.3 -> 0.24.7
[U.] #10 aws-sdk-cpp 1.11.118 -> 1.11.207
[U.] #11 bundler 2.4.22 -> 2.5.3
[U.] #12 cargo 1.74.0 -> 1.75.0
[U.] #13 docker-buildx 0.12.0 -> 0.12.1
[U.] #14 docker-compose 2.23.3 -> 2.24.0
[U.] #15 du-dust 0.8.6 -> 0.9.0
[U.] #16 eza 0.17.0, 0.17.0-man -> 0.17.1, 0.17.1-man
[U.] #17 gcc 12.3.0-lib, 12.3.0-libgcc -> 13.2.0-lib, 13.2.0-libgcc
[U.] #18 gh 2.40.1 -> 2.41.0
[U.] #19 git 2.42.0, 2.42.0-doc -> 2.43.0, 2.43.0-doc
[U.] #20 glib 2.78.1 -> 2.78.3
[U.] #21 iproute2 6.5.0 -> 6.6.0
[U.] #22 jira-cli-go 1.4.0 -> 1.5.0
[U*] #23 jq 1.7, 1.7-bin, 1.7-doc, 1.7-lib, 1.7-man -> 1.7.1, 1.7.1-bin, 1.7.1-doc, 1.7.1-lib, 1.7.1-man
[U.] #24 json-c 0.16 -> 0.17
[U.] #25 libbpf 1.2.2 -> 1.3.0
[U.] #26 libnl 3.7.0 -> 3.8.0
[U.] #27 libseccomp 2.5.4-lib -> 2.5.5-lib
[U.] #28 libxml2 2.11.5 -> 2.12.3-unstable-2023-12-14
[U.] #29 llvm 16.0.6, 16.0.6-dev, 16.0.6-lib -> 17.0.6, 17.0.6-dev, 17.0.6-lib
[U.] #30 pcsclite 1.9.5 -> 2.0.1
[C.] #31 python3 3.10.13, 3.10.13-env, 3.11.6, 3.11.6-env -> 3.10.13, 3.10.13-env, 3.11.7, 3.11.7-env
[U.] #32 python3.10-pip 23.2.1, 23.2.1-man -> 23.3.1, 23.3.1-man
[U.] #33 python3.11-msgpack 1.0.5 -> 1.0.7
[U.] #34 rustc 1.74.0 -> 1.75.0
[U.] #35 rustc-wrapper 1.74.0 -> 1.75.0
[U.] #36 s2n-tls 1.3.56 -> 1.4.1
[U.] #37 sqlite 3.43.2 -> 3.44.2
[U.] #38 tzdata 2023c -> 2023d
[U.] #39 util-linux 2.39.2-bin, 2.39.2-lib, 2.39.2-login, 2.39.2-mount, 2.39.2-swap -> 2.39.3-bin, 2.39.3-lib, 2.39.3-login, 2.39.3-mount, 2.39.3-swap
[U.] #40 util-linux-minimal 2.39.2-bin, 2.39.2-lib, 2.39.2-login, 2.39.2-mount, 2.39.2-swap -> 2.39.3-bin, 2.39.3-lib, 2.39.3-login, 2.39.3-mount, 2.39.3-swap
[U.] #41 xgcc 12.3.0-libgcc -> 13.2.0-libgcc
Added packages:
[A+] #1 nix-lib-nmd 0.5.0
Removed packages:
[R-] #1 source <none>
Closure size: 341 -> 341 (339 paths added, 339 paths removed, delta +0, disk usage +78.9MiB).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Not all systems I use allow access to 1password's servers, so using it for everything isn't ideal. Either it has to be explicitly bypassed on those systems, or I could use gpg encryption instead, optionally fetching the gpg keyring out of 1password if 1) no gpg agent is available and 2) the gnupg keys aren't yet present and 3) the 1password cli is usable here. Then on hosts without access to it, I could manually deploy the gpg keyring.
The text was updated successfully, but these errors were encountered: