Understood, and thanks for the help! some more questions... Why do they
label the private key line line "sub" when you run gpg --list-keys? It
would seem that if they label the public key line "pub", that it would
make sense to label the private key line "pri" or "priv"...
Also, what about the expiration? I used the gpg --edit-key to change the
expiration, but --list-keys does not show the change... what gives?
Thanks again!
Doug
On Mon, 2003-02-17 at 10:59, Derek Glidden wrote:
> On Mon, 2003-02-17 at 10:03, Doug Koobs wrote:
> > I wasn't sure if I was doing this correctly, so when I created, I set it
> > to expire in 1 day... I just trued to use
>
> You probably shouldn't have uploaded it to the keyserver network if it
> was going to expire. You can regenerate as many keys as you need and
> upload one when you finally get it worked out.
>
> It's not that it's a big deal, but unless you also generate a
> key-revocation and revoke the key, you'll have an expired key hanging
> around the keyservers pretty much forever. So any time anyone wants to
> search for and download your key, they'll still see the old one. Not a
> huge deal, but...
>
> > gpg --edit-key d7469a12
> >
> > and used the "expire" option to change the key to never expire, but when
> > I do --list-keys, I still get
> >
> > pub 1024D/D7469A12 2003-02-17 Doug Koobs <dkoobs@dkoobs.com>
> > sub 1024g/4C369838 2003-02-17 [expires: 2003-02-18]
> >
> > I assume this means my key will still expire today, but I'm not sure
> > what the second line is... Any ideas?
>
> That's your private key.
>
> GnuPG, being public/private key encryption, generates two keys - your
> public and your private key. Things encrypted with your public key can
> only be decrypted with your private key, and vice-versa. (Sorry if this
> is too basic.) If someone wants to encrypt something that only you can
> receieve, they encrypt it with your public key. If you want to "sign"
> something that is "provably" yours to within the limits of the
> recipient's keyring's ring-of-trust, you generate a checksum of the
> content and sign the checksum with your private key - when someone
> receives it, they decode the checksum with your public key, and if that
> succeeds, then the content is checked against the checksum.
>
> So you have, for any "GnuPG key", two separate keys. When you
> "--list-keys" it shows you both.
>
> --
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> #!/usr/bin/perl -w
> $_='while(read+STDIN,$_,2048){$a=29;$b=73;$c=142;$t=255;@t=map
> {$_%16or$t^=$c^=($m=(11,10,116,100,11,122,20,100)[$_/16%8])&110;
> $t^=(72,@z=(64,72,$a^=12*($_%16-2?0:$m&17)),$b^=$_%64?12:0,@z)
> [$_%8]}(16..271);if((@a=unx"C*",$_)[20]&48){$h=5;$_=unxb24,join
> "",@b=map{xB8,unxb8,chr($_^$a[--$h+84])}@ARGV;s/...$/1$&/;$d=
> unxV,xb25,$_;$e=256|(ord$b[4])<<9|ord$b[3];$d=$d>>8^($f=$t&($d
> >>12^$d>>4^$d^$d/8))<<17,$e=$e>>8^($t&($g=($q=$e>>14&7^$e)^$q*
> 8^$q<<6))<<9,$_=$t[$_]^(($h>>=8)+=$f+(~$g&$t))for@a[128..$#a]}
> print+x"C*",@a}';s/x/pack+/g;eval
>
> usage: qrpff 153 2 8 105 225 < /mnt/dvd/VOB_FILENAME \
> | extract_mpeg2 | mpeg2dec -
>
> http://www.cs.cmu.edu/~dst/DeCSS/Gallery/
> http://www.eff.org/ http://www.anti-dmca.org/
>
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 15:29:29 EDT