-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Tuesday 30 May 2017 at 8:42:04 PM, in
, Michael
Englehorn wrote:-
> Also, it would be strange to only publish your key's
> "name only" UID to the
> keyserver, because then at a keysigning event I
> wouldn't know where to
> send your public key
On 2017-05-29 at 18:58 +, listo factor via Gnupg-users wrote:
> This I find surprising: if one does not want receiving
> encrypted messages from those that he does not have
> existing relationship with, why does he publish his
> public key on public keyservers?
(1) Who says they published it?
So you don't mind when telemarketers call you?A public listing is not permission to annoy.___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
"Michael A. Yetto" writes:
> On Tue, 30 May 2017 15:53:44 +
> listo factor via Gnupg-users writes, and having
> writ moves on:
>
>>On 05/29/2017 11:52 PM, Konstantin Gribov - gros...@gmail.com wrote:
>>> Primary reason to publish a key is to m
On Tue, 30 May 2017 15:53:44 +
listo factor via Gnupg-users writes, and having
writ moves on:
>On 05/29/2017 11:52 PM, Konstantin Gribov - gros...@gmail.com wrote:
>> Primary reason to publish a key is to make it available for
>> fetching. It isn't a permission for anyone to annoy a person
>>
On Tue, 30 May 2017 15:53:44 +
listo factor via Gnupg-users wrote:
Hello listo,
>a piece of information publicly available on the net
>and then depend on "netiquette" for that piece of
>information not be used in a manner the owner finds
To paraphrase what's been said by others (and you app
On 05/29/2017 11:52 PM, Konstantin Gribov - gros...@gmail.com wrote:
Primary reason to publish a key is to make it available for fetching. It
isn't a permission for anyone to annoy a person anyhow.
Keservers have every characteristic of a public directory.
What possible reason there could be f
Yes, they could. But publishing all subkeys is simpler than publishing some
of them. And key is usually generated with both sign and encryption subkey
as many guides, howtos etc guide people to.
To look at such test emails from the other point of view just imagine that
someone found your email on
On Mon, May 29, 2017 at 11:52:27PM +, Konstantin Gribov wrote:
>
> As an example, many open source devs are publishing their keys which they
> use for signing software releases but rarely for encrypted communication.
On the other hand, they could publish certificates without encrypting
subkey
Primary reason to publish a key is to make it available for fetching. It
isn't a permission for anyone to annoy a person anyhow.
As an example, many open source devs are publishing their keys which they
use for signing software releases but rarely for encrypted communication.
On Tue, May 30, 2017
> This I find surprising: if one does not want receiving
> encrypted messages from those that he does not have
> existing relationship with, why does he publish his
> public key on public keyservers?
All presence on the keyservers says is, "if you have something to send
me, you may send it securel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi
On Monday 29 May 2017 at 2:18:18 PM, in
, Marcus
Brinkmann via Gnupg-users wrote:-
> For people who want to communicate with other people
> rather than bots,
> there is also this:
> https://www.reddit.com/r/GPGpractice/
> https://www.reddit.c
For people who want to communicate with other people rather than bots,
there is also this:
https://www.reddit.com/r/GPGpractice/
https://www.reddit.com/r/publickeyexchange/
On 05/29/2017 01:00 PM, Duane Whitty wrote:
> Hi list,
>
> When I checked my email this morning I had an encrypted message
13 matches
Mail list logo
