how to have a gpg public key?

[Louie Miranda]

How can i have a gpg public key?

--
Thank you,
Louie Miranda (louie@axishift.ath.cx)



--
To UNSUBSCRIBE, email to [email]debian-user-request@lists.debian.org[/email]
with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]

[Louie Miranda]

> Go to a locksmith in your nearest town and ask them to cut you one. They
keep

> blanks on hand.

Have you done this? So how was it? Was it so good?

--
Thank you,
Louie Miranda (louie@axishift.ath.cx)


----- Original Message -----
From: "Michael D. Crawford" <crawford@goingware.com>
To: <debian-user@lists.debian.org>
Sent: Tuesday, July 22, 2003 1:35 PM
Subject: Re: how to have a gpg public key?

> > How can i have a gpg public key?

>
> Go to a locksmith in your nearest town and ask them to cut you one. They

keep

> blanks on hand.
>
> Warmest regards,
>
> Mike
> --
> Michael D. Crawford
> GoingWare Inc. - Expert Software Development and Consulting
> [url]http://www.goingware.com[/url]
> [email]crawford@goingware.com[/email]
>
> Tilting at Windmills for a Better Tomorrow.
>
> "I give you this one rule of conduct. Do what you will, but speak
> out always. Be shunned, be hated, be ridiculed, be scared,
> be in doubt, but don't be gagged."
> -- John J. Chapman, "Make a Bonfire of Your Reputations"
> [url]http://www.goingware.com/reputation/[/url]
>
>
> --
> To UNSUBSCRIBE, email to [email]debian-user-request@lists.debian.org[/email]
> with a subject of "unsubscribe". Trouble? Contact

[email]listmaster@lists.debian.org[/email]

>

--
To UNSUBSCRIBE, email to [email]debian-user-request@lists.debian.org[/email]
with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]

[Stephen Touset]

Sorry to be brusque, but:

man gpg

Louie Miranda wrote:

>How can i have a gpg public key?
>
>--
>Thank you,
>Louie Miranda (louie@axishift.ath.cx)
>
>
>
>
>

--
To UNSUBSCRIBE, email to [email]debian-user-request@lists.debian.org[/email]
with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]

[Jeff Wiegley, Ph.D.]

Bah dum ba...

1st: A problem with this list is its huge signal to noise ratio.
If you don't have an answer to give jokes are less than helpful.

2nd: Louie, the answer to your question is:

You don't need just a gpg public key. What you probably want is a
gpg key pair. Having just a public key doesn't do you much good.
You need both a private key and a public key; the two keys
together make up an asymmetric key pair. (and they are dependent
on each other; you can just use any public key with any private
key. they have to be created together.

Since your post implies you may be new to the world of
asymmetric ciphers I'll add a little bit of theory here...

symmetric ciphers are ones such that only a single key is
needed. You use the single key to turn plaintext into
cipher text by encrypting the plaintext with the key
(well actually you use an algorithm that requires both
the key and the plaintext as input.)

its "symmetric" because to turn the ciphertet back into
plaintext (decryption) you use the same key.

This has some disadvantages: anybody that knows the key
can encrypt and decrypt anything to/from you and they
can even give the key away and then basically everybody
can encrypt and decrypt your messages and you are just
wasting time.

They don't readily support current security concepts of
digital signatures. But they are very strong for their
key size (in bits) compared to what I will now describe...

So along comes asymmetric key systems.

basically you have two keys A and B. If you encrypt with
key A you need to know only key B to decrypt it. GPG, RSA, PGP
take this a bit further they also support the fact that if
you encrypt with B you can decrypt the message with A.
(not all asymmetric systems do B->A)

So what? Well let's call A "private" and B "public". (we
could have called either one private it wouldn't matter.) Nobody,
and I mean nobody, else should ever know the private key other than
the owner (i.e. you). But *everybody* can/should/may be
allowed to have complete knowledge of the "public" key.

Now if they want to send you a message that only you can
read they encrypt the message with your public key knowing
that only you possess the private key necessary to decrypt
the message and other people who also know the public key
still can't decrypt it because the public key won't decrypt
that which was encrypted using the public key. (If you want
to send encrypted messages to them you need to know *their*
public key and encrypt with that. (that part is a bit
unintuitive to security beginners who are use to using the
same set of secrets to both send and receiver messages.)

But now you can also digitally sign messages. You simply encrypt
the message with your private key. people know your public key
and only the public key will decrypt the message is if it was
encrypted with your private key. AND *only* you know the private
key. Therefor if the public key successfully decrypts the message
then it must have been you that wrote it.

So it good to have a private key for signing your outgoing
mail so that others can know and use your public key to
verify that you actually wrote the messages.

This is glossing over a lot of the problems associated with
two sticky points:
1) how do you reliably distribute your public key?
2) What happens if somebody else actually does come to
know your private key? (this requires the ability to
"revoke" a key pair.)

