From 36c3030ca9ad9223361d3a175d33f86b12124114 Mon Sep 17 00:00:00 2001 From: Elian Loraux <elian.loraux@tetras-libre.fr> Date: Wed, 4 Sep 2024 12:13:56 +0200 Subject: [PATCH] remove pass instruction --- README.md | 19 +------------------ 1 file changed, 1 insertion(+), 18 deletions(-) diff --git a/README.md b/README.md index 94e3bb4..1116cbd 100644 --- a/README.md +++ b/README.md @@ -15,7 +15,7 @@ From the [Arch Linux wiki page](https://wiki.archlinux.org/title/SSH_keys#Genera ```sh -C "$(whoami)@$(uname -n)-$(date -I)" ``` -> will add a comment saying which user created the key on which machine and when (like `user@machine-2023-08-14`) +> will add a comment saying which user created the key on which machine and when (like `user@machine-2023-08-14`) ## Adding key to the repo Simply copy your key from `~/.ssh/` to the repo's `SSH` folder. @@ -47,20 +47,3 @@ Then export it gpg --export --armor --output '<your.email@tetras-libre.fr_pub.asc' <key id> ``` Finally copy the `.asc` key file to the GPG folder (if it's not already there) - - -# Pass -## Check manually if key is valid for pass - -- Clone [pass](https://gitlab.tetras-libre.fr/tetras-libre-admin/pass) repository -- `gpg -d /path/to/key/in/pass/key.gpg.` - -If the result is "No secret key", check in the pass repository if everything is ok : -- Last version of the repo (in case of force push) -- Use QTPass or cli to add concerned key - -## Add new key to pass - -- Pull the repo -- Add the new public GPG in your gpg -- Check if Pass(QTPass) is set to encrypt passwords with the new key in addition of the existing -- GitLab