aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/README.md (follow)
Commit message (Collapse)AuthorAgeFilesLines
* add fish configbasbebe2021-01-101-0/+7
|
* Merge pull request #225 from ZenithalHourlyRate/gpg-agent-forwarddrduh2020-12-301-41/+139
|\ | | | | Add New Agent Forward Method and Clarify Two Methods
| * Rephrase one sentence according to one comment on drduh/YubiKey-Guide#225Zenithal2020-12-241-1/+1
| |
| * Add subsections on chained agent forwardingZenithal2020-12-241-4/+35
| |
| * Add note on chained agent forwardingZenithal2020-12-031-0/+4
| |
| * Correct WSL agent forwardingZenithal2020-12-031-4/+8
| | | | | | | | | | This is a mix of two forwarding method, this commit separates them
| * Change note in alter agent sectionZenithal2020-12-031-1/+2
| | | | | | | | Different methods have different requirements
| * Add new method for ssh-agent forwardingZenithal2020-12-031-4/+45
| |
| * Add details to GPG-Agent forward; Alter structureZenithal2020-12-031-56/+73
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* | Change format of important notes in mutt subsectionZenithal2020-12-021-1/+1
| |
* | Add Mutt subsection in Email sectionZenithal2020-12-021-0/+9
| |
* | Add Mutt in Email introZenithal2020-12-021-1/+1
|/
* Merge pull request #218 from DevSecNinja/devsecninja/addPowerShellCommanddrduh2020-11-211-3/+10
|\ | | | | Add PowerShell command to get YubiKey name
| * Change edit to create or editJean-Paul van Ravensberg2020-10-311-1/+1
| | | | | | As gpg-agent.conf didn't exist on my system
| * Add PowerShell command to get YubiKey nameJean-Paul van Ravensberg2020-10-311-2/+9
| |
* | Merge pull request #213 from linutsdc/fix-linksdrduh2020-11-211-2/+2
|\ \ | | | | | | Fix links with parentheses
| * | Fix links with parenthesesandy2020-09-171-2/+2
| |/
* | Merge pull request #211 from rgevaert/patch-1drduh2020-11-211-0/+2
|\ \ | | | | | | unset GNUPGHOME variable
| * | unset GNUPGHOME variableRudy Gevaert2020-09-011-0/+2
| |/ | | | | | | | | 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
* | Merge pull request #214 from anmull/debian-iso-versiondrduh2020-11-211-4/+4
|\ \ | | | | | | Changes command to download Debian ISO to use the value in the SHA512SUMS file
| * | Update verification of Debian ISO to not hardcode the version.Anthony Muller2020-09-251-2/+2
| | |
| * | Change Debian ISO url to be generated from the contents of SHA512SUM.Anthony Muller2020-09-251-2/+2
| |/ | | | | | | | | This removes the need to maintain the version number, which is currently out of date.
* | Fix reset commandNemo2020-11-141-1/+1
| | | | | | gpg-connect-agent uses `-r/--run` not `-R`
* | Merge branch 'master' into update-python-refsdragon7882020-09-021-3/+48
|\|
| * Merge branch 'master' of https://github.com/Amolith/YubiKey-Guide into ↵drduh2020-08-301-3/+35
| |\ | | | | | | | | | Amolith-master
| | * change defaults and add info to #Require touchAmolith2020-08-261-3/+35
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
| * | Add option to retrieve additionaly entropy from YubiKey itselfMirko Vogt2020-08-291-0/+13
| |/
* | Merge branch 'master' into update-python-refsdragon7882020-08-231-2/+39
|\|
| * Merge pull request #203 from bengim/bengim-patch-PyOpenSSLdrduh2020-08-221-0/+2
| |\ | | | | | | fixing wrong cryptography version
| | * Update README.mdbengim2020-08-221-0/+2
| | | | | | | | | fixing wrong cryptography version by explicitly installing PyOpenSSL
| * | Correct spellingStefano Figura2020-08-141-3/+3
| | |
| * | Update wording Stefano Figura2020-08-141-1/+3
| | | | | | | | | Ensure that is clear that we do not need to modify keys or even plug the yubikey
| * | Update notation sectionStefano Figura2020-08-131-1/+1
| | |
| * | Add notations sectionStefano Figura2020-08-131-0/+25
| |/
* / Python2 is EOL, update packages/references to Py3dragon7882020-08-211-3/+3
|/
* Fix usage inconsistencyb1f6c1c42020-08-111-5/+5
| | | | | Master key shall only be used to certify other keys. The usage indicator in README.md is inconsistently shown as SC and C.
* Set touch policy to fixed.Kenny MacDermid2020-05-271-3/+3
| | | | | | | | | 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.
* Add information on potential PIN issues and how to debug themSebastian Schmieschek2020-05-271-2/+5
| | | | | | | | | | 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.
* Stack rank secure environment and add a few tipsdrduh2020-05-251-19/+42
|
* Merge pull request #185 from vald-phoenix/fix-borken-anchordrduh2020-05-241-5/+5
|\ | | | | Fix broken anchor
| * Fix broken anchorVladyslav Krylasov2020-05-041-5/+5
| | | | | | | | There are two anchors with the same name and this breaks navigation.
* | Fix order of revocation command.Max Mäusezahl2020-05-241-1/+1
| | | | | | | | | | | | | | | | | | | | 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.
* | Include --expert when editing master keyMike Mazur2020-05-171-1/+1
|/ | | | This is specifically during setup when rotating keys.
* Clarified wordingJason Stelzer2020-05-041-1/+1
|
* GPG keys on multiple computersJason Stelzer2020-05-041-0/+1
| | | | I feel like this took me longer to figure out than it should have.
* Address throw-keyids issue with mailvelope to fix #178drduh2020-05-031-14/+18
|
* Split export pubkey from backup to fix #175drduh2020-05-031-86/+95
|
* Disambiguate backup volume label to fix #176.drduh2020-05-031-77/+127
|
* Merge pull request #180 from vald-phoenix/yubikey-reset-by-ykmandrduh2020-05-031-0/+6
|\ | | | | Describe ykman PGP keys reset
| * Describe ykman PGP keys resetVladyslav Krylasov2020-04-281-0/+6
| |
generated by cgit, for Dennis Eriksen