I see. I supposed if you are only using it to encrypt your own files and dont care about sharing them then it really doesn't matter.
On Wed, Jul 27, 2011 at 10:34 AM, Steve <steveb...@gulli.com> wrote: > The original poster explained it, that they wanted to use encryption only > locally (or inside a company or a closed system). > > That's fine, but the question of course remains: why not upload keys? No > damage is done. Maybe he'll writes back and elaborates on this? > > steve > > Am 27.07.2011 um 16:24 schrieb Wyllys Ingersoll: > > > Blocking publication of a public key? What exactly would be the point of > using public key encryption if you are not willing to share your public > key? > > > On Wed, Jul 27, 2011 at 10:21 AM, Bill Woodcock <wo...@pch.net> wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA256 >> >> >> On Jul 27, 2011, at 4:29 AM, Steve wrote: >> > that is currently not possible. But even if you only want to use >> encryption locally there's no damage when someone uploads his/her key to the >> key servers. You could of course block the IP of the key servers and >> exchange key locally. then the keys won't be uploaded, but I'm not sure why >> you want to prevent this form happening. >> >> I'm always stumped when people to go to extreme lengths to keep their >> public keys from being public… Is it because they're worried that the >> public key being exposed will lead to someone brute-forcing their private >> key eventually? >> >> -Bill >> >> >> >> >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG v1.4.11 (Darwin) >> >> iQIcBAEBCAAGBQJOMB7yAAoJEG+kcEsoi3+H5qIP/jlZC3FXmET8C9Q6GxfYffur >> 61MPCMG1OjMnIHoYVzj/AYswrZmv3idvkICXIRS38Ih96X7PBd8puLcRiP/KUs9/ >> 7sCUs3Wg/VcfY4nZX5pUj4cGFaOLgI2KY+n7HqAI25OojpFyq+lbns5WTKD7g0Ym >> Bt7GEt81l4zoj8KVWYAkZMDp48H8YZO8FdNqQ9EIBDRAhNpanlbz5aE5E4E+DSEi >> aSDaROU8yt7v8oOYLGW4aZqhapDWDkbPgN5gOy2Dgo9qtYEuh1Mjr6HMNsNyM6OL >> GAkhIi7phRjmQgysGsErUt9/BdZKNw/PVhuUhreQVdfW5uVv8hNhKfrp+bFoT0u0 >> oI1OOjyyFFqd0tTPXxnf3lSXfGVC23Jk+9fJSmFVrtLfb5oi8SR9bis2RQiKYJwF >> djQP7qPYtWT839DLk/tXPgMmo2JC0Q6+tIzpta1CuDEFgH63rS4efpmnbQYOHFNJ >> P410AV5GMDKOunWmQBEawD278cOLqkL+AsEttW1HFZK+u9m5zLuKbR2KNCDj6ds9 >> XW4qHbHOL+GFFrhrnVKUFMzp29mzWl3dljWbuM5HlfrSj/sqOfOK4fb9igt7A4hU >> TmfY+hRonlKDL28IphQoKitk+Rplck+yYzDUZo+f2rqezFWqmC/LgL3N/qXA94ng >> 3FCwmcdc8WUKIVPtkLpb >> =cjJ6 >> -----END PGP SIGNATURE----- >> >> _______________________________________________ >> gpgtools-users mailing list >> gpgtools-users@lists.gpgtools.org >> FAQ: http://www.gpgtools.org/faq.html >> Changes: http://lists.gpgtools.org/mailman/listinfo/gpgtools-users >> Unsubscribe: >> http://lists.gpgtools.org/mailman/options/gpgtools-users/wyl...@gmail.com?unsub=Unsubscribe&unsubconfirm=1 >> >> This email sent to: wyl...@gmail.com >> > > _______________________________________________ > gpgtools-users mailing list > gpgtools-users@lists.gpgtools.org > FAQ: http://www.gpgtools.org/faq.html > Changes: http://lists.gpgtools.org/mailman/listinfo/gpgtools-users > Unsubscribe: > http://lists.gpgtools.org/mailman/options/gpgtools-users/steveb...@gulli.com?unsub=Unsubscribe&unsubconfirm=1 > > This email sent to: steveb...@gulli.com > > > > _______________________________________________ > gpgtools-users mailing list > gpgtools-users@lists.gpgtools.org > FAQ: http://www.gpgtools.org/faq.html > Changes: http://lists.gpgtools.org/mailman/listinfo/gpgtools-users > Unsubscribe: > http://lists.gpgtools.org/mailman/options/gpgtools-users/wyl...@gmail.com?unsub=Unsubscribe&unsubconfirm=1 > > This email sent to: wyl...@gmail.com > >
_______________________________________________ gpgtools-users mailing list gpgtools-users@lists.gpgtools.org FAQ: http://www.gpgtools.org/faq.html Changes: http://lists.gpgtools.org/mailman/listinfo/gpgtools-users Unsubscribe: http://lists.gpgtools.org/mailman/options/gpgtools-users/arch...@mail-archive.com?unsub=Unsubscribe&unsubconfirm=1 This email sent to: arch...@mail-archive.com
