-
Notifications
You must be signed in to change notification settings - Fork 22
Home
szszszsz edited this page Mar 24, 2017
·
2 revisions
If you think you have spotted an issue please report it here, including device's model, version, operating system family with version and GPG2 version (if related).
If you are unable to generate keys under GPG2 or some other action is not working properly it is possible some bug was introduced lately. It would be best to create a log file. Please follow these steps to do so:
- !!! Set your admin and user PINs to default !!! to not disclose your original PINs.
- Copy scdaemon.conf.txt to
~/.gnupg/scdaemon.conf
and correct the absolute path there to match own user home directory. If any config is already there please backup it and swap with this one. - Kill old
scdaemon
withpkill scdaemon
. - Do not-working scenario - generate 4096 keys as usual .
- Run step 2 again so the log file will not be appended with unneeded information by running
scdaemon
in the background. - Undo changes from step 1 - rename/delete or swap
scdaemon.conf
with the backup, so log files will not be generated during day-to-day use. - Attach the log file
scdaemon.log
here in a comment as a file.
The log file will be sent further to GPG team.