Created attachment 1316367 [details] Accept as previously submitting to a server with a self-signed certificate Description of problem: On my old Fedora 20, balsa would send email to my server that has a self-signed certificate. Upon upgrading to f26 and fixing other issues, that no longer worked, with STARTTLS failing because of in invalid cert, for X509_V_ERR_DEPTH_ZERO_SELF_SIGNED_CERT (=18). As balsa was upgraded only from 2.5.1 to 2.5.3 and libesmtp remained at 1.0.6, I suspect a change in openssl. Even though libesmtp requires compat-openssl10, there may still have been changes from openssl-1.0.1e-42.fc20 to compat-openssl10-1.0.2j-6.fc26. I think that a balsa user might reasonably expect that they will use their provided mail server even if it has a self-signed cert, as when sending mail the cert is only used to keep others from seeing the data. balsa should be changed to accept that error. A patch is included. Umm, additionally, as libesmtp requires compat-openssl10, I have built balsa against that as well. I didn't try mixing them so I don't know if that is needed. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
BTW, if the code I patched tries to get the certificate with SSL_get_peer_certificate(), it gets nothing back. I don't know openssl enough to know why, but `man SSL_get_peer_certificate` says that no certificate was provided (so how does openssl know that it is self-signed?). Anyway, adding an exception via libbalsa_is_cert_known() can't work.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
The problem still exists in F28 balsa. My patch still works (as it is the same minor release of balsa). Is there something I should do?
It looks to me like that problem is real. I am just not sure that blindly continuing when verification returns X509_V_ERR_DEPTH_ZERO_SELF_SIGNED_CERT is a good idea. We should give the user a chance to inspect the certificate, should we not?
If the user selects a mail server, they do expect to use it. As the cert is only used to ecrypt wire communications, I don't see any need for it to be "real", no matter who operates the mail server. Is there any threat?
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.