Hello Peter and thank you very much!
> On 18/01/17 13:06, Stefan Boehringer wrote:
>> The error is as follows:
>>
gpg: Auf geht's - Botschaft eintippen ...
test
gpg: Keine gültigen OpenPGP-Daten gefunden.
gpg: processing message failed: Unbekannter Systemfehler
>
> What was t
On 18/01/17 15:39, Damien Goutte-Gattat wrote:
>
> I believe there's a bug in the handling of the regular expression
> associated with a trust signature. I've just submitted a patch to fix it
> [1]. With that patch applied, I get the expected result for step 10
> (Blake's key is fully valid, not
Hi,
On 01/18/2017 03:51 PM, John Lane wrote:
I think things look ok up to step 9 and point (a) and (b) appear to work
as I expect but (c) doesn't. I'd really appreciate some feedback about
what is happening in:
step 10 (trust level 1 restricted to example.org)
step 14 (trust level 2 restricted t
On 18/01/17 00:21, NIIBE Yutaka wrote:
> This is just a lucky coincidence, but I'm glad to see the development of
> GnuPG goes well.
Ah, two birds with one stone! Thank you for working on multi-card-reader
setups!
> Thank you for your support of GnuPG. Your support encourages me
> (hopefully, al
On 18/01/17 13:06, Stefan Boehringer wrote:
> The error is as follows:
>
>>> gpg: Auf geht's - Botschaft eintippen ...
>>> test
>>> gpg: Keine gültigen OpenPGP-Daten gefunden.
>>> gpg: processing message failed: Unbekannter Systemfehler
What was the command line you used to invoke gpg? It looks l
On 18/01/17 03:03, David Shaw wrote:
>
> Can you post the actual user IDs of the keys you are testing with (or a
> similar example.com set) so I can try them as well?
Hi David,
I have written a test shell script to experiment with trust signatures.
The script is at https://git.io/vMXMQ
There
On 170118-22:59+1030, Lachlan Gunn wrote:
> Le 2017-01-18 à 22:48, Miroslav Rovis a écrit :
> > On 170115-22:17+0100, Juan Miguel Navarro Martínez wrote:
> > ...
> >> Lastly, revoke the old one if you aren't going to use it publicly anymore.
> > Isn't is wrong to revoke a key which you don't consid
Damien Goutte-Gattat writes:
>> I don't know why so much is stated as "unbekannt = unknown"...
>
> It looks like you didn't save and restore your trust database when you
> deleted your .gnupg folder (it's a file called trustdb.gpg). As a
> result, GnuPG does not know what level of ownertrust shou
On 01/18/2017 01:06 PM, Stefan Boehringer wrote:
I don't know why so much is stated as "unbekannt = unknown"...
It looks like you didn't save and restore your trust database when you
deleted your .gnupg folder (it's a file called trustdb.gpg). As a
result, GnuPG does not know what level of ow
Hello there.
I'm quite new to GnuPG. In November I played around with it and
generated my first key.
In the meantime I started to read more about it and decided to start
anew, generating a masterkey under more secure conditions (I used
Tails), keeping it offline afterwards and generated signing a
Le 2017-01-18 à 22:48, Miroslav Rovis a écrit :
> On 170115-22:17+0100, Juan Miguel Navarro Martínez wrote:
> ...
>> Lastly, revoke the old one if you aren't going to use it publicly anymore.
> Isn't is wrong to revoke a key which you don't consider was compromised?
> If you don't want to use it, i
On 170115-22:17+0100, Juan Miguel Navarro Martínez wrote:
...
> Lastly, revoke the old one if you aren't going to use it publicly anymore.
Isn't is wrong to revoke a key which you don't consider was compromised?
If you don't want to use it, it suffices that it is expired, or?
--
Miroslav Rovis
Za
On Sun, 15 Jan 2017 22:09, fa...@ariis.it said:
> gpg --edit-key
Since 2.1.17 you can also do this without using the menu:
gpg --quick-set-expire YOUR_FINGERPRINT EXPIRE_DATE
EXPIRE_DATE can have the usual formats for example "2018-11-30"
Shalom-Salam,
Werner
--
Die Gedanken sin
13 matches
Mail list logo
