Re: [Evolution] Import of S-Mime Certificate provides no response and does not import

[Peter Franzek <pfranzek yahoo com>]

Thank you for all the replies.

I was able to eventually import a certificate into Evolution running on Debian 16. I first imported the PFX file into MS Outlook 2010 on Windows 7, then exported the certificate back out of Outlook into another PFX file. I was then able to import the new file into Evolution. So the root issue was solved by the import and then re-export. Evolution does not like the original file, but MS Outlook is able to use it.

There is still the issue where the failure is not reported back to the user. Prior to posting to this thread, I had pulled down the 3.27.4 source and verified the same code specified earlier was still present.

I will work on setting up a VM and build Evolution from source. If I am able to track this down, I will look into a fix.

Thanks again for the responses.

Best regards,

Peter

On Tuesday, January 9, 2018, 2:31:02 PM EST, MayDay Computers <maydaycomputers gmail com> wrote:

MIME Import is working for me on Evolution 3.24.6 (Fedora 26).

---

 Travis Walden
 MayDayComputers gmail com

On Tue, Jan 9, 2018 at 1:16 PM, Pete Biggs <pete biggs org uk> wrote:

>
> I have been trying to import a certificate into Evolution 3.18.5.2.
> After following the import steps, selecting import on the
> Certificates section of Preferences, specifying NSS DB password and
> specifying Certificate password, the operation ceases with no
> feedback.
>
> Pulling down the source code for version 3.18.5.2 and examining the
> file evolution-3.18.5.2/smime/gui/ certificate-manager.c around line
> 992 exposes the likely reason for the import failure with no
> indication of failure.
>
> Lines 980 through 1008 select the proper import operation based on
> the certificate type, perform the selected import operation and
> report any errors that occur. Line 992 circumvents the error
> reporting by doing a return if the certificate type is unknown.
>
> The user experience may be better if error were set to indicate an
> unsupported certificate type and the error reported.

If it's a bug then it should be reported. Version 3.18.5.2 is long out
of date though and is not a current version so will not be fixed by the
Evolution developers. If you need that version fixed then you should
report it in your distribution's bug reporting system.

If you can reproduce the behaviour in a current version of Evolution
then file a bug in the Gnome bugzilla. If you can provide code to fix
it, then I'm sure that would be appreciated!  If you do report it,
please give the bugzilla number here so people searching for such a
problem in the future can find it.

P.

______________________________ _________________
evolution-list mailing list
evolution-list gnome org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/ mailman/listinfo/evolution- list

_______________________________________________
evolution-list mailing list
evolution-list gnome org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list