[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gnupg-devel
Subject:    Re: WKD: returns only one pubkey (and why)
From:       Dashamir Hoxha via Gnupg-devel <gnupg-devel () gnupg ! org>
Date:       2022-12-12 13:01:28
Message-ID: CAMucfLwva9TYPbYszFayyiY=mfo-7xFMZDKXTd1DX0_HNtv++g () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


On Mon, Dec 12, 2022 at 11:48 AM Bernhard Reiter <bernhard@intevation.de>
wrote:

>
> In this email I respond to what WKD aims for:
>
> The design goal of WKD as it is (please see the question in my other
> email):
> Establish some minimal trust so that I can encrypt at the first message
> exchange, and hereby improve the usability of the end to end crypto
> functionality.


The way that I understand WKD (and how I explain it in my presentations) is
that it is a way to publish your public keys (share them with your
contacts). It is an alternative (and replacement) to the keyserver
infrastructure. It is preferred and recommended over the keyservers, since
those have some well-known problems. Also it is better than public key
exchange by email attachments, since you publish only once and it can be
discovered by the clients automatically.

Maybe your definition is the same as this one, but formulated differently.

On the other hand, if "being a replacement for keyservers" is not one of
the aims of WKD, I think that it should become. My opinion is that it *can*
be a replacement for keyservers.

Regards,
Dashamir

[Attachment #5 (text/html)]

<div dir="ltr"><div dir="ltr"><div class="gmail_default" \
style="font-family:arial,sans-serif;font-size:small"><span \
style="font-family:Arial,Helvetica,sans-serif">On Mon, Dec 12, 2022 at 11:48 AM \
Bernhard Reiter &lt;<a \
href="mailto:bernhard@intevation.de">bernhard@intevation.de</a>&gt; \
wrote:</span></div></div><div class="gmail_quote"><blockquote class="gmail_quote" \
style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"> <br>
In this email I respond to what WKD aims for:<br>
<br>
The design goal of WKD as it is (please see the question in my other email):<br>
Establish some minimal trust so that I can encrypt at the first message<br>
exchange, and hereby improve the usability of the end to end crypto<br>
functionality. </blockquote><div><br></div><div><div class="gmail_default" \
style="font-family:arial,sans-serif;font-size:small">The way that I understand WKD \
(and how I explain it in my presentations) is that it is a way to publish your public \
keys (share them with your contacts). It is an alternative (and replacement) to the \
keyserver infrastructure. It is preferred and recommended over the keyservers, since \
those have some well-known problems. Also it is better than public key exchange by \
email attachments,  since you publish only once and it can be discovered  by the \
clients automatically.</div><div class="gmail_default" \
style="font-family:arial,sans-serif;font-size:small"><br></div><div \
class="gmail_default" style="font-family:arial,sans-serif;font-size:small">Maybe your \
definition is the same as this one, but formulated differently.</div><div \
class="gmail_default" \
style="font-family:arial,sans-serif;font-size:small"><br></div><div \
class="gmail_default" style="font-family:arial,sans-serif;font-size:small">On the  \
other hand, if &quot;being a replacement for keyservers&quot; is not one of the aims \
of WKD, I think that it should become. My opinion is that it *can* be a replacement \
for keyservers.</div></div><div><br></div><div><div class="gmail_default" \
style="font-family:arial,sans-serif;font-size:small">Regards,</div><div \
class="gmail_default" \
style="font-family:arial,sans-serif;font-size:small">Dashamir</div><br></div></div></div>




_______________________________________________
Gnupg-devel mailing list
Gnupg-devel@gnupg.org
https://lists.gnupg.org/mailman/listinfo/gnupg-devel


[prev in list] [next in list] [prev in thread] [next in thread]