Gnupg

[Alain Schroeder]

On Mon, Mar 05, 2001 at 03:35:42PM +0100, Adam Jendrosek wrote:
> At 15:19 05.03.01, you wrote:
> >On Mon, Mar 05, 2001 at 02:43:47PM +0100, Adam Jendrosek wrote:
> > >
> > > Könnt ihr mir mal sagen,
> > > wie ich als normaler User einen PGP Schlüssel erzeugen kann zur Zeit kann
> > > das nur root.
> >
alain at butterfly:~$ ls -la `which gpg`
-rwsr-xr-x    1 root     root       562236 Feb 25 06:38 /usr/bin/gpg

Funktionier aber auch nicht suid-root.

Vielleicht solltest du einfach mal dein .gnupg Verzeichnis löschen, wenn
du eh nur ganz von vorne anfangen möchtest?

xxxxx at butterfly:~$ rm -rf .gnupg/
xxxxx at butterfly:~$ gpg --gen-key
gpg (GnuPG) 1.0.4; Copyright (C) 2000 Free Software Foundation, Inc.
This program comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions. See the file COPYING for details.

gpg: Warning: using insecure memory!
gpg: /home/xxxxx/.gnupg: directory created
gpg: /home/xxxxx/.gnupg/options: new options file created
gpg: you have to start GnuPG again, so it can read the new options file
jenny at butterfly:~$ gpg --gen-key
gpg (GnuPG) 1.0.4; Copyright (C) 2000 Free Software Foundation, Inc.
This program comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions. See the file COPYING for details.

gpg: Warning: using insecure memory!
gpg: /home/xxxxx/.gnupg/secring.gpg: keyring created
gpg: /home/xxxxx/.gnupg/pubring.gpg: keyring created
Please select what kind of key you want:
   (1) DSA and ElGamal (default)
   (2) DSA (sign only)
   (4) ElGamal (sign and encrypt)
Your selection? 1
DSA keypair will have 1024 bits.
About to generate a new ELG-E keypair.
              minimum keysize is  768 bits
              default keysize is 1024 bits
    highest suggested keysize is 2048 bits
What keysize do you want? (1024) 
Requested keysize is 1024 bits   
Please specify how long the key should be valid.
         0 = key does not expire
      <n>  = key expires in n days
      <n>w = key expires in n weeks
      <n>m = key expires in n months
      <n>y = key expires in n years
Key is valid for? (0) 
Key does not expire at all
Is this correct (y/n)? y
                        
You need a User-ID to identify your key; the software constructs the
user id
from Real Name, Comment and Email Address in this form:
    "Heinrich Heine (Der Dichter) <heinrichh at duesseldorf.de>"

Real name: asdfasdf
Email address: asdfasdf at asdf.com
Comment: asdf                   
You selected this USER-ID:
    "asdfasdf (asdf) <asdfasdf at asdf.com>"

Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? o
You need a Passphrase to protect your secret key.    

We need to generate a lot of random bytes. It is a good idea to perform
some other action (type on the keyboard, move the mouse, utilize the
disks) during the prime generation; this gives the random number
generator a better chance to gain enough entropy.
+++++++++++++++++++++++++.+++++.+++++++++++++++.++++++++++.+++++..+++++.++++++++++++++++++++..+++++..+++++++++++++++.+++++..+++++..++++++++++.+++++>.++++++++++...........................+++++
We need to generate a lot of random bytes. It is a good idea to perform
some other action (type on the keyboard, move the mouse, utilize the
disks) during the prime generation; this gives the random number
generator a better chance to gain enough entropy.
+++++.++++++++++++++++++++++++++++++.+++++..+++++++++++++++++++++++++..+++++..+++++.+++++.++++++++++.++++++++++.++++++++++.++++++++++++++++++++.......>.+++++................<.+++++.>+++++......+++++^^^
public and secret key created and signed.

So sollte das ablaufen.

	Bye,
	  - -- Alain -- -

-- 
I can't understand why people are frightened of new ideas.  I'm frightened
of the old ones."                       -- John Cage
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
URL: <http://lug-owl.de/pipermail/linux/attachments/20010305/6f37a764/attachment.sig>