Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#36200 - Mutt doesn't always accept ssl certs

Attached to Project: Arch Linux
Opened by Konsi (0x6b) - Friday, 19 July 2013, 09:13 GMT
Last edited by Gaetan Bisson (vesath) - Wednesday, 24 July 2013, 01:46 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Gaetan Bisson (vesath)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Hi,

Mutt can't remember the (a)lways accept option for ssl certs.

The "fix" seems to be, to build mutt against GnuTLS rather then OpenSSL.

Prove: https://bugzilla.redhat.com/show_bug.cgi?id=620978

Cheers,
0x6b
This task depends upon

Closed by  Gaetan Bisson (vesath)
Wednesday, 24 July 2013, 01:46 GMT
Reason for closing:  Upstream
Additional comments about closing:  Please reopen this bug if you need further support and/or know a satisfying way to fix it.
Comment by Gaetan Bisson (vesath) - Friday, 19 July 2013, 10:51 GMT
Remembering SSL certificates works for me...
Comment by Konsi (0x6b) - Friday, 19 July 2013, 16:27 GMT
I guess this depends if you have a valid one.

I have a invalid cert inside the Intranet.
Forcing the Microsoft-Admin-Guy will take _forever_ (bureaucracy)

Now Mutt asks me to remember my choice.
Next time it asks again.
Comment by Gaetan Bisson (vesath) - Saturday, 20 July 2013, 01:07 GMT
I am reluctant to patch Mutt unless the changes have been accepted upstream.
Could you try a development build of Mutt and see if your problem is gone (it probably will not be, but it would be great if it was)? I have one in my personal repo: http://arch.vesath.org/all/mutt-hg-20130602.f467353f5657-1.src.tar.gz
Otherwise, if you explain to me why you cannot use ssl_verify_host=no (shouldn't you trust IP addresses on your internal network?) then I might be convinced to add https://bugzilla.redhat.com/attachment.cgi?id=436392 ...
Comment by Konsi (0x6b) - Saturday, 20 July 2013, 12:57 GMT
It's just about adding '--with-gnutls' to the configure command.

However, I found out that using gnutls causes more problems than openssl.
So, in my case, it's better to stay with openssl and use the
ssl_verify_host variable as you suggested.

On monday I'll give check if the bug is fixed (most likely not).

Thanks for your support.

Loading...