Dear all,
I'd appreciate some advice. I recently returned back from a year abroad to my
trusted hardware, and it seems an upgrade of gpg in the meantime broke things.
Setup:
* OpenPGP card with S, E, A subkeys; using both gnupg and ssh with the card
* SPR532 USB card reader with pinpad
~/.bas
Am 16.03.2021 um 17:19 schrieb Mark McDonnell via Gnupg-users
:
> It would be great if users could configure the default as it feels dangerous
> to default to saving the passphrase.
That is possible by running the following command:
defaults write org.gpgtools.common UseKeychain -bool NO
On Tue, 16 Mar 2021 20:34, Klaus Ethgen said:
> I believe, it is the "no-allow-external-cache" option.
Right, but I am not sure about the macOS pinentry; in particular if it
is closely based on the standard pinentry code base or does its own
thing. Any pointer to that pinentry?
Salam-Shalom,
>
> Probably the easiest way to avoid this is to seed the cache of gpg-agent with
> the needed passphrases before starting the concurrent invocations. See
> man gpg-preset-passphrase
> for details.
>
I just tried that to see if it would help. It doesn't make any
difference because the passphr
Hi,
Am Di den 16. Mär 2021 um 17:19 schrieb Mark McDonnell via Gnupg-users:
> It would be great if users could configure the default as it feels
> dangerous to default to saving the passphrase.
I believe, it is the "no-allow-external-cache" option.
I had the same on linux with the shity gnome PW
On Dienstag, 16. März 2021 12:19:17 CET John Lane wrote:
> Hello, I have a scenario where gpg is prompting for a passphrase when I
> don't think it should because it is cached in the agent. It seems to be
> triggered by concurrent use. Here is an example.
[snip]
> $ for n in {1..10}; do ( gpg --dec
Ah, ok cool think I found it.
Thanks bex.
It would be great if users could configure the default as it feels
dangerous to default to saving the passphrase.
On Tue, Mar 16, 2021 at 11:41 AM wrote:
> Hi,
>
> The key is listed in the login keychain. It uses the name and one of the
> associated n
Hello, I have a scenario where gpg is prompting for a passphrase when I
don't think it should because it is cached in the agent. It seems to be
triggered by concurrent use. Here is an example.
First, create some encrypted data:
$ echo test | gpg --encrypt -o test.gpg -r
Then decrypt it a number
Hi,
The key is listed in the login keychain. It uses the name and one of the
associated numbers - It is the fifth element in —with-key-data but I don’t
recognize it.
This default for pin entry is … frustrating.
Regards,
bex
On Mar 16, 2021, 12:05 PM +0100, Mark McDonnell via Gnupg-users
, w
Hi,
The default behaviour of the pinentry app (on macOS at least) is to have
the option "save password in Keychain" automatically selected.
I have to deselect this every time I use a specific GPG key where I don't
want the password saved in the macOS Keychain. Unfortunately it seems I
neglected t
Andrew, Jürgen,
Am Freitag 12 März 2021 17:27:08 schrieb Andrew Gallagher via Gnupg-users:
> PGPro is open source, but neither it nor iPGMail handle openPGP/MIME -
> Canary Mail
Am Freitag 12 März 2021 18:15:18 schrieb Juergen Bruckner via Gnupg-users:
> I can also name following Android Apps he
11 matches
Mail list logo
