Joey Schulze un jour écrivit:
Simon Valiquette wrote:
In the Securing Debian Manual, the key id to use to send an encrypted
email to the security team is 363CCD95, but on the following link,
it is F2E861A3 that is listed instead.
http://www.debian.org/security/faq.en.html#contact
Maybe the
Simon Valiquette wrote:
>
> Hello, I am finishing the French translation of the Securing Debian
> Manual, and I noticed something about the key to use to contact the
> Debian Security Team.
>
> In the Securing Debian Manual, the key id to use to send an encrypted
> email to the security team
On Mon, Dec 29, 2008 at 03:50:48PM +0100, Kurt Roeckx wrote:
> On Mon, Dec 29, 2008 at 07:32:47AM -0500, Simon Valiquette wrote:
> > So here are my questions:
> >
> > 1. Do both keys are still valid?
> >
> > 2. If the key F2E861A3 is legitimate (which I think it is because
> > I have a trust pa
On Mon, Dec 29, 2008 at 07:32:47AM -0500, Simon Valiquette wrote:
>
> So here are my questions:
>
> 1. Do both keys are still valid?
>
> 2. If the key F2E861A3 is legitimate (which I think it is because
> I have a trust path to it), wouldn't it makes sense to sign it with
> the old key as well
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Hello, I am finishing the French translation of the Securing Debian
Manual, and I noticed something about the key to use to contact the
Debian Security Team.
In the Securing Debian Manual, the key id to use to send an encrypted
email to the s
5 matches
Mail list logo