On Thursday 21 May 2009 15:15:18 Raimar Sandner wrote:
> I believe (an I think others do too) it is good praxis to not sign new keys
> even if you have signed the old one and the new key is signed by the old
> one, without personally checking with the keyholder first. After all, the
Hello
On Thursday 21 May 2009 11:35:44 Allen Schultz wrote:
> For the reason of SHA1 issues in the news, I've recently set up
> a new OpenPGP key, and
> will be transitioning away from my old one.
> This message is signed by
> both keys to certify the
> transition.
I have not recieved signatures
On Wednesday 20 May 2009 19:53:47 Fayina Zaporozhets wrote:
> I did trust and signed the key before:
>
>
>
> C:\GNU\GnuPG>gpg --edit-key E3655B17
>
> gpg (GnuPG) 1.4.9; Copyright (C) 2008 Free Software Foundation, Inc.
>
> This is free software: you are free to change and redistribute it.
>
> Ther
On Sunday 10 May 2009 14:52:21 Tyler Spivey wrote:
> Hello. I'm trying to make any message I clearsign
> have a hash of SHA256.
> Here is what I've done so far:
> I've added "personal-digest-preferences SHA256" to the end of my gpg.conf
> file. According to the manpage, this should be enough; since
On Friday 08 May 2009 09:14:27 Raimar Sandner wrote:
> On Friday 08 May 2009 02:09:31 David Shaw wrote:
> > One fear that I've seen talked about for SHA-1 is that an attacker can
> > create a duplicate document such that if you signed document or key A,
> > they could
On Friday 08 May 2009 02:09:31 David Shaw wrote:
> One fear that I've seen talked about for SHA-1 is that an attacker can
> create a duplicate document such that if you signed document or key A,
> they could come up with a document or key B that your signature would
> equally apply to. That fear
On Thursday 07 May 2009 16:50:06 Joel C. Salomon wrote:
> Joel C. Salomon wrote:
> > I foolishly signed a key I had not verified well, and the signed version
> > is on a keyserver. How can I unsign it?
> >
> > I have tried the following (changing the key ID to 0xDEADBEEF):
>
>
>
> I tried the comm
On Monday 04 May 2009 04:56:24 David Shaw wrote:
> If you want a DSA2 key:
>
>gpg --enable-dsa2 --gen-key
>
> Select option 1, and enter 3072 for the DSA key size.
> If you want an RSA key:
>
> gpg --cert-digest-algo sha256 --gen-key
>
> Select option 5. Enter a RSA key size. The defau
On Saturday 02 May 2009 15:45:11 David Shaw wrote:
> On May 2, 2009, at 6:25 AM, Simon Ruderich wrote:
> > I would like to use a different hash than SHA-1. I tried setting
> > personal-digest-preferences SHA256 in my gpg.conf but it didn't
> > work. What hash can I use with my key (default DSA/Elga
On Saturday 02 May 2009 14:11:46 John W. Moore III wrote:
> Simon Ruderich wrote:
> > I would like to use a different hash than SHA-1. I tried setting
> > personal-digest-preferences SHA256 in my gpg.conf but it didn't
> > work. What hash can I use with my key (default DSA/Elgamel key)
> > and how?
> I have to use GnuPG in batch mode to enable a running process to decrypt
> encrypted file. If I run the shell script through ssh (with the specific
> user that was previously used to set the keys and has its proper .gnupg
> directory) this works fine despite the following warning: WARNING: messa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 29 April 2009 15:40:47 Peter Pentchev wrote:
> On Wed, Apr 29, 2009 at 03:31:51PM +0200, Raimar Sandner wrote:
> > On Wednesday 29 April 2009 12:09:02 Olivier Mehani wrote:
> > > Let me explain: having several backgroun
On Wednesday 29 April 2009 12:09:02 Olivier Mehani wrote:
> Let me explain: having several background-ish applications making use of
> the agent, it happens that the pinentry sometimes pops out when the
> passphrase cache has expired. One of my first concerns is that there's
> no way to identify w
On Sunday 26 April 2009 07:00:52 you wrote:
> On Apr 25, 2009, at 6:27 PM, Raimar Sandner wrote:
> > On Saturday 25 April 2009 18:27:44 Raimar Sandner wrote:
> >> Hello,
> >>
> >> when gnupg trusts a key as a result of trustdb calculations, I
> >> wo
On Saturday 25 April 2009 22:00:05 John W. Moore III wrote:
> Raimar Sandner wrote:
> > In the end it is of course a people thing whether you trust a key or not,
> > no mathematical model ever can replace your final decision. So there is a
> > big difference in gpg saying &q
On Saturday 25 April 2009 18:27:44 Raimar Sandner wrote:
> Hello,
>
> when gnupg trusts a key as a result of trustdb calculations, I would
> like to know what the chain depth for the given key is.
[snip]
> As of now I can only think of gradually reducing max-cert-depth,
> recalcu
On Saturday 25 April 2009 20:58:44 david wrote:
> Raimar Sandner wrote:
> > Hello,
> >
> > when gnupg trusts a key as a result of trustdb calculations, I would
> > like to know what the chain depth for the given key is.
[snip]
>
> Hi, I don't wish to be over-
Hello,
when gnupg trusts a key as a result of trustdb calculations, I would
like to know what the chain depth for the given key is.
I know that I can control the maximal acceptable depth with the
max-cert-depth configuration parameter. I would like to keep the
default of 5, but it is still a diff
18 matches
Mail list logo
