Hi,
Here's a ``bug report'' from a Debian user, it's unreproducible,
fairly lacking in anything resembling detail and is probably useless,
and for that I apologize, but I figure I might as well punt it here
and see if it means anything to anyone/Werner.
James
~Yawn And Walk North~ http://yawn.nocrew.org/
------- Start of forwarded message -------
To: james@nocrew.org
Subject: Re: Replacing/phasing out PGP (was Re: Idea for non-free organization)
References: <19980630183118.A13326@mercury.oz.net> <Pine.LNX.3.96.980701033227.12809A-100000@ns1.greenbush.com> <19980701110942.58843@wi.leidenuniv.nl> <dmmg1gl8shh.fsf@dcsun4.comp.brad.ac.uk> <dmmg1glh4fw.fsf@dcsun4.comp.brad.ac.uk>
From: Ben Gertzfield <che@debian.org>
Date: 01 Jul 1998 12:47:10 -0700
Message-ID: <yttlnqdfj5t.fsf@gilgamesh.cse.ucsc.edu>
It took me two tries to generate this key.
gpg: Warning: using insecure memory!
We need to generate a lot of random bytes. It is a good idea to perform
some other action (work in another window, move the mouse, utilize the
network and the disks) during the prime generation; this gives the random
number generator a better chance to gain enough entropy.
+++++..+++++..+++++......+++++........+++++...++++++++++....++++++++++..........+++++..++++++++++...+++++..+++++.................+++++.........+++++.......+++++....+++++....+++++..+++++........+++++...+++++.........+++++....+++++..+++++......................+++++>...........+++++.+++++..............................>+++++<...+++++................................<....+++++...........+++++
gpg: seckey-cert.c:197: protect_secret_key: Assertion `!((cert->skey[i]) && ((cert->skey[i])->flags&2))' failed.
zsh: abort gpg --gen-key
Running it a second time was okay. Go fig. *grin*
Ben
--
Brought to you by the letters R and N and the number 14.
"X -- because it's extra. Y -- because it's extra." -- TMBG
Debian GNU/Linux -- where do you want to go tomorrow? http://www.debian.org/
I'm on FurryMUCK as Che, and EFNet and YiffNet IRC as Che_Fox.
------- End of forwarded message -------
Here's a ``bug report'' from a Debian user, it's unreproducible,
fairly lacking in anything resembling detail and is probably useless,
and for that I apologize, but I figure I might as well punt it here
and see if it means anything to anyone/Werner.
James
~Yawn And Walk North~ http://yawn.nocrew.org/
------- Start of forwarded message -------
To: james@nocrew.org
Subject: Re: Replacing/phasing out PGP (was Re: Idea for non-free organization)
References: <19980630183118.A13326@mercury.oz.net> <Pine.LNX.3.96.980701033227.12809A-100000@ns1.greenbush.com> <19980701110942.58843@wi.leidenuniv.nl> <dmmg1gl8shh.fsf@dcsun4.comp.brad.ac.uk> <dmmg1glh4fw.fsf@dcsun4.comp.brad.ac.uk>
From: Ben Gertzfield <che@debian.org>
Date: 01 Jul 1998 12:47:10 -0700
Message-ID: <yttlnqdfj5t.fsf@gilgamesh.cse.ucsc.edu>
It took me two tries to generate this key.
gpg: Warning: using insecure memory!
We need to generate a lot of random bytes. It is a good idea to perform
some other action (work in another window, move the mouse, utilize the
network and the disks) during the prime generation; this gives the random
number generator a better chance to gain enough entropy.
+++++..+++++..+++++......+++++........+++++...++++++++++....++++++++++..........+++++..++++++++++...+++++..+++++.................+++++.........+++++.......+++++....+++++....+++++..+++++........+++++...+++++.........+++++....+++++..+++++......................+++++>...........+++++.+++++..............................>+++++<...+++++................................<....+++++...........+++++
gpg: seckey-cert.c:197: protect_secret_key: Assertion `!((cert->skey[i]) && ((cert->skey[i])->flags&2))' failed.
zsh: abort gpg --gen-key
Running it a second time was okay. Go fig. *grin*
Ben
--
Brought to you by the letters R and N and the number 14.
"X -- because it's extra. Y -- because it's extra." -- TMBG
Debian GNU/Linux -- where do you want to go tomorrow? http://www.debian.org/
I'm on FurryMUCK as Che, and EFNet and YiffNet IRC as Che_Fox.
------- End of forwarded message -------