These are why Veri$ign charges $75 per year to maintain
certificates on their distribution system.

anyhow, that was a lot of theory, here's your answer...

################################################## ############
This is what you really wanted to know...
gpg --gen-key
################################################## ############

it will interactively ask you a bunch of questions.
You probably want DSA ElGamal keys since these let
you sign and encrypt stuff

keysize of 1024 is ok, but some recent work in the area of
number theory indicates that somebody with about 10 billion
dollars can create a specialized computer capable of cracking
such keys in a not-unreasonable period of time.

I go with 2048, the disadvantage is that it takes quite a bit
more processor time to sign and encrypt using larger keys. It
also makes your armor (ascii) representation of your public
key crazy huge.

you will be asked for a passphrase... This is sort of like
a password. actually its a symmetric key that you pick that
will be used to encrypt your private key. This way even if
your system gets stolen that can't figure out what the
private key is since it, itself, is encrypted. Anything that
needs access to your private key such a mail user agent
will prompt you for this passphrase.

Want to be fascist like me? check out
[url]http://world.std.com/~reinhold/diceware.html[/url]

its a system for creating memorizable passphrases that are
many words long. each letter of such a passphrase generates
approximately 3 bits of entropy (random data). So a such
a passphrase consisting of 6 words with an average length
of 4 characters generates 24 characters * 3 bits = 72 bits.
Thus your private key will be encrypted with a strength
roughly equal to a purely random 9 character password. But
you'll be able to remember it (while we are back on
theory: symmetric keys are generally stronger than asymmetric
systems. it takes about 1024 bit asymmetric keys to obtain
the same strength as an 80 bit symmetric key. Such
such a passphrase it really strong.

Oh... you're second question is gonna be... what happened
to the keys gpg generated? Well it stored them on your
"keyring". you collect keys and store them on this "ring"
and then you can select which one you want to use to decrypt
or encrypt something.

But you need to get your public key in an exportable fashion...

################################################## ####################
Your second bit of meat...

gpg --export --armor
################################################## ####################

