Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
Wiki Replica
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
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
The Tor Project
TPA
Wiki Replica
Commits
8d7a0ac4
Verified
Commit
8d7a0ac4
authored
1 year ago
by
anarcat
Browse files
Options
Downloads
Plain Diff
Merge remote-tracking branch 'wiki/master'
parents
4ff73083
c4207d84
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
howto/yubikey.md
+9
-6
9 additions, 6 deletions
howto/yubikey.md
with
9 additions
and
6 deletions
howto/yubikey.md
+
9
−
6
View file @
8d7a0ac4
...
...
@@ -441,7 +441,8 @@ first PIN:
This will prompt you for the current PIN. The factory default is
`123456`
(yes, just like the combination on someone's luggage).
Also set the Admin PIN in that way:
You will want to also set the Admin PIN, but the default is slightly different
from the previous one, it is
`12345678`
:
gpg/card> passwd
gpg: OpenPGP card no. [REDACTED] detected
...
...
@@ -770,18 +771,21 @@ from the backups.
gpg --import $BACKUP_DIR/public.key
3.
confirm GnuPG can see
the
secret keys:
3.
confirm GnuPG can
not
see
any
secret keys:
gpg --list-secret-keys
you should not see any `Card serial no.`, `sec>`, or `ssb>` in
there. If so, it might be because GnuPG got confused and still
thinks the old key is plugged in.
you should not see any result from this command.
4.
then, crucial step, restore the private key and subkeys:
gpg --decrypt $BACKUP_DIR/gnupg-backup.tar.pgp | tar -x -f - --to-stdout | gpg --import
5.
confirm GnuPG can see the secret keys:
you should not see any
`Card serial no.`
,
`sec>`
, or
`ssb>`
in
there. If so, it might be because GnuPG got confused and still
thinks the old key is plugged in.
5.
then go through the
`keytocard`
process again, which is basically:
gpg --edit-key $FINGERPRINT
...
...
@@ -793,7 +797,6 @@ from the backups.
key 1
keytocard
key 2
key 1
keytocard
At this point the new key should be a good copy of the previous
...
...
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