Bug 429147 - Sylpheed reportedly doesn't allow for acceptance of a self-signed certificate
Sylpheed reportedly doesn't allow for acceptance of a self-signed certificate
Status: CLOSED UPSTREAM
Product: Fedora
Classification: Fedora
Component: sylpheed (Show other bugs)
rawhide
All Linux
low Severity low
: ---
: ---
Assigned To: Michael Schwendt
Fedora Extras Quality Assurance
http://bugs.debian.org/cgi-bin/bugrep...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-01-17 11:15 EST by Lubomir Kundrak
Modified: 2008-01-17 13:04 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-01-17 13:04:20 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Lubomir Kundrak 2008-01-17 11:15:04 EST
Description of problem:

From Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=355192

It seems like our version won't have the problem with accepting the expired
certificated, but they claim that it might be considered a security issue that a
unverifiable certificate can not be accepted permanently. I am not sure, so I
intentionally do not include Security keyword.

Could you please verify if you find something bad about the way sylpheed handles
the certificates and eventually communicate that upstream?
Comment 1 Michael Schwendt 2008-01-17 13:04:20 EST
It is known already. Users ask about it from time to time, e.g.
see: http://www.sraoss.jp/pipermail/sylpheed/2007-May/001233.html

Without a comfortable certificate management user-interface
where users must examine a certificate in detail, accepting a
self-signed certificates permanently would be insecure.
With a half-baked solution, users would simply click "OK"
without verifying a certificate actually.

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