Re: pinetry and emacs
Phillip Susi writes: >> It was pinentry-curses. I tried switching to pinentry-tty and it rapes >> the tty even worse than the curses one. At least some keystrokes >> occasionally had some effect with the curses one. With This one nothing >> I hit would do anything. Couldn't get it to eventually think I entered >> a wrong password and give up, couldn't C-c, C-g, or C-z; I just had to >> use ~. to force ssh to hang up. Why and how is this program so abusive >> of the terminal? > > Weird... I ran strace on the program from another terminal and could see > that it was reading each keystroke, but continued to read after seeing > the \r. I hit C-j ( \n ) and it finally recognized the end of input. > I'm thinking that it requires that tty mode that appends a \n to a \r to > be enabled, but it doesn't bother enabling it when it takes over the > tty. I faced the same issue when I started Emacs from virtual terminal window. But I do not get the issue when launching from directly GUI. I am on MacOS. ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: export-filter question or bug
On Fri, 12 Feb 2021 11:44, Erich Eckner said: > $GPG --export --export-filter keep-uid="mbox = $mbox" $fpr gpg-wks-client does something similar but using "uid =" with a pre-checked UID in an import filter. It also uses import-options=import-export to process the keyblock without actually importing it. > $GPG --export --export-filter keep-uid="mbox = > buildmas...@archlinux32.org" 2E29129B8C684FE7A959C422714A1770ECE2DF62 > | gpg You should use | gpg --show-keys > pub rsa4096 2017-06-23 [SC] [expired: 2019-06-23] >2E29129B8C684FE7A959C422714A1770ECE2DF62 > uid buildmaster > sub rsa4096 2017-06-23 [S] [expired: 2021-12-31] > > (note the expired pub, thus the whole key is considered expired) Please try with --show-keys instead of using the default action. > This is not usable for wkd for me, because it contains all uids (of > course). I am curious why you don't use gpg-wks-client for example with the --install-key command. Salam-Shalom, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. signature.asc Description: PGP signature ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
export-filter question or bug
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, I'm using the following command to export keys for wkd: $GPG --export --export-filter keep-uid="mbox = $mbox" $fpr However, this creates funny results for the key for buildmas...@archlinux32.org which is downloadable here: https://archlinux32.org/keys.php?k=2E29129B8C684FE7A959C422714A1770ECE2DF62 Is my filtering wrong or is this some bug in gpg? To reproduce the issue, run: tmp_dir=$(mktemp -d) GPG='gpg --homedir '"$tmp_dir" curl 'https://archlinux32.org/keys.php?k=2E29129B8C684FE7A959C422714A1770ECE2DF62' | $GPG --import $GPG --export --export-filter keep-uid="mbox = buildmas...@archlinux32.org" 2E29129B8C684FE7A959C422714A1770ECE2DF62 | gpg this gives: pub rsa4096 2017-06-23 [SC] [expired: 2019-06-23] 2E29129B8C684FE7A959C422714A1770ECE2DF62 uid buildmaster sub rsa4096 2017-06-23 [S] [expired: 2021-12-31] (note the expired pub, thus the whole key is considered expired) However, skipping the --export-filter: $GPG --export 2E29129B8C684FE7A959C422714A1770ECE2DF62 | gpg gives the correct expiration: pub rsa4096 2017-06-23 [SC] [expires: 2021-12-31] 2E29129B8C684FE7A959C422714A1770ECE2DF62 uid buildmaster uid archlinux32 repository signing key sub rsa4096 2017-06-23 [S] [expires: 2021-12-31] This is not usable for wkd for me, because it contains all uids (of course). Thanks in advance, Erich -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE3p92iMrPBP64GmxZCu7JB1Xae1oFAmAmXBMACgkQCu7JB1Xa e1rL3Q/8Doo2VqaXgZgJAPw3xK0CvF8VQc8GLW4krEDTQH6Wu70e7nYGxFeJyLgt pqmloRZHDbGBfAh35qIfO1eQZgoe9eyVQyriJcqG/BrW5H9Qk20KGUHhHD1yjupZ +8WAQXzbmapiZz5COBkp1AQlOXgjKWMMTWMPt1DyaOaUKvw6LfpU78nML7wY6rF5 r7VX5jwrEDQmdyuPrumCotuZZpNOPgdAtURO9YHGh9sbOSsuIh4jvxWPyLOiFLRO M9wmyVhDt7sDQzoyzKew5LJGqsXaJ+SaAbQszNnS5NYMWeoeZk9nJGKgUosWFhwi RWe9ADVo9JTJcivGT/u/DGIlUtYhIdCO3z87sNvON6o4Uh9twAJk+okR/X7EYcRu ZcVWp/HFqwqBGDKtnxw8TCvLFEHPmnnklaXBwZW0k1TQw1HbmdQoe5vHsJJoIx0s CGMD2/5NxDWZtRPs/hJMnERgX7n15VJgMVDPSMSeGGQUIibrmEO3Pggyy2xNmVeo x0Bhobi+zsUKluC78Jv/GHkSc1jJa0ioXQIU2Kf2/zfm9148NFtE3bWOiz/sqC19 n+SItHRN/qs4J8obNNX2T9pXbnOXQ9wAmA5rYxG/3lKyq0rCKfXAXlOFSXksabDG PI10H2boPeMLu+HlnRtuAOq5an70flwuvXlDWg3Ux8NY3vJ4eu0= =dzM2 -END PGP SIGNATURE- ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
