Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
Keys
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container registry
Model registry
Operate
Environments
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
tetras-libre
Keys
Commits
6276eca0
Commit
6276eca0
authored
1 year ago
by
Elian Loraux
Browse files
Options
Downloads
Patches
Plain Diff
add instruction to create your own key and import key of collaborators
parent
466c5d3f
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+19
-18
19 additions, 18 deletions
README.md
with
19 additions
and
18 deletions
README.md
+
19
−
18
View file @
6276eca0
SSH and GPG public keys for Tétras Libre collaborators
# List GPG key :
# GPG
gpg is use for pass
`gpg --list-keys`
## Creating gpg key
`gpg --generate-key`
follow diaglog
# Edit confidence a key :
`gpg --edit-key <keyName>`
# Change confidence :
`trust`
## Add key of Tétras Libre collaborators
To import gpg key, use
`gpg --import key.asc`
. To import all key, go on GPG folder and use
`gpg --import *`
After that, you need to edit confidence of key. For this, use
`gpg --edit-key <keyName>`
and use
`trust`
command in gpp (gpg>trust)
Answer the response to add the confidence
`5 - ultimate`
. Use
`quit`
to leave.
# Check manually if key is valid for pass
-
Clone pass repository
-
`gpg -d /path/to/key/in/pass/key.gpg.
# Pass
## Check manually if key is valid for pass
-
Clone 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 :
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
-
Use QTPass or cli to add concerned key
# Add new key on pass
#
# Add new key on pass
- Pull the repo
- Add the new public GPG in your gpg
`
gpg --import publickey.asc
`
-
Check if Pass(QTPass) is set to encrypt passwords with the new key in addition of the existing
-
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
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment