-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi again!
I have just posted a msg to the list
~http://lists.gnupg.org/pipermail/gnupg-users/2008-May/033328.html
and when I have received my own email, my signature doesn't verify! :-(
Could you help me to see what I'm doing wrong?
I'm sending
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Hello Ramon !
Ramon Loureiro [EMAIL PROTECTED] wrote:
@X-Mime-proxy: body=us-ascii
@X-Original-Content-Transfer-Encoding: 7bit
@X-Original-Content-Type: text/plain; charset=us-ascii; Format=flowed
I have just posted a msg to the list
~
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi
I just have ask for an email certificate to thawte.com thinking that
it's handled like a GPG signature (I thought that I'll have something
like a GPG certified signature)
Now I have the certificate I have installed it in Explorer and
Hello Ramon,
GnuPG really won't help you there, unless person other-side has way to
verify your signature.
As GnuPG is just a standard command line program, technologically
speaking, as long as the mail server allows, it should be able to sign
the E-mail automatically.
So it is probably
Ramon Loureiro wrote the following on 5/2/08 3:52 AM:
Hi
I just have ask for an email certificate to thawte.com thinking that
it's handled like a GPG signature (I thought that I'll have something
like a GPG certified signature)
Now I have the certificate I have installed it in
Hi again!
Charly Avital escribió:
Ramon Loureiro wrote the following on 5/2/08 3:52 AM:
Hi
I just have ask for an email certificate to thawte.com thinking that
it's handled like a GPG signature (I thought that I'll have something
like a GPG certified signature)
Now I have the
On Fri, 02 May 2008 09:38:25 +0200
Ramon Loureiro [EMAIL PROTECTED] wrote:
Could you help me to see what I'm doing wrong?
Possibly MTA re-encoding broke the sig. It is safer to
use BASE64 encoding rather than 7bit when sending msgs
with inline sigs.
best regards
Paul
--
It isn't worth a
With a certificate of this kind you can sign e-mail and decrypt e-mail
encrypted to you on the basis of S/MIME, which is a different protocol from
OpenPGP and incompatible with it. The pros of it is that it is supported by
mainstream MUAs, Outlook Express and MS Outlook, and the Web of Trust
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Oh! my God!
That's the neverending story!
it does not verify once again...
- -
enigmail gpg.exe --charset utf8 --batch --no
- -tty --status-fd 2 -d
gpg: invalid armor header: =20\r\n
gpg:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Charly Avital escribió:
Great!
I think I've got it!
(This msg should be MIME-signed with a Thawte certificationx)
The raw source of your message shows:
Content-type: multipart/signed; protocol=application/x-pkcs7-signature;
micalg=sha1;
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ramon Loureiro wrote:
Hi!
Is it possible to make a thunderbird filter that save my signed msgs in
some folder?
What in the email header must the filter check to see it has a (valid)
signature?
Or must it look for BEGIN PGP... strings into the
On 2-May-08, at 04:50 , Ramon Loureiro wrote:
Great!
I think I've got it!
(This msg should be MIME-signed with a Thawte certificationx)
Yes, it was signed, by the Thawte issued signature.
Basically a PKI-509 type signing is a tree of trust relationship,
where the root of the tree is a
12 matches
Mail list logo