now you can give the resulting block to the rest of the world.
(I've assumed you only have one public key on your keyring.

gpg --list-keys
gpg --list-public-keys
gpg --list-private-keys

will show you your various keys. Though since you are asking
about creation you'll probably just have the one single
public key and the above command will export the armor block
version of it to stdout.

gpg --export --armor somestring

would export the public key that has "somestring" as part
of the name given to it when it was created.

umm... sorry for the length but it should have answered your
question and more.

last tip... "evolution" is apretty good graphical mail user
agent and it has good support built in for signing and
encrypting mail using GPG/PGP

What you should wind up with is something that looks like this...

-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.2.1 (GNU/Linux)

mQGiBD8czdURBACrz4UfwKHHqIFBa+1spiFn8OJ+JoHyZpUlDZ XjV5qWMLTjJ+FD
S1YTHWAb49n9e+ZwzlPiHs5tSeKXK3bKHddwrmuBscRe1ZXKZu nN1U/TDd49VZbD
5YHWdxCQwnLK3RnZ/oVhqvSLEV9F8ACcBkaegrOj3iDIVxEvxww3RZzVfwCgvHs2
caFrD9FqgDSbIoZe7NsQrTED/0T+XdIxtDjNQNdA5TS7E1HdIBqXsen3hygYsre/
3O8cmD8uwINhygYu4VUXmMRBOnt3AzKdIm72UV2ShtrVL3V6qJ DIGwhx4mlolKer
325mR1OfDSsHE2G3cSmmbdsptFdtdldpTZ9ZxKW5vfnQkcWXHw BQ+I7LfVuqg2cw
XEULA/0aTAJYf9DHnBilqmPRtixgT9c47ZWsreSF3wD07Q0T4YotzIHs vmKJgA6X
mEwB/Q7PQWhzYgL9WyRzNF3dxlZ855jUBiyJOpSBTXFDs625U3/384l+h+2cGAyk
0GMQ0xuh4N7vicwwj/gJic3nsoimoBedtPmkrIvBZ+GCXBi6VrQlSmVmZnJleSBX
aWVnbGV5LCBQaEQgPGplZmZ3QGN5dGUuY29tPohZBBMRAgAZBQ I/HM3VBAsHAwID
FQIDAxYCAQIeAQIXgAAKCRBMXNqawuYjSSW6AJ95YTZMycvSTN DBtrttOTj0l3LT
7wCdHGdFrzBiGQezckJOLKwkihGbxim5Ag0EPxzN3xAIALrNh1 X84y42rZyLfn72
s5KChctZskNuCAbcEtxCNDEFNx9FzRvzv9T3j30RF8dE66phRc AZwvuF1PKUbw3a
ojIFTm1Ow50p1cVxXnfNh0IOsfElrUz9Tor4yQxZkoUUS190eC b6FCk3vB7wC1vK
ilKtdkl6UCzxbwOZhpqBxQ49jidDz9DoAUFiZn7+Fcey9ZaDsM DN0xqIabvrv1BP
zy58lHCX8j5wpcIsjBBbQ77kUUWkdQYqdqznHoWd7JgTWMngfH AnktUgZsrXxes6
t6nLrabjsGhhh9fzv31/hVmvYWKh0fBn5bDEXJlq0252QSqjsVpqrj1QcFd6+kSt
JzcAAwUH/0DmAI0yOUopFP+G4NCuJ1Jp/2FtRjkAIM8gRHFLxojpyB6lk9wykrms
wmuS3JBw5smpZ20DIUU8vca82nWxQgk9XE8G/qwVrWH+oTfyS3nnOKWuaZyDx40a
b16Gudp/wQMIex9kvN51PjPc2ltW94OzPwJ7c0nnqyXZWirlxBphuQjuXH JDl6qZ
rlHvQYGD5FNAxNyM4EERJi3bU4L9QZ1QqepJ/ppYAcVLqRS7RlCs/r0rGgubwb8o
uZlYkmTeoB1vSSzzaGcrAcP3eos3oJsPIxQAN+YY0DCVfdUCyA urQWrAfy/P79Wm
ziSP26VJK3x7OTMcpYWyBCTu5rUfYriIRgQYEQIABgUCPxzN3w AKCRBMXNqawuYj
SXOUAJ91l+Rng/ZpVl9YEmYLLzENX2hLZwCgg4yfhVq6gWe48+YwQ29z8IA5iJw=
=Fvnd
-----END PGP PUBLIC KEY BLOCK-----

which I just generated using the above two commands.

For more see "man gpg". Sorry if you already knew all the
theory stuff and were just having gpg syntax problems.

- Jeff

On Mon, 2003-07-21 at 22:35, Michael D. Crawford wrote:

> > How can i have a gpg public key?

>
> Go to a locksmith in your nearest town and ask them to cut you one. They keep
> blanks on hand.
>
> Warmest regards,
>
> Mike
> --
> Michael D. Crawford
> GoingWare Inc. - Expert Software Development and Consulting
> [url]http://www.goingware.com[/url]
> [email]crawford@goingware.com[/email]
>
> Tilting at Windmills for a Better Tomorrow.
>
> "I give you this one rule of conduct. Do what you will, but speak
> out always. Be shunned, be hated, be ridiculed, be scared,
> be in doubt, but don't be gagged."
> -- John J. Chapman, "Make a Bonfire of Your Reputations"
> [url]http://www.goingware.com/reputation/[/url]
>

--
To UNSUBSCRIBE, email to [email]debian-user-request@lists.debian.org[/email]
with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]

