-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
And I'll add that most rsync servers I've used usually keep things set
at 7 for a balance between processor cost and compression rates. If
processor cost is an issue for you, it pays to test a few of the
compression levels out to see what's acceptable.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Is there a good way to send signed HTML email messages? If I understand
the problems come up when gpg thinks an html tag is a gpg tag. So
pgp/mime solves this problem?
- -Francis
Patrick Brunschwig wrote:
>
> Maybe you should disable composition of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
How do we know it's really yours or that you are really you? I'll accept
that this message was signed with it, but by signing you key it means I
have no doubt that it really does indeed belong to Dan Mundy. And I've
nver met him.
I personally don't ha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
With all this talk about key signing and trust models, I noticed that I
don't trust any of your public keys. I supose I'd have to trust one or
two of you first, but how do the key signatures get transfered around?
Email? or can you upload the signature
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
How would I revoke a key I no longer have a private key for? I
understand I can't do the same thing, but can I do something like the
opposite of signing? Signing against a key?
- -Francis
Patrick Brunschwig wrote:
>
> You can revoke the keys you do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've got
keyserver ldap://keyserver.pgp.com
in my gpg.conf, but my enigmail has a few listed.
random.sks.keyserver.penguin.de
pgp.dtype.org
keyserver.kjsl.com
ldap://certserver.pgp.com
It uses random.sks.keyservcer.penguine.de by default.
A random
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It's trying to run it's interface on your terminal, how are you running
the program? Is it just a command prompt, or is it through xterm or some
other terminal program?
- -Francis
Gustavo Tabares wrote:
> Hi all,
>
> I'm having problems generating
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Keep your keys under your user account and specify that root should look
there in your gpg.conf. This way your user account will still be able to
read and use them even after root's had a go at them.
- -Francis
David Shaw wrote:
> On Tue, May 10, 200