Commit Graph

235 Commits (4370ba86ac93f450247b3c2090f0206454ef5b91)

Author SHA1 Message Date
berwag 4370ba86ac
Update README.md
changed wording according to yubischiess' comment
2021-01-28 11:19:53 +01:00
berwag ed85d93845
Additions to "Required Software"
proposed change according to Issue#215
2021-01-27 20:24:51 +01:00
basbebe a65cdca19a
add fish config 2021-01-10 20:01:55 +01:00
drduh 4544d41d4c
Merge pull request #225 from ZenithalHourlyRate/gpg-agent-forward
Add New Agent Forward Method and Clarify Two Methods
2020-12-30 09:14:23 -08:00
Zenithal 1eacf97835
Rephrase one sentence according to one comment on drduh/YubiKey-Guide#225 2020-12-24 21:08:41 +08:00
Zenithal a24fa8f373
Add subsections on chained agent forwarding 2020-12-24 21:01:44 +08:00
Zenithal 7e49f5cc89
Add note on chained agent forwarding 2020-12-03 01:18:21 +08:00
Zenithal 52727f1e04
Correct WSL agent forwarding
This is a mix of two forwarding method,
this commit separates them
2020-12-03 01:16:47 +08:00
Zenithal 6097e6762c
Change note in alter agent section
Different methods have different requirements
2020-12-03 01:01:36 +08:00
Zenithal 0d06d2ace8
Add new method for ssh-agent forwarding 2020-12-03 00:52:43 +08:00
Zenithal 54f9e8a3f9
Add details to GPG-Agent forward; Alter structure
GPG Agent forwarding has a broader usage, not only
limited to ssh-agent forwarding.

In this commit gpg-agent forwarding is raised as a
separate section as it can not be contained by #SSH
any longer.

More details are added for gpg-agent forwarding, including
some important notes taken from practice and analysis.

For ssh-agent forward, older method are contained, and new
method will be included as framework has been structured.
2020-12-03 00:13:15 +08:00
Zenithal 410a1d6ac2
Change format of important notes in mutt subsection 2020-12-02 23:23:34 +08:00
Zenithal 083aa53cf0
Add Mutt subsection in Email section 2020-12-02 22:59:30 +08:00
Zenithal 0ea32bb949
Add Mutt in Email intro 2020-12-02 22:35:56 +08:00
drduh fc6f9eb80d
Merge pull request #218 from DevSecNinja/devsecninja/addPowerShellCommand
Add PowerShell command to get YubiKey name
2020-11-21 10:59:23 -08:00
drduh 006ea19d04
Merge pull request #213 from linutsdc/fix-links
Fix links with parentheses
2020-11-21 10:48:00 -08:00
drduh 5c0bcd40a7
Merge pull request #211 from rgevaert/patch-1
unset GNUPGHOME variable
2020-11-21 10:45:59 -08:00
drduh f2aeed1b55
Merge pull request #214 from anmull/debian-iso-version
Changes command to download Debian ISO to use the value in the SHA512SUMS file
2020-11-21 10:45:40 -08:00
Nemo 7067ba6c38
Fix reset command
gpg-connect-agent uses `-r/--run` not `-R`
2020-11-14 09:24:19 +00:00
Jean-Paul van Ravensberg b1d3d279eb
Change edit to create or edit
As gpg-agent.conf didn't exist on my system
2020-10-31 11:29:35 +01:00
Jean-Paul van Ravensberg fd4b6f3eb4
Add PowerShell command to get YubiKey name 2020-10-31 11:15:51 +01:00
Anthony Muller 70dc01467b Update verification of Debian ISO to not hardcode the version. 2020-09-25 18:11:40 +00:00
Anthony Muller 967ca3cc52 Change Debian ISO url to be generated from the contents of SHA512SUM.
This removes the need to maintain the version number, which is currently
out of date.
2020-09-25 08:18:44 +00:00
andy f0e877fe5f Fix links with parentheses 2020-09-17 19:31:00 -04:00
dragon788 94a753d4a1
Merge branch 'master' into update-python-refs 2020-09-02 13:57:38 -05:00
Rudy Gevaert 547c1267bc
unset GNUPGHOME variable
if not done, in the next step you get error: 
gpg: keyblock resource '/home/..../gnupg-workspace/pubring.kbx': No such file or directory
gpg: no writable keyring found: Not found
2020-09-01 14:20:32 +02:00
drduh 03f0e40558 Merge branch 'master' of https://github.com/Amolith/YubiKey-Guide into Amolith-master 2020-08-30 14:19:41 -07:00
Mirko Vogt 767b84eb3b Add option to retrieve additionaly entropy from YubiKey itself 2020-08-29 16:24:34 +00:00
Amolith 0e7dabeeeb
change defaults and add info to #Require touch
As mentioned in #197, the previous behaviour would require users to
touch their key any time an authentication, signing, or encryption
operation was performed. In some situations, this behaviour would be
undesirable and the only way to revert it would be fully resetting the
key and starting from scratch. Rather than using `fixed`, this commit
simply turns the feature `on` so the user can change it later if they
wish.