[Jeff Wiegley, Ph.D.]

I would have to actually see the output of gpg --list-keys
to definitively answer but...

1) be wary distributing any information related to private
keys. So you probably shouldn't show anybody the output
of --list-secret-keys...

2) "fingerprints" are distillation of some large amount of
information down to a very small set of information with
the property that if two large chunks differ by even a
small amount then the keys will differ as well (and
preferably will differ by a great deal.

So you should be able to tell if you are talking about
the same keys by comparing their fingerprints.

I don't know what the "sub" is either.

- Jeff

On Tue, 2003-07-22 at 00:48, Louie Miranda wrote:

> I mean, for ex this one.
>

> > GPG/PGP ID: 26384A3A
> > Fingerprint: D9FF DF4A 2D46 A353 A289 E8F5 AA75 DCBE 2638 4A3A

>
> Is this different from the one that i generated?
>
>
> --
> Thank you,
> Louie Miranda (louie@axishift.ath.cx)
>
>
>
> ----- Original Message -----
> From: "Louie Miranda" <louie@axishift.ath.cx>
> To: "Jeff Wiegley, Ph.D." <jeffw@cyte.com>; "Debian-User"
> <debian-user@lists.debian.org>
> Sent: Tuesday, July 22, 2003 3:38 PM
> Subject: Re: how to have a gpg public key?
>
>

> > These are good docs, really appreciate it a lot. Specially im new w/
> > encryption.
> >
> > I have generated the keys....
> >
> > and..
> >
> > webdev:~# gpg --list-keys
> > /root/.gnupg/pubring.gpg
> > ------------------------
> > pub ***
> > sub ***
> >
> > I wonder whats the sub ? I also see other users have gnupgpid: x9374483
> > (whatever)
> > Is that all related to the pub section?
> >
> > i thank you personally.
> >
> > --
> > Thank you,
> > Louie Miranda (louie@axishift.ath.cx)
> >
> >
> > ----- Original Message -----
> > From: "Jeff Wiegley, Ph.D." <jeffw@cyte.com>
> > To: "Louie Miranda" <louie@axishift.ath.cx>
> > Cc: <debian-user@lists.debian.org>
> > Sent: Tuesday, July 22, 2003 2:08 PM
> > Subject: Re: how to have a gpg public key?
> >
> >
> > --
> > To UNSUBSCRIBE, email to [email]debian-user-request@lists.debian.org[/email]
> > with a subject of "unsubscribe". Trouble? Contact

> [email]listmaster@lists.debian.org[/email]

> >

--
To UNSUBSCRIBE, email to [email]debian-user-request@lists.debian.org[/email]
with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]

[Hugo Vanwoerkom]

"Jeff Wiegley, Ph.D." <jeffw@cyte.com> wrote in
message news:<bYP1.6a4.7@gated-at.bofh.it>...

> Bah dum ba...
>
> 1st: A problem with this list is its huge signal to

noise ratio.

> If you don't have an answer to give jokes are

less than helpful.

>
> 2nd: Louie, the answer to your question is:
>

<snip>
What do you do when you switch systems? E.g. I heve
done the key-gen thing and all, but now I want to gen
a new Debian Sarge from scratch. What do you have to
copy to have what you had before?

