Hi Pawel!
On Thu, 04 Jan 2001, Pawel Wiecek wrote:
> On Jan 4, 1:11pm, Peter Palfrader wrote:
> > (see a thread here on -devel perhaps a
> > month or two ago).
>
> I can't find it in the archive...
http://lists.debian.org/debian-devel-0010/msg00683.html & Fups
On Jan 4, 1:11pm, Peter Palfrader wrote:
> New keys sent to keyring.debian.org via gpg --send will take approximatly
Gosh...
> forever. New keys have to be added my hand by the keyring maintainer and
Emailed him as well...
> this might long (up 2 12 months?) (see a thread here on -devel perhap
Hi Pawel!
On Thu, 04 Jan 2001, Pawel Wiecek wrote:
> How long does it take usually for a (GPG) key sent to keyring.debian.org
> to show up in official keyring (and maintainers database)?
> I'm waiting for my new GPG key to show up for quite a few weeks and it seems a
> bit excessive to me :^)
Ne
How long does it take usually for a (GPG) key sent to keyring.debian.org
to show up in official keyring (and maintainers database)?
I'm waiting for my new GPG key to show up for quite a few weeks and it seems a
bit excessive to me :^)
BTW -- our web interface to developers database (http://db.debi
On Tue, Mar 14, 2000 at 10:55:31AM +0200, joost witteveen wrote:
> Hi,
>
> Until recently I only had a PGP key, and as
> suggested by /usr/share/doc/debian-keyring/README.gz, I've
> now generated a GPG one, signed it with my PGP key, and
> submitted it to [EMAIL PROTECTED]
>
> A couple of hours
On Tue, Mar 14, 2000 at 10:55:31AM +0200, joost witteveen wrote:
> That was all march 10, nearly 4 days ago, and fakeroot still isn't
> dinstalled.
Was it rejected, or is it just stuck? If it was rejected, you have to
reupload, if it is stuck, then ssh to master, go into incoming directory,
and ru
Hi,
Until recently I only had a PGP key, and as
suggested by /usr/share/doc/debian-keyring/README.gz, I've
now generated a GPG one, signed it with my PGP key, and
submitted it to [EMAIL PROTECTED]
A couple of hours later I uploaded a package (fakeroot_0.4.4-5)
signed with my new GPG keys.
That
On Tue, Oct 05, 1999 at 12:39:50PM +0200, Rene Mayrhofer wrote:
> > > Is it possible to use a key created by pgp5 for package signing ? The
> > > key works for me when I use it with gpg, both the opposite is not true
> > > (e.g. pgp5 is unable to verify a signature created with a gpg key). I am
> >
Joseph Carter wrote:
>
> On Mon, Oct 04, 1999 at 07:45:23PM +0200, Rene Mayrhofer wrote:
> > Is it possible to use a key created by pgp5 for package signing ? The
> > key works for me when I use it with gpg, both the opposite is not true
> > (e.g. pgp5 is unable to verify a signature created with
On Mon, 4 Oct 1999, Rene Mayrhofer wrote:
> Is it possible to use a key created by pgp5 for package signing ? The
> key works for me when I use it with gpg, both the opposite is not true
> (e.g. pgp5 is unable to verify a signature created with a gpg key). I am
> no maintainer yet and so I want t
On Mon, Oct 04, 1999 at 07:45:23PM +0200, Rene Mayrhofer wrote:
> Is it possible to use a key created by pgp5 for package signing ? The
> key works for me when I use it with gpg, both the opposite is not true
> (e.g. pgp5 is unable to verify a signature created with a gpg key). I am
> no maintainer
Hi all
Is it possible to use a key created by pgp5 for package signing ? The
key works for me when I use it with gpg, both the opposite is not true
(e.g. pgp5 is unable to verify a signature created with a gpg key). I am
no maintainer yet and so I want to start cleanly. What is the "right"
way if
On Fri, Oct 16, 1998 at 04:06:18PM +1000, Chris Leishman wrote:
> At the moment I am using pgp2i, but I would like to try and change to
> gnupg. My question is - will I need to generate a new public/private key,
> or is it possible to use my pgp one with gnupg?
Technically it is possible to use y
Hi all,
At the moment I am using pgp2i, but I would like to try and change to
gnupg. My question is - will I need to generate a new public/private key,
or is it possible to use my pgp one with gnupg?
I would really prefer to keep my old one, as otherwise I'll have to
distribute a new key, not t
14 matches
Mail list logo
