GNOME Bugzilla – Bug 630503
S/MIME signed mail failed with message "security library: received bad data. (-8190)"
Last modified: 2010-10-15 07:50:00 UTC
Description: Ubuntu maverick (development branch) Release: 10.10 ii evolution 2.30.3-1ubuntu4 groupware suite with mail client and organizer ii evolution-common 2.30.3-1ubuntu4 architecture independent files for Evolution ii evolution-couchdb 0.5.0-0ubuntu1 Evolution support for CouchDB databases ii evolution-data-server 2.30.3-1ubuntu2 evolution database backend server ii evolution-data-server-common 2.30.3-1ubuntu2 architecture independent files for Evolution Data Server ii evolution-exchange 2.30.3-0ubuntu1 Exchange plugin for the Evolution groupware suite ii evolution-indicator 0.2.10-0ubuntu1 GNOME panel indicator applet for Evolution ii evolution-plugins 2.30.3-1ubuntu4 standard plugins for Evolution ii evolution-webcal 2.28.1-1 webcal: URL handler for GNOME and Evolution ii libebackend1.2-0 2.30.3-1ubuntu2 Utility library for evolution data servers ii libebook1.2-9 2.30.3-1ubuntu2 Client library for evolution address books ii libecal1.2-7 2.30.3-1ubuntu2 Client library for evolution calendars ii libedata-book1.2-2 2.30.3-1ubuntu2 Backend library for evolution address books ii libedata-cal1.2-6 2.28.3.1-0ubuntu5 Backend library for evolution calendars ii libedata-cal1.2-7 2.30.3-1ubuntu2 Backend library for evolution calendars ii libedataserver1.2-11 2.28.3.1-0ubuntu5 Utility library for evolution data servers ii libedataserver1.2-13 2.30.3-1ubuntu2 Utility library for evolution data servers ii libedataserverui1.2-8 2.30.3-1ubuntu2 GUI utility library for evolution data servers ii libevolution 2.30.3-1ubuntu4 evolution libraries (Note: This is a fresh upgrade from a working Lucid configuration... This was working before.) Sending a S/MIME signed mail fail. expected to happen: My mail should be signed then sent. happened instead: I can't send signed mails, I get the message: "Impossible de créer le message. Because "security library: received bad data. (-8190) - Le chiffrement de données a échoué", you may need to select different mail options" Next if I click OK, the send again, I get this message: "Impossible de créer le message. Because "Impossible de trouver de certificat pour « [...me...] »", you may need to select different mail options." I can send the message if I uncheck "Sign with S/MIME". With this two errors, if I go to Edit->preferences -> edit my mail account -> security and want to select a certificate, the "choose certificate box" is empty, no certificates available. If I go to Edit->preferences -> Certificates -> Your certificates, all my certs are present.
Thanks for a bug report. Is it possible some of them is expired? Though Evolution 2.30.3 is using nss sql backend (or tries to), that might be it too. Try to get the latest nss version, something like 3.12.6 or newer.
> Is it possible some of them is expired? Do you meen, is my certificate expired ? -> NO, valid until 04/2011 That's what I have about the libnss $ dpkg -l |grep libnss ii libnss-mdns 0.10-3ubuntu4 NSS module for Multicast DNS name resolution ii libnss3-1d 3.12.7-0ubuntu1 Network Security Service libraries Do you need other informations to correct this ? It would be great to have this feature corrected for the Ubuntu Maverick release. ;)
Please always post the Ubuntu bugtracker link. Also, why did you post this here and in Ubuntu's bugtracker? Why is this a GNOME issue?
@Andre Klapper Sorry for my mistakes ! I posted here and in Ubuntu's bugtracker because each time I've reported a bug related to evolution, it has been reported to upstream. So as Maverick release date approach very fast, I've decided to do the upstream report myself to save time. If it's not a GNOME (Evolution) issue, please could you give me clues to properly referrals this bug :) Regards
I thought this is related to bug #626066, but I do not seem to be able to reproduce this with patches from there kept or reverted and using nss-3.12.6 or 3.12.7. I have set a certificate to my email account (I verified it's accessible in account preferences), and when I do Send in the composer with a body filled I'm asked for a certificate store password and when I provide it the message is signed, encrypted and sent, all as expected. This is with actual git master, which should be pretty the same as 2.30.3, as nss changes got it, unfortunately, to stable release too.
Maybe it's an upgrade bug. I've generated a new certificate and imported/used it, all works fine. If I reconfigure my account to use my old certificate, I get the error on the comment #1. If from this "crash", I try to edit my account to select another certificate, only the new certificate is present. Restarting evolution let me choose between my 2 certificates. I think, that my private key was lost during upgrade process.
Hmm, pity. I'm closing this due to the above comment.