Hugo

__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
[url]http://sitebuilder.yahoo.com[/url]


--
To UNSUBSCRIBE, email to [email]debian-user-request@lists.debian.org[/email]
with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]

[Andreas Janssen]

Hugo Vanwoerkom wrote:

> "Jeff Wiegley, Ph.D." <jeffw@cyte.com> wrote in
> message news:<bYP1.6a4.7@gated-at.bofh.it>...

>> 2nd: Louie, the answer to your question is:
>>

> <snip>
> What do you do when you switch systems? E.g. I heve
> done the key-gen thing and all, but now I want to gen
> a new Debian Sarge from scratch. What do you have to
> copy to have what you had before?

Keys are by default stored in ~/.gnupg/pubring.gpg and
~/.gnupg/secring.gpg.

best regards
Andreas Janssen

--
Andreas Janssen
[email]andreas.janssen@bigfoot.com[/email]
PGP-Key-ID: 0xDC801674
Registered Linux User #267976


--
To UNSUBSCRIBE, email to [email]debian-user-request@lists.debian.org[/email]
with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]

[Colin Watson]

On Tue, Jul 22, 2003 at 01:56:16PM -0700, Hugo Vanwoerkom wrote:

> What do you do when you switch systems? E.g. I heve done the key-gen
> thing and all, but now I want to gen a new Debian Sarge from scratch.

I don't understand what you mean by "gen a new Debian Sarge from
scratch". Keys are independent of the system you generated them on.

> What do you have to copy to have what you had before?

~/.gnupg/secring.gpg, and you probably want at least
~/.gnupg/pubring.gpg too for convenience.

Cheers,

--
Colin Watson [cjwatson@flatline.org.uk]


--
To UNSUBSCRIBE, email to [email]debian-user-request@lists.debian.org[/email]
with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]

[Vineet Kumar]

* Jeff Wiegley, Ph.D. (jeffw@cyte.com) [030721 23:28]:

> Bah dum ba...
>
> 1st: A problem with this list is its huge signal to noise ratio.

Wow, we're doing pretty well if a huge S/N ratio is considered a problem
around here!

Personally, I'd say people fscking up the threads is a real problem =)

... but nobody asked me, so I won't open that can of worms just yet
(until it explodes into a full-blown rant, that is).

good times,
Vineet
--
[url]http://www.doorstop.net/[/url]
--
[url]http://www.eff.org/[/url] Defeinding freedom in the digital world

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/Hs8e1nIkYEQE+iMRArQ8AJ4vjY/+YsSrhgNn7Gc6sYHGcUX0hQCeOwcK
CLGITHz4fA7lPB2nEDuSz2k=
=ON8x
-----END PGP SIGNATURE-----

[Paul Johnson]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tue, Jul 22, 2003 at 12:41:47PM +0800, Louie Miranda wrote:

> How can i have a gpg public key?

See gnupg documentation. I think kgpg is a clicky interface for KDE
GnuPG users, which might help you out if you're new as well.

