From: andre <andre@liquidprivacy.net>
To: Bruno Wolff III <bruno@wolff.to>
Cc: pgsql-sql@postgresql.org
Cc: pgsql-novice@postgresql.org
Subject: Re: Guarantee uniqueness of PGP key
Date: Tue, 21 May 2002 06:56:16 -0500
Message-ID: <20020521115616.C87C780269@pepe.lfcity.org> (raw)
In-Reply-To: <20020521115442.GA17061@wolff.to>
References: <20020520201709.A3F8A80269@pepe.lfcity.org>
<20020521115442.GA17061@wolff.to>
Yes, I've decided to relax the unique-ness constraint on the public key. The
email address is still guaranteed unique. And we send out an encrypted
verification email that only the person with the private key can decrypt and
respond to. Thus, it doesn't really hurt to have multiple people paste in the
same pub key.
If I really wanted uniqueness, I think you (and the others who replied) are
correct that I should be storing the 'fingerprint' in a separate column.
/andre
On Tuesday 21 May 2002 06:54 am, Bruno Wolff III wrote:
> On Mon, May 20, 2002 at 15:17:09 -0500,
>
> andre <andre@liquidprivacy.net> wrote:
> > The problem is that some PGP keys are over 2713 bytes, and postgres (7.2)
> > gives the error:
>
> You might want to rethink your design. You probably want just the RSA or
> DSA public key to be unique. Otherwise you will treat different versions of
> what is essentially the same key as being different. (This might be due
> to be signed by a different set of keys.) I suspect that this isn't what
> you want. I think even the craziest people are using keys that should
> be around 1000 bytes. Paranoid people (or those needing very long lived
> public keys) are using ones half that size.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: andre@liquidprivacy.net, bruno@wolff.to, pgsql-novice@postgresql.org
Subject: Re: Guarantee uniqueness of PGP key
In-Reply-To: <20020521115616.C87C780269@pepe.lfcity.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox