Bug 1151748 - WeeChat does not use the correct default SSL/TLS CA certificate file
Summary: WeeChat does not use the correct default SSL/TLS CA certificate file
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: weechat
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
Assignee: Nobody's working on this, feel free to take it
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-11 10:24 UTC by dave.null
Modified: 2020-11-05 09:44 UTC (History)
5 users (show)

Fixed In Version: weechat-1.0.1-2.el7
Clone Of:
Environment:
Last Closed: 2014-11-01 17:14:52 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description dave.null 2014-10-11 10:24:56 UTC
Description of problem:
By default, weechat does not point to the default Fedora CA certificate file.
The WeeChat default is /etc/ssl/certs/ca-certificates.crt but on Fedora, the
ca-certificates packages put the certs in /etc/pki/tls/certs/ca-bundle.crt

This can be easily fixed with a user defined WeeChat setting, for example:
/set weechat.network.gnutls_ca_file /etc/pki/tls/certs/ca-bundle.crt


Version-Release number of selected component (if applicable):
weechat-1.0.1-1.fc20.i686

How reproducible: always

Steps to Reproduce:
With a default WeeChat configuration,
1. start weechat
2. connect a SSL enabled IRC server, for example:
   /connect chat.freenode.org/7000 -ssl

Actual results:
Connection fails with the message:
[...]
gnutls: peer's certificate is NOT trusted
gnutls: peer's certificate issuer is unknown


Expected results:
Connection succeed in SSL/TLS with good certificate verification.

Proposed fix:
The default CA file can be changed at build time with the CA_FILE variable. When building with CMake, the fix is just adding "-DCA_FILE=/etc/pki/tls/certs/ca-bundle.crt" on the cmake command line in the spec file.

Additional info:
When testing with chat.freenode.org the SSL connection sometimes fails for other reasons which is not related to this issue.


Thanks.

Comment 1 dave.null 2014-10-11 11:05:23 UTC
Typo in description: for testing, use "chat.freenode.net" instead of "chat.freenode.org".

Comment 2 Jamie Nguyen 2014-10-22 22:50:40 UTC
Thanks for reporting this! Fix on the way..

Comment 3 Fedora Update System 2014-10-22 23:15:13 UTC
weechat-1.0.1-2.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/weechat-1.0.1-2.fc21

Comment 4 Fedora Update System 2014-10-22 23:16:12 UTC
weechat-1.0.1-2.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/weechat-1.0.1-2.fc20

Comment 5 Fedora Update System 2014-10-22 23:44:09 UTC
weechat-1.0.1-2.el7 has been submitted as an update for Fedora EPEL 7.
https://admin.fedoraproject.org/updates/weechat-1.0.1-2.el7

Comment 6 Fedora Update System 2014-10-23 16:07:01 UTC
Package weechat-1.0.1-2.el7:
* should fix your issue,
* was pushed to the Fedora EPEL 7 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=epel-testing weechat-1.0.1-2.el7'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-3565/weechat-1.0.1-2.el7
then log in and leave karma (feedback).

Comment 7 Fedora Update System 2014-11-01 17:14:52 UTC
weechat-1.0.1-2.fc21 has been pushed to the Fedora 21 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 8 Fedora Update System 2014-11-07 02:38:16 UTC
weechat-1.0.1-2.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 9 Fedora Update System 2014-11-09 15:40:59 UTC
weechat-1.0.1-2.el7 has been pushed to the Fedora EPEL 7 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.