On 19.09.2019 12:31, Stefan Claas via Gnupg-users wrote:
> Binarus wrote:
>
>> IMHO, this system lacks a mandatory unique token in the key ID. The
>> natural choice for such a token would be the email address, because in
>> the first place it is the only thing you know for sure when writing a
>> p
Binarus wrote:
> IMHO, this system lacks a mandatory unique token in the key ID. The
> natural choice for such a token would be the email address, because in
> the first place it is the only thing you know for sure when writing a
> private message to somebody else who you haven't become acquainted
On 18.09.2019 17:30, Stefan Claas via Gnupg-users wrote:
> Binarus wrote:
>
>> You have stated that my real name must be in the key ID if I would like
>> to have the key certified by Governikus. Does the key ID need to have
>> other personal data in it? After all, as an example, there for sure
Binarus wrote:
> You have stated that my real name must be in the key ID if I would like
> to have the key certified by Governikus. Does the key ID need to have
> other personal data in it? After all, as an example, there for sure are
> at least 1000 people in Germany whose name is "Peter Meier" (
On 17.09.2019 21:58, Stefan Claas via Gnupg-users wrote:
> Binarus wrote:
>
>> Actually, I currently don't know anybody who I could ask to sign my
>> keys, and furthermore, the problem is bigger the other way around. Can I
>> trust the key which I found on the key server for the intended
>> reci
Binarus wrote:
> Actually, I currently don't know anybody who I could ask to sign my
> keys, and furthermore, the problem is bigger the other way around. Can I
> trust the key which I found on the key server for the intended
> recipient's email address? Can I at least be sure that the key server
>
On 17.09.2019 17:21, Werner Koch wrote:
> On Tue, 17 Sep 2019 15:08, gnupg-users@gnupg.org said:
>
>> See also dkg's thoughts on the matter on the openpgp-wg mailing list, to
>> align
>> the specification with reality:
>
> OpenPGP has never defined what goes into the User ID except for the
>
On Tue, 17 Sep 2019 17:35, look@my.amazin.horse said:
> convention or otherwise. The spec is factually wrong and misleading for
> implementors in this aspect, and should be updated to reflect reality.
The specs are not wrong if you would read them:
| the name and email address of the key holder
> Thus the current wording is sufficient and has served us well over the last 25
> years
If your statement here includes the "by convention contains an rfc2822
name-addr" part of the wording, please bring this opinion up on the openpgp-wg
thread.
The argument is being made (and I agree) that it
On Tue, 17 Sep 2019 15:08, gnupg-users@gnupg.org said:
> See also dkg's thoughts on the matter on the openpgp-wg mailing list, to align
> the specification with reality:
OpenPGP has never defined what goes into the User ID except for the
encoding which should be UTF-8. Anything else does not bel
On Tue, 17 Sep 2019 14:57, li...@binarus.de said:
> to use only key IDs consisting solely of the actual mail address
> hereafter (with or without the angle brackets - I can live with both
That is actually what I suggest for quite some time. The extra stuff is
not required and may lead only to co
On 17.09.2019 15:08, Vincent Breitmoser wrote:
>
>> but as far as I have understood my communication with Vincent, it's such IDs
>> which are a problem for keys.openpgp.org.
>
> Right, that's because we currently use an actual rfc2822 parser on
> keys.openpgp.org. This works fine for *most* us
> but as far as I have understood my communication with Vincent, it's such IDs
> which are a problem for keys.openpgp.org.
Right, that's because we currently use an actual rfc2822 parser on
keys.openpgp.org. This works fine for *most* users, but in the end causes more
trouble than it's worth, so
At first, thank you very much for your explanations!
On 17.09.2019 12:17, Werner Koch wrote:
> On Tue, 17 Sep 2019 09:12, li...@binarus.de said:
>
>> I am asking myself why Enigmail doesn't. I am not sure (and can't test
>> at the moment) how GnuPG would behave if given a problematic name when
>>
On Tue, 17 Sep 2019 09:12, li...@binarus.de said:
> I am asking myself why Enigmail doesn't. I am not sure (and can't test
> at the moment) how GnuPG would behave if given a problematic name when
> generating a key; I hope it would give a warning or would add the
gpg generates such a key just fin
On 16.09.2019 12:58, Claus Assmann wrote:
> On Mon, Sep 16, 2019, Binarus wrote:
>
>> Surname, Forename | Company
>
>> Commas are not allowed as part of email addresses. While I knew that, I
>
> unless quoted, e.g.,
> "Surname, Forename | Company"
Thanks, Claus, for the clarification / correc
On Mon, Sep 16, 2019, Binarus wrote:
> Surname, Forename | Company
> Commas are not allowed as part of email addresses. While I knew that, I
unless quoted, e.g.,
"Surname, Forename | Company"
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http:
On 14.09.2019 13:15, Binarus wrote:
> I have used the Thunderbird / Enigmail / Gpg4Win troika for quite a
> while without any issue. Yesterday, I had to reinstall, and while doing
> so, upgraded to the newest versions of that packages, and while I was at
> it, revoked my old (1024-bit) keys and gen
Dear Vincent,
On 14.09.2019 14:58, Vincent Breitmoser wrote:
>> I got confirmation emails for three of that four keys, but it seems that
>> the key server isn't in the mood to send a confirmation email for the
>> fourth. I have uploaded that one multiple times since then (again via
>> Enigmail's
Hi Binarus,
> I got confirmation emails for three of that four keys, but it seems that
> the key server isn't in the mood to send a confirmation email for the
> fourth. I have uploaded that one multiple times since then (again via
> Enigmail's key management), each time getting a success message
Dear all,
at first, thank you very much for providing privacy and safety for such
a long time free of charge to us!
Second, the following question could be slightly off-topic because it is
partly about the behavior of a key server which clearly is not part of
the GPG software. However, I think I
21 matches
Mail list logo