- --
.''`. Paul Johnson <baloo@ursine.ca>
: :' : proud Debian admin and user
`. `'`
`- Debian - when you have better things to do than fix a system
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/H672J5vLSqVpK2kRAq2gAJ4+VPZbFG/ki1nXcHPUqISs7SnVwwCguUx5
XwNnCllSbIHdlTM+u2CuhUk=
=c9Bf
-----END PGP SIGNATURE-----


--
To UNSUBSCRIBE, email to [email]debian-user-request@lists.debian.org[/email]
with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]

[Paul Johnson]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, Jul 21, 2003 at 11:08:53PM -0700, Jeff Wiegley, Ph.D. wrote:

> 1st: A problem with this list is its huge signal to noise ratio.
> If you don't have an answer to give jokes are less than helpful.

Looking at lists.debian.org, I see this is a list for debian users,
not topic specific, nor are there gaurantees that you won't get your
leg pulled if you ask a silly/obvious question. 8:o) Seems like a
better solution to this feature instead of bitching about it is to
steer users towards asking better questions.

[url]http://www.catb.org/~esr/faqs/smart-questions.html[/url]

Or for the ones who absolutely refuse to put forth any effort
whatsoever on their part, just expect us to send them the Magic
Answer:

[url]http://www.debian.org/consultants/[/url]

> basically you have two keys A and B. If you encrypt with
> key A you need to know only key B to decrypt it. GPG, RSA, PGP
> take this a bit further they also support the fact that if
> you encrypt with B you can decrypt the message with A.
> (not all asymmetric systems do B->A)

We'll assume A is private and B is the public key.

Not quite. In the above example, the first scenario (encrypting with
private, decrypting with public key) is highly improbable (though the
odds get better with the more computing power and time you have,
consider a supercomputer and several (dozen?) years), AFAIK, otherwise
why not just use symettrical keys?

> (we
> could have called either one private it wouldn't matter.) Nobody,
> and I mean nobody, else should ever know the private key other than
> the owner (i.e. you). But *everybody* can/should/may be
> allowed to have complete knowledge of the "public" key.

x-hkp://pgp.mit.edu/ and other Keyservers are your friend.

> Now if they want to send you a message that only you can
> read they encrypt the message with your public key knowing
> that only you possess the private key necessary to decrypt
> the message and other people who also know the public key
> still can't decrypt it because the public key won't decrypt
> that which was encrypted using the public key. (If you want
> to send encrypted messages to them you need to know *their*
> public key and encrypt with that. (that part is a bit
> unintuitive to security beginners who are use to using the
> same set of secrets to both send and receiver messages.)

Basically, what's going on here is you're standing in a public
hallway. You want to give something to your friend. It's
valuable/personal, and you're not comfortable leaving it taped to the
door for everybody/anybody to see/steal. So you slip it under the
door into his private apartment. If you've got a public key for
someone, you're standing in the hallway outside their apartment.
Encrypt it with their public key and send off the encrypted message
and you've slid it under the door.

It's fairly safe to assume, however, that unlike at Initech, your
coworkers are extremely unlikely to go off on a grand-theft-stapler-
induced rage, break into the recipient's office
and use your message to burn the building down.[1]

> But now you can also digitally sign messages. You simply encrypt
> the message with your private key. people know your public key
> and only the public key will decrypt the message is if it was
> encrypted with your private key. AND *only* you know the private
> key. Therefor if the public key successfully decrypts the message
> then it must have been you that wrote it.

Actually, to sign a message, you don't need to encrypt it. Though in
an encrypted message, it's good to also sign it so the recipient knows
for sure who the sender is (though you can not sign it to remain
anonymous, though the practicality of this is limited).

> This is glossing over a lot of the problems associated with
> two sticky points:
> 1) how do you reliably distribute your public key?

Keyservers, ascii-armored in your .pgpkey file (if you run fingerd or
equiv) and on your website tend to be the big three ways of doing it.

> These are why Veri$ign charges $75 per year to maintain
> certificates on their distribution system.

Not that Verisign is trustworthy. This is a contributing factor as to
why S/MIME email is extremely rare.

> keysize of 1024 is ok, but some recent work in the area of
> number theory indicates that somebody with about 10 billion
> dollars can create a specialized computer capable of cracking
> such keys in a not-unreasonable period of time.

Well, theory and practice are two different things. When the FBI
seized Kevin Mitnick's machines, there were some PGP encrypted files.
Mitnick refused to cough up the password. For the five years or so
the FBI had his hardware, they couldn't crack his files. I know at
least before the government accountants started saying on CNN that war
could easily drive the US to bankruptcy before Bush is out of office
that they probably had some decent hardware at their disposal.[2]

> last tip... "evolution" is apretty good graphical mail user
> agent and it has good support built in for signing and
> encrypting mail using GPG/PGP

kmail also has a pretty nice GUI for doing the same. mutt has
seamless GPG/PGP support, though mutt is also somewhat hostile to
newbies and extremely hostile to Windows convertees[3].





[1] Office Space reference.

[2] I really wish CIC would grant me a visa already so I can get the
heck out of this madhouse before California completely destroys the
American west.

[3] Am I the only person who thinks Windows convertees are
artificially harder to teach unix than totally green
never-used-a-computer-before people?

- --
.''`. Paul Johnson <baloo@ursine.ca>
: :' : proud Debian admin and user
`. `'`
`- Debian - when you have better things to do than fix a system
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/H7p/J5vLSqVpK2kRAgJkAKCnyZk9scctWytea4Rl2x4tWYPW7QCfTy N0
MuNK2VPGZxtiihnEDx+CNzw=
=paJq
-----END PGP SIGNATURE-----


--
To UNSUBSCRIBE, email to [email]debian-user-request@lists.debian.org[/email]
with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]

[Paul Johnson]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tue, Jul 22, 2003 at 03:38:27PM +0800, Louie Miranda wrote:

> webdev:~# gpg --list-keys
> /root/.gnupg/pubring.gpg
> ------------------------
> pub ***
> sub ***
>
> I wonder whats the sub ? I also see other users have gnupgpid: x9374483
> (whatever)
> Is that all related to the pub section?

public key complete with a single name/email address. I think you
have to have at least one subkey on your public key, but I could be wrong.

- --
.''`. Paul Johnson <baloo@ursine.ca>
: :' : proud Debian admin and user
`. `'`
`- Debian - when you have better things to do than fix a system
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/H7rvJ5vLSqVpK2kRAjyWAJ9uw94Lo2KsyJRnKePkicEhKEZHmg CgpBUl
Vfi2URWvso4ee+7qEkgoy5M=
=Sifp
-----END PGP SIGNATURE-----


--
To UNSUBSCRIBE, email to [email]debian-user-request@lists.debian.org[/email]
with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]

[Paul Johnson]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tue, Jul 22, 2003 at 03:48:23PM +0800, Louie Miranda wrote:

> I mean, for ex this one.
>

> > GPG/PGP ID: 26384A3A
> > Fingerprint: D9FF DF4A 2D46 A353 A289 E8F5 AA75 DCBE 2638 4A3A

>
> Is this different from the one that i generated?

Yes, it should be. If it's not, something's wrong.

- --
.''`. Paul Johnson <baloo@ursine.ca>
: :' : proud Debian admin and user
`. `'`
`- Debian - when you have better things to do than fix a system
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/H7siJ5vLSqVpK2kRAvlAAJ9N/tKuJc0KUDLJtZy9HLsOVq/RcQCgwSaV
4ZSCwIL0zSrLtYeeAPJxtfw=
=vRua
-----END PGP SIGNATURE-----


--
To UNSUBSCRIBE, email to [email]debian-user-request@lists.debian.org[/email]
with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]

[Paul Johnson]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tue, Jul 22, 2003 at 01:56:16PM -0700, Hugo Vanwoerkom wrote:

> What do you do when you switch systems? E.g. I heve
> done the key-gen thing and all, but now I want to gen
> a new Debian Sarge from scratch. What do you have to
> copy to have what you had before?

If you need to copy your PGP data someplace else, you want to copy
your ~/.gnupg directory.

- --
.''`. Paul Johnson <baloo@ursine.ca>
: :' : proud Debian admin and user
`. `'`
`- Debian - when you have better things to do than fix a system
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/H7unJ5vLSqVpK2kRAgSBAJ9frRmSXDnheq1bimDNzuB/Y6DDhgCgmCaL
NlettjTvuB5K/vYji3gTbno=
=q8Vv
-----END PGP SIGNATURE-----


--
To UNSUBSCRIBE, email to [email]debian-user-request@lists.debian.org[/email]
with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]