Additionally, a note about the other policies was included so users can
decide for themselves which fits their situation better.
2020-08-26 23:42:53 -04:00
dragon788 9bb54914b4
Merge branch 'master' into update-python-refs 2020-08-23 13:20:03 -05:00
drduh 697a7d8fb9
Merge pull request #203 from bengim/bengim-patch-PyOpenSSL
fixing wrong cryptography version
2020-08-22 14:19:45 -07:00
bengim 2187610c1d
Update README.md
fixing wrong cryptography version by explicitly installing PyOpenSSL
2020-08-22 19:33:38 +04:00
dragon788 58b7c819d7
Python2 is EOL, update packages/references to Py3 2020-08-21 17:55:28 -05:00
Stefano Figura 8a95de3e3f
Correct spelling 2020-08-14 00:12:06 +02:00
Stefano Figura a2bc415f84
Update wording
Ensure that is clear that we do not need to modify keys or even plug the yubikey
2020-08-14 00:06:37 +02:00
Stefano Figura 8a08a8ac15
Update notation section 2020-08-13 23:51:42 +02:00
Stefano Figura c9ea04db2c
Add notations section 2020-08-13 23:45:18 +02:00
b1f6c1c4 f6f2c26e90
Fix usage inconsistency
Master key shall only be used to certify other keys. The usage indicator in
README.md is inconsistently shown as SC and C.
2020-08-11 02:17:08 -04:00
Kenny MacDermid 78164e8bfd
Set touch policy to fixed.
Setting the touch policy to `on` does not prevent the policy from
later being turned off again. Setting it to `fixed` is more secure
because it can not be turned off.

If someone wants to disable the touch policy they can always restore
the keys from the backups created in the guide.
2020-05-27 16:39:29 -03:00
Sebastian Schmieschek e1055025fe
Add information on potential PIN issues and how to debug them
I missed the error message when attempting to set a PIN of only 5 characters due
to the UI repeating the options below it.
Pinentry happily stores the bogus PIN and even counts down the retry counter
when entering the correct (default) one. This can be resolved by unblocking the
PIN.
Once I ran the gpg-agent with debug output (a tip found in the added link), the
issue was obvious.
2020-05-27 11:46:19 +01:00
drduh ccb8b0130a Stack rank secure environment and add a few tips 2020-05-25 12:49:07 -07:00
drduh 0bd52ed7d8
Merge pull request #185 from vald-phoenix/fix-borken-anchor
Fix broken anchor
2020-05-24 17:09:09 +00:00
Max Mäusezahl 1cf9656b33
Fix order of revocation command.
According to 'man gpg' the order of arguments should be

gpg [--homedir name] [--options file] [options] command [args]

In this case '--gen-revoke' is the command, '$KEYID' is an argument and
'--output $GNUPGHOME/revoke.asc' is an option. Previously this was
incorrect (option came first) and would spawn an error.
2020-05-24 17:53:56 +02:00
Mike Mazur de13c8dba6
Include --expert when editing master key
This is specifically during setup when rotating keys.
2020-05-17 21:00:03 +08:00
Vladyslav Krylasov 4c1d538c60 Fix broken anchor
There are two anchors with the same name and this breaks navigation.
2020-05-04 19:19:02 +01:00
Jason Stelzer aea317b527 Clarified wording 2020-05-04 08:28:23 -04:00
Jason Stelzer 07134a4e4f GPG keys on multiple computers
I feel like this took me longer to figure out than it should have.
2020-05-04 08:22:14 -04:00
drduh 93cbbd9d8b Address throw-keyids issue with mailvelope to fix #178 2020-05-03 14:18:29 -07:00
drduh 46d1d89115 Split export pubkey from backup to fix #175 2020-05-03 14:07:35 -07:00
drduh bf38b94a65 Disambiguate backup volume label to fix #176. 2020-05-03 13:45:58 -07:00