<div dir="ltr"><div>Works just as well :)</div><div><br></div><div>Eran<br></div></div><br><div class="gmail_quote"><div dir="ltr">On Mon, Jul 2, 2018 at 11:51 AM nusenu <<a href="mailto:nusenu-lists@riseup.net">nusenu-lists@riseup.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
Eran Sandler:<br>
> Nice. Perhaps nusenu can add that to the spec. The current spec has gpg<br>
> support and keybase user, but perhaps there is a case for specifying the<br>
> gpg server as well (like in Marco's case).<br>
<br>
<br>
Usually the key fingerprint is enough to find a key<br>
if it was uploaded to any major keyserver.<br>
<br>
I'm not sure about adding a keyserver field to the spec,<br>
instead of a keyserver field I would use a keyuri that<br>
points to the public key file on a https server directly.<br>
<br>
<br>
<br>
-- <br>
<a href="https://twitter.com/nusenu_" rel="noreferrer" target="_blank">https://twitter.com/nusenu_</a><br>
<a href="https://mastodon.social/@nusenu" rel="noreferrer" target="_blank">https://mastodon.social/@nusenu</a><br>
<br>
_______________________________________________<br>
tor-relays mailing list<br>
<a href="mailto:tor-relays@lists.torproject.org" target="_blank">tor-relays@lists.torproject.org</a><br>
<a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays" rel="noreferrer" target="_blank">https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays</a><br>
</blockquote></div>