On Thursday, 1 January 2015, Robert J. Hansen wrote:
> > I’ve discussed this attack vector on the keyserver mailing list. The
> general consensus is that the attack that I’m concerned about is real, and
> would result in serious disruption to the global keyserver network for an
> extended period
Hi
Sorry if I misunderstood, but I didn’t say that the photo ID should
be allowed to be as large as possible, and this is not allowed anyway
by, for example, apps like GPG Keychain.
But I was wondering … instead of attaching a photo to a public key,
why not attach a hash of the photo using an ima
On 01-01-2015 14:33, Sandeep Murthy wrote:
> Sorry if I misunderstood, but I didn’t say that the photo ID should
> be allowed to be as large as possible, and this is not allowed anyway
> by, for example, apps like GPG Keychain.
Huge size would not be the only problem. Wait until the first person
Hi guys,
I've updated my GnuPG key and send to keyservers.
What I updated ?
I've just deleted 2 expired subkeys and added one with a longer (in
2015) expiration.
But as I can see in a keyserver -
http://pgpkey.org/pks/lookup?op=vindex&search=0x5935a6bfb301c1aa2218e0e57d58bae0dbeb2b6a&fingerprin
Hello
I am sorry if this is a little off-topic but I am not sure where to ask.
I use both, gpg and smime (the later either with gpgsm or with
thunderbird)
Recently the German news magazine «Der Spiegel» [1] published more of
the «Snowden files», which reveal that gpg is NSA safe[2].
Does anybody
On 01.01.2015, Uwe Brauer wrote:
> Recently the German news magazine «Der Spiegel» [1] published more of
> the «Snowden files», which reveal that gpg is NSA safe[2].
>
> Does anybody know whether smime has the same level of security? There
> are at least two possible weak spots.
Nobody really
Hi,
find below a plain text copy of a blurb i wrote today:
https://gnupg.org/blog/20150101-happy-gnu-year.html
if you like to comment, please group reply to this mail.
Salam-Shalom,
Werner
Happy gnu year
to everyone and a big *thank you* to all supporters of
Besides Mozilla Thunderbird (v31.3.0) en Enigmail (1.7.2) I installed
GpG4Win (2.2.3) in order to encrypt/sign emails.
Works like a charm (no pun intended).
The only problem I have is that, when I try to open the "Manage Smartcard"
option in Enigmail, I receive an error saying that the smartcard is
Ryan Sawhill wrote:
> I disagree with your subject, and propose that you google for a tutorial
> since the man page clearly didn't work for you.
The man page did work for me, and I was able to accomplish my goal.
> (As far as I can tell, you were trying to import someone's pubkey, in which
> case
Hi Werner,
Apologies, I'm an idiot. The option is still there.
Optional Features:
--disable-option-checking ignore unrecognized --enable/--with options
--disable-FEATURE do not include FEATURE (same as
--enable-FE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 01/01/2015 05:59 AM, Kelly Dean wrote:
> Ryan Sawhill wrote:
>> I disagree with your subject, and propose that you google for a
>> tutorial since the man page clearly didn't work for you.
>
> The man page did work for me, and I was able to accom
On Thursday 01 January 2015 04:59:37 Kelly Dean wrote:
> Getting the fingerprint should not require importing the key. Getting the
> fingerprint should not require writing to any file at all. It should only
> require reading.
I haven't tried with gpg 1.4, but with gpg 2.0.22 it's as easy as
# gpg
On Thursday 01 January 2015 19:19:58 Uwe Brauer wrote:
> Hello
>
> I am sorry if this is a little off-topic but I am not sure where to ask.
> I use both, gpg and smime (the later either with gpgsm or with
> thunderbird)
>
> Recently the German news magazine «Der Spiegel» [1] published more of
> t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Am 01.01.2015 um 18:10 schrieb Linux Debian:
(...)
> I've updated my GnuPG key and send to keyservers. What I updated ?
> I've just deleted 2 expired subkeys and added one with a longer
> (in 2015) expiration. But (...) those 2 expired subkeys stil
On 12/31/2014 08:59 PM, Kelly Dean wrote:
I thought my original message made clear that I was trying to get the
fingerprint. The point of my message was that GPG apparently requires pointless
circumlocution for this simple function.
No, your original message contained nothing but the output o
On 12/31/2014 06:40 PM, Robert J. Hansen wrote:
The protocol was secure: you just had to configure it correctly.
Yes, thank you for your tidy summary of "Security 101." :)
What I'm looking for is some sort of concrete information about "When
ssh is configured the NSA can break it." I've seen
> Sorry if I misunderstood, but I didn’t say that the photo ID should
> be allowed to be as large as possible, and this is not allowed anyway
> by, for example, apps like GPG Keychain.
It *is* allowed by the spec, and it’s the spec that’s the problem here.
> But I was wondering … instead of attac
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi
On Thursday 1 January 2015 at 9:55:18 PM, in
, Ingo Klöcker
wrote:
> I haven't tried with gpg 1.4, but with gpg 2.0.22 it's
> as easy as
> # gpg --with-fingerprint key.gpg
I just tested with GnuPG 1.4.18 and it worked.
- --
Best regards
> What I'm looking for is some sort of concrete information about "When ssh is
> configured the NSA can break it." I've seen quite a few sites make
> the claim that "zomg, ssh is broken!" but haven't yet seen any specifics.
First, my usual reminder: don’t focus on the three-letter Voldemort. T
19 matches
Mail list logo
