Bug 749930 - sylpheed: does not alert when an SSL certificate has expired
Summary: sylpheed: does not alert when an SSL certificate has expired
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 749931
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-28 21:51 UTC by Vincent Danen
Modified: 2019-09-29 12:48 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-10 10:58:10 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Vincent Danen 2011-10-28 21:51:05 UTC 
A Debian bug report [1] indicated that Sylpheed does not warn you when an SSL certificate has expired.

I tried this on Fedora 15 with sylpheed-3.1.1-1.fc15 and had it obtain a certificate from my server, and told it to accept it permanently (saved to ~/.sylpheed-2.0/trust.crt).  I did this with today's date.  Then I set the date to a month from now and it still accepts the certificate:

% cat trust.crt| openssl x509 -fingerprint -sha1 -text|grep After
            Not After : Nov 20 14:45:33 2011 GMT
% date
Mon Nov 28 08:49:09 MST 2011

Apparently Sylpheed has suffered from other SSL-related weaknesses in the past, and it looks like this may have worked previously but no longer seems to.

[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=355192#98
Comment 1 Vincent Danen 2011-10-28 21:52:26 UTC 
Created sylpheed tracking bugs for this issue

Affects: fedora-all [bug 749931]
Comment 2 Product Security DevOps Team 2019-06-10 10:58:10 UTC 
This CVE Bugzilla entry is for community support informational purposes only as it does not affect a package in a commercially supported Red Hat product. Refer to the dependent bugs for status of those individual community products.
Note You need to log in before you can comment on or make changes to this bug.