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
8143f55f
Commit
8143f55f
authored
1 year ago
by
Eliott Sammier
Browse files
Options
Downloads
Patches
Plain Diff
Update README.md: minor typos
parent
bae17dc5
No related branches found
No related tags found
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+7
-7
7 additions, 7 deletions
README.md
with
7 additions
and
7 deletions
README.md
+
7
−
7
View file @
8143f55f
SSH and GPG public keys for Tétras Libre collaborators
# GPG
gpg
is use for pass
GPG
is use
d
for
[
pass
](
https://gitlab.tetras-libre.fr/tetras-libre-admin/pass
)
## Creating gpg key
`gpg --generate-key`
follow dia
g
log
follow dialog
## Add key of Tétras Libre collaborators
To import gpg key, use
`gpg --import <key file>`
. To import all key, go o
n
GPG folder and use
`gpg --import *`
To import
a
gpg key, use
`gpg --import <key file>`
. To import all key
s
, go
t
o 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 gp
p
(gpg>trust)
After that, you need to edit confidence of
the
key. For this, use
`gpg --edit-key <keyName>`
and use
`trust`
command in gp
g
(
`
gpg>trust
`
)
Answer the response to add the confidence
`5 - ultimate`
. Use
`quit`
to leave.
# Pass
## Check manually if key is valid for pass
-
Clone pass repository
-
`gpg -d /path/to/key/in/pass/key.gpg.`
`
-
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 o
n
pass
## Add new key
t
o pass
-
Pull the repo
-
Add the new public GPG in your gpg
...
...
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