1.5 KiB
1.5 KiB
azos/pass
azos/pass
Password store conventions and path mappings for lauretta.
See root: azos
Format
The store was migrated (2026-07-25) from a nested path scheme to a flat layout.
Each entry is domain.com with the password on line 1 and login: on line 2:
<PASSWORD> login: user@example.com
Conventions
- All
passwordCommandfields in Nix/mbsync configs must pipe through| head -1to extract only the password line pass-git-helperhandles multi-line entries natively — nohead -1needed there- mbsync app passwords live under the
mbsync/namespace to keep them separate from account passwords
Path Mappings
| Service | pass path | Config location |
|---|---|---|
| Gmail mbsync | mbsync/anerisgreat@gmail.com |
features/mail/default.nix |
| BGU mbsync | mbsync/anerz@post.bgu.ac.il |
features/mail/default.nix |
| Zakobar mail (privateemail.com) | privateemail.com |
features/mail/default.nix |
| Nextcloud / caldav | zakobar.com |
features/lauretta/emacs/config.org |
| Git credentials (zakobar.com) | zakobar.com |
features/git-config/pass-git-mapping.ini |
Pending
mbsync/anerisgreat@gmail.comandmbsync/anerz@post.bgu.ac.ilentries not yet created in the store — mail sync will fail until these are added viapass insert