After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 116200 - g_mime_multipart_signed_verify doesn't check correctly
g_mime_multipart_signed_verify doesn't check correctly
Status: RESOLVED FIXED
Product: gmime
Classification: Other
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Jeffrey Stedfast
Jeffrey Stedfast
Depends on:
Blocks:
 
 
Reported: 2003-06-28 18:03 UTC by gnome
Modified: 2005-04-14 20:00 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description gnome 2003-06-28 18:03:04 UTC
In g_mime_multipart_signed_verify the to be checked part is being
generated, this results in a bad signature. And this happens because the
generated header format doesn't match the original format.
Examples of headers where this happens are:
Content-Type: multipart/mixed; boundary=7AUc2qLy4jB3hD7Z
Content-Disposition: attachment; filename="balsa-rfc3156-patch-2003-06-25.gz"

They are generated as:
Content-Type: multipart/mixed; boundary="7AUc2qLy4jB3hD7Z"
Content-Disposition: attachment;
 filename="balsa-rfc3156-patch-2003-06-25.gz"
Comment 1 Jeffrey Stedfast 2003-06-30 13:43:05 UTC
yep, known bug... just never got around to adding it to bugzilla :-)

this is something I've been trying to work out for the 2.1 development
branch...
Comment 2 Jeffrey Stedfast 2004-07-07 20:59:51 UTC
I've changed a number of things that help to reduce the liklihood of header
re-formatting in the 2.1.x releases (especially 2.1.7), but there's still no
guarentee.
Comment 3 Jeffrey Stedfast 2005-04-14 20:00:04 UTC
calling this FIXED now