On 29/04/14 01:17, MFPA wrote:
I have a key on the servers for just over four years now with a valid
address that has been used for no other purpose and has not received a
single email. OK, not a statistically valid experiment but I'm sure
plenty of others have done similar.
I have a key on
Am Di 29.04.2014, 10:51:35 schrieb Peter Lebbing:
But it hardly ever happens. 22 attempted scams in 3 years, and they
arrive in batches. 7 batches to be precise; 7 distinct moments in
time that scams arrived on that address.
That is interesting but if it is supposed to be an answer then I
On 29/04/14 11:13, Hauke Laging wrote:
if it is supposed to be an answer then I guess from the perspective of the
average user it answers the wrong question.
It wasn't. It was an elaboration on one particular aspect of the answer MFPA
gave.
Will uploading my certificate to a public key
Hi,
Some keys stored on the public key servers have User IDs which seem to
be encoded with a different encoding than UTF-8.
For example the key with key ID 0xA8364AC589C44886 shows an invalid
character when viewed online:
http://pgp.mit.edu/pks/lookup?search=0xA8364AC589C44886
gpg is able to
On Tue, 29 Apr 2014 11:11, martijn.l...@gmail.com said:
Some keys stored on the public key servers have User IDs which seem to
be encoded with a different encoding than UTF-8.
Right. Old PGP versions didn't care about the requirement for utf-8 and
used whatever the terminal was configured to
Eh, I consider the possibility of address harvesting an opportunity
for a bit of sport. I enjoy occasionally crafting a new regular
expression to make maildrop automatically toss a new strain of UCE.
--
Mark H. Wood, Lead System Programmer mw...@iupui.edu
Machines should not be friendly.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi
On Tuesday 29 April 2014 at 3:23:10 PM, in
mid:20140429142310.ge14...@iupui.edu, Mark H. Wood wrote:
Eh, I consider the possibility of address harvesting an
opportunity for a bit of sport. I enjoy occasionally
crafting a new regular
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi
On Tuesday 29 April 2014 at 10:59:21 AM, in
mid:535f77f9.8070...@digitalbrains.com, Peter Lebbing wrote:
The problem with keeping an e-mail address secret is
you need to keep it secret all of the time, while it
only needs to leak to
I don't know how much of a spam problem there is by having keyservers harvested
for their e-mail addresses,
but if indeed it does become a problem, then maybe at that point, the e-mail
addresses should not be listed on the keyserver.
When a person generates a new key, the e-mail required by
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi
On Tuesday 29 April 2014 at 7:18:40 PM, in
mid:20140429181840.457e7a0...@smtp.hushmail.com, ved...@nym.hush.com
wrote:
When a person generates a new key, the e-mail required
by gnupg for key generation, can be listed as something
benign
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi
On Monday 28 April 2014 at 8:22:44 PM, in
mid:535eaa84.9010...@digitalbrains.com, Peter Lebbing wrote:
- trust-model direct (and then set validity with
trust command) - trust: ultimate (note: don't do
this!)
But unless I am missing
Am Di 29.04.2014, 20:22:52 schrieb MFPA:
validate a key without removing validity from
all the keys on the keyring that are validated by signatures.
I don't understand that.
Hauke
--
Crypto für alle: http://www.openpgp-schulungen.de/fuer/unterstuetzer/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi
On Tuesday 29 April 2014 at 8:34:27 PM, in
mid:1495086.yRroNSC0aI@inno, Hauke Laging wrote:
Am Di 29.04.2014, 20:22:52 schrieb MFPA:
But unless I am missing something, trust: ultimate
is the only way the trust command can validate a key
Hi,
I use '--keyserver srv --search-keys key' to get info on a number of
keys. As far as I can tell, that doesn't return an expiration date (if
that exists).
Are there other ways to easily check on the exp. date, besides importing
the key and then verifying the expiration date?
thanks,
koen
14 matches
Mail list logo
