Re: [Evolution-hackers] how to get evo 1.2.1 to recognize gpg encrypted messages



On Thu, 2003-03-06 at 16:32, Jacob Martinson wrote:
> all,
> 
> i am sending encrypted messages from the command line on solaris with a
> combination of mailx and gpg.  i am having a hard time getting evolution
> 1.2.1 to recognize the messages as being gpg-encrypted.  it won't prompt
> for the passphrase.  rather, it just displays the encrypted message.  
> 
> i looked at a couple gpg-encrypted messages that were sent from another
> 1.0.8 evo client to look at headers and whatnot in order to figure out
> how it was figuring out when to decrypt... anyway, after adding all the
> same headers i saw in the working email, i still can't get it to work...
> i am appending a non-working message.  any information on how evolution
> 1.2.1 determines when to decrypt a message (or what i need to do from
> the sending side to tell it to) would be greatly appreciated!!!

probably not in the right formats...

> 
> -jacob
> 
> 
> snippet of a non-working message:
> 
> Content-return: prohibited
> Date: Wed, 05 Mar 2003 15:55:07 -0600
> From: Jacob Martinson <jmartinson info234 com>
> Subject: test1
> To: jmartinson indigopool com
> Message-id: <1046901308 1274 1 camel localhost localdomain>
> MIME-version: 1.0
> X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10)
> Content-type: multipart/encrypted; protocol="application/pgp-encrypted";
> boundary="=-d4nEyI1DG6lbwrVbxldZ"
> X-Evolution-Source: mbox:/var/spool/mail/jmartinson
> 
> 
> --=-d4nEyI1DG6lbwrVbxldZ
> Content-Transfer-Encoding: 7bit
> Content-Type: application/pgp-encrypted
> 
> Version: 1
> --=-d4nEyI1DG6lbwrVbxldZ
> Content-Type: application/octet-stream; name=encrypted.asc
> Content-Description: This is an encrypted message part
> Content-Transfer-Encoding: 7bit
> 
> -----BEGIN PGP MESSAGE-----
> Version: GnuPG v1.0.7 (GNU/Linux)
> 
> hQIOA8OBduTW9YhlEAf+KrBWoFgQsho7x9cezofxJC9nEgr1CK3P3eFKcS+iEdE3
> dW1fsumAfN694is3CL/XMEVW7VYkrcvXDo6w2u6wTCAEGi4QXzDeqBzxISuGSDAh
> keFf54IsMPbNboMNYoAXjNiTX8cFq1Kzb5COFsCO28hPGIDLR/ivc3psqt2SEUpo
> 
> 
> 

the above MIME structure looks okay I think, but I can't tell if the
encrypted blurb is in the correct format in its decrypted form.

ie, when you decrypt the blurb, it needs to be a MIME part.

> snippet of a non-working message:
> 
> Content-return: prohibited
> Date: Thu, 06 Mar 2003 19:22:02 +0000 (GMT)
> Date-warning: Date header was inserted by
> nammta01.sugar-land.nam.slb.com
> From: jmartins ipweb4 indigopool com
> Subject: ipops-test13
> Bcc: 
> Message-id: <0HBC006FMDSQF2 nammta01 sugar-land nam slb com>
> X-Evolution-Source: mbox:/var/spool/mail/jmartinson
> Mime-Version: 1.0
> Content-Transfer-Encoding: 8bit
> 
> Content-type: multipart/encrypted; protocol="application/pgp-encrypted";
> boundary="=-d4nEyI1DG6lbwrVbxldZ"

the extra blank line above should not exist. but there *should* be a
blank line *after* the Content-Type header.

> --=-d4nEyI1DG6lbwrVbxldZ
> Content-Transfer-Encoding: 7bit
> Content-Type: application/pgp-encrypted
> 
> Version: 1
> --=-d4nEyI1DG6lbwrVbxldZ

where's the Content-Type: application/octet-stream header go? :-)

it needs to be here.

> -----BEGIN PGP MESSAGE-----
> Version: GnuPG v1.2.1 (SunOS)
> 
> hQIOA1pJc7SLiu8hEAf/cLN3AaC+2v17kp1NZ4W8D2wtM/QPp8u+Qb+kjeO2fkFi
> /MN5BTib76kswdjgNTg/laEkPPGJG2B0d4Kgn2n+O+ihpAgYucaAXfjleZN4tt7c
> e42lfaxQwdPMXcN5gPVQMG+NE3q0x74WrjmQzjHw9MvJ8oHlGBS65YRpVAwk6Zhz
> 2GdahdD3C2H6y1W2WAxbzVSpm+J6SAIfsXdAypyo4ICHgCLdZxiaFiNl5UHlIEv/
> BKfKPp5H4LimaxUzOfINLmtY/a/AFiudNyv31kk0QU1AjOzyMqvo01GMAHWO/CeG
> LEyT33oa5E7O4UV0hXtsPkW5YMGt6Z3Yx4TbMZpoCwf/Yu+cfZAiLAuEqpXa+go5

can't tell if the encrypted blurb is in MIME format.

I suggest you read http://www.ietf.org/rfc/rfc3156.txt

Jeff

-- 
Jeffrey Stedfast
Evolution Hacker - Ximian, Inc.
fejj ximian com  - www.ximian.com




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]