hi,Sam Varshavchik��
Thanks for your good hits.I konw now that if i want to send an encrypt message,I
must kown the recipient the PUBLIC KEY at first and then encrypt it with the PUBLIC
KEY.
>* All the parties create their own public/private keypairs, and exchange
>their PUBLIC keys
I can create public/private keypairs with sqwebmail. But i have trouble in
exchanging PUBLIC KEYS.
If i want to mail encrypt messages each other with a stranger,I must tell him my
PUBLIC KEY,and get his PUBLIC KEY.
>With sqwebmail, public keys may be exchanged by sending them as attachments.
> From the attachment window there's a drop-down box to attach your public
>key. When the recipient receives the attached public key, there will be a
>prompt to import the public key.
That means i should send a encrypt message with my own PUBLIC KEY to the stranger to
tell him my PUBLIC KEY .
When the recipient read the encrypt message ,it is shown like following
"
attachement: application/pgp-signature (0.1K)
display / download
"
The signature content is like
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.5 (GNU/Linux)
iD8DBQA7pebrtcs2OoCrGbYRAlpKAKCffA0tfdchuyoo2I/t4M6OB4eHYwCeNOxb
PwSOiU1t3E3OeTztW1K8fYY=
=GJN/
-----END PGP SIGNATURE-----
But it seems no promt to import the public key .
Why? My sqwebmail version is 2.1.1,Must i upgrade it to 3.0.0?
I
>sqwebmailsoft writes:
>
>> hi,Sam Varshavchik
>> I am sorry I cant catch your words of "Tell the sender to use
>MIME-GPG encapsulation".I created an encrypt key at first ,Then I sent a encrypt
>message to a user who is in my local mail server through sqwebmail. If the user is
>itself. I can decrypt the message well.But if the user is different from the
>sender.To decrypt the message is always fail
>> The information is like following
>> gpg: encrypted with ELG-E key, ID DEBF014B
>> gpg: encrypted with ELG-E key, ID 37F45440
>> gpg: encrypted with ELG-E key, ID 94E5E1CA
>> gpg: decryption failed: secret key not available
>> gpg: [don't know]: invalid packet (ctb=0f)
>>
>> How to import the secrte key which is not available just now and how to use the
>encrypt key on sqwebmail?
>
>You do not import secret keys, in this particular instance.
>
>It sounds like you do not fully understand how public-key encryption works.
>There are many resources on the web with more information, but the general
>idea is:
>
>* All the parties create their own public/private keypairs, and exchange
>their PUBLIC keys.
>
>* Mail is encrypted with the recipient's PUBLIC key. The recipient uses the
>corresponding PRIVATE key, which only the recipient has, to decrypt the
>message. Only the recipient has the private key to decrypt the message.
>The sender may also optionally sign the message with the sender's PRIVATE
>key, which only the sender has, and the recipient will verify the signature
>with the sender's PUBLIC key.
>
>With sqwebmail, public keys may be exchanged by sending them as attachments.
> From the attachment window there's a drop-down box to attach your public
>key. When the recipient receives the attached public key, there will be a
>prompt to import the public key.
>
>
>
>--
>Sam
��
��
sqwebmailsoft
[EMAIL PROTECTED]
