Re: Building cvs 2.1, some errors

[Albrecht Dreß <albrecht dress arcor de>]

> 2 - in rfc2135.[ch] :
> rfc3156.c:955: error: conflicting types for  
> `libbalsa_rfc2440_decrypt_buffer'
> rfc3156.h:95: error: previous declaration of  
> `libbalsa_rfc2440_decrypt_buffer'
> I have removed LibBalsaCodeset codeset from the arguments in the .h file  
> as it seems extraneous regarding the implementation.

I'm working on a port of my "new" gpgme (ver. 0.4.5) support to balsa 2.1  
- currently using the latest tarball instead of the cvs, though. Work  
stalled a little bit recently, partly due to my "real life" work, and  
partly because gmime's rfc3156 support is seriously broken at least with  
ver. 2.1.2 (didn't check 2.1.3 yet, but it's still on the TODO list). This  
bug sometimes (see attached message) prevents proper signature checking  
for rfc3156 messages of which the signed stuff itself is again a  
multipart. Inter alia, all such messages produced with balsa 2.0 are  
always passed wrongly to the crypto engines, making gpg support more or  
less unusable.

Anyway, I hope I can release a first patch for the "new" gpgme support in  
balsa around easter (or maybe a week later).

Cheers, Albrecht.

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 Albrecht Dreß  -  Johanna-Kirchner-Straße 13  -  D-53123 Bonn (Germany)
       Phone (+49) 228 6199571  -  mailto:albrecht.dress@arcor.de
_________________________________________________________________________

---

• From: Albrecht Dreß <albrecht dress arcor de>
• To: fejj ximian com
• Subject: BUG in gmime-2.1.2
• Date: Wed, 10 Mar 2004 21:59:55 +0100

Hi,

I ran into a nasty bug in gmime 2.1.2 when trying to verify a multipart/ 
signed which in turn contains a multipart mixed. A message (verbatim cut  
from the mbox file)

[----snip--------------------------------------------------------------]
Content-Type: multipart/signed; micalg=PGP-SHA1;
        protocol="application/pgp-signature"; boundary="Clx92ZfkiYIKRjnr"
Content-Disposition: inline


--Clx92ZfkiYIKRjnr
Content-Type: multipart/mixed; boundary="qlTNgmc+xy1dBmNv"
Content-Disposition: inline


--qlTNgmc+xy1dBmNv
Content-Type: text/plain; Format=Flowed; DelSp=Yes; charset=ISO-8859-15
[----snip--------------------------------------------------------------]

is passed to the verify engine as

[----snip--------------------------------------------------------------]
Content-Type: multipart/mixed; boundary=qlTNgmc+xy1dBmNv
Content-Disposition: inline


--qlTNgmc+xy1dBmNv
Content-Type: text/plain; Format=Flowed; DelSp=Yes; charset=ISO-8859-15
[----snip--------------------------------------------------------------]

Please notice that the double quotes in the boundary parameter were lost,  
of course breaking any signature verification.

Any ideas?

Cheers, Albrecht.


-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 Albrecht Dreß  -  Johanna-Kirchner-Straße 13  -  D-53123 Bonn (Germany)
       Phone (+49) 228 6199571  -  mailto:albrecht.dress@arcor.de
_________________________________________________________________________

PGP signature

---

PGP signature