On Thu, 17 Sep 2020 11:27, Alan Bram said:
> configuration, there was an already-running agent that I had to kill first
> in order to get it to reread the config.
Just for the reecords:
gpgconf --reload gpg-agent
would have been sufficent but "gpgconf --kill gpg-agent: works of course
also.
Alan Bram via Gnupg-users wrote:
> I have been using gnupg for a few years now, with no change in the way I
> invoke it. Recently (I guess my package manager updated to a new version:
> 2.2.23) it started injecting a warning about "insecure passphrase" and
> suggesting that I ought to include a d
On Thu, Sep 17, 2020 at 10:52 AM Alan Bram wrote:
> On Thu, Sep 17, 2020 at 8:56 AM Phil Pennock
> wrote:
>
>>
>> Set min-passphrase-nonalpha in ~/.gnupg/gpg-agent.conf -- the default is
>> 1, but I think that you can set it to 0.
>>
>
> I tried that, but it doesn't seem to have any effect.
>
D
On Thu, Sep 17, 2020 at 8:56 AM Phil Pennock
wrote:
>
> Set min-passphrase-nonalpha in ~/.gnupg/gpg-agent.conf -- the default is
> 1, but I think that you can set it to 0.
>
I tried that, but it doesn't seem to have any effect. Then, as an
experiment, I tried setting it to 2, and observed that i
On Wed, 16 Sep 2020 15:03, Alan Bram said:
> I have been using gnupg for a few years now, with no change in the way I
> invoke it. Recently (I guess my package manager updated to a new version:
> 2.2.23) it started injecting a warning about "insecure passphrase" and
> suggesting that I ought to inc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello Ryan,
Thursday, September 17, 2020, 4:42:24 PM, you wrote:
> -Ryan McGinnis
> http://www.bigstormpicture.com
> PGP Fingerprint: 5C73 8727 EE58 786A 777C 4F1D B5AA 3FA3 486E D7AD
BTW your public key is not on keys.openpgp.org
- --
Best regar
On 2020-09-16 at 15:03 -0700, Alan Bram via Gnupg-users wrote:
> I have been using gnupg for a few years now, with no change in the way I
> invoke it. Recently (I guess my package manager updated to a new version:
> 2.2.23) it started injecting a warning about "insecure passphrase" and
> suggesting
Stop. Unsubscribe
Sent from Yahoo Mail on Android
On Thu, Sep 17, 2020 at 10:40 AM, Stefan Claas wrote: Alan
Bram via Gnupg-users wrote:
> I have been using gnupg for a few years now, with no change in the way I
> invoke it. Recently (I guess my package manager updated to a new version:
Wonder if someone saw this email and uploaded it -- it shows up when I search!
:)
Best,
-Ryan McGinnis
http://www.bigstormpicture.com
PGP Fingerprint: 5C73 8727 EE58 786A 777C 4F1D B5AA 3FA3 486E D7AD
‐‐‐ Original Message ‐‐‐
On Thursday, September 17, 2020 10:25 AM, Martin wrote:
>
Alan Bram via Gnupg-users wrote:
> I have been using gnupg for a few years now, with no change in the way I
> invoke it. Recently (I guess my package manager updated to a new version:
> 2.2.23) it started injecting a warning about "insecure passphrase" and
> suggesting that I ought to include a d
(BTW -- not to be pedantic, but if by "a few" words you mean "three", then you
don't have a good passphrase -- six words is kinda minimum with diceware to get
a decent amount of entropy)
-Ryan McGinnis
http://www.bigstormpicture.com
PGP Fingerprint: 5C73 8727 EE58 786A 777C 4F1D B5AA 3FA3 486E D
I have been using gnupg for a few years now, with no change in the way I
invoke it. Recently (I guess my package manager updated to a new version:
2.2.23) it started injecting a warning about "insecure passphrase" and
suggesting that I ought to include a digit or special character.
I don't want to
12 matches
Mail list logo
