Bug 125795 - STARTTLS configuration on but no certs created
STARTTLS configuration on but no certs created
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: sendmail (Show other bugs)
All Linux
medium Severity low
: ---
: ---
Assigned To: Thomas Woerner
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2004-06-11 10:47 EDT by Steve Bonneville
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-09-01 22:55:23 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2004:299 normal SHIPPED_LIVE Updated sendmail packages 2004-09-01 00:00:00 EDT

  None (edit)
Description Steve Bonneville 2004-06-11 10:47:39 EDT
Description of problem:

Between 8.12.10-1 and 8.12.11-3.3, the default configuration in
/etc/mail/sendmail.mc changed to uncomment the defines enabling
STARTTLS certs for the server and for SSL client authentication.
However, no certificates are actually included, leading to errors like
the following in /var/log/maillog:

Jun 11 10:22:48 server1 sendmail[4998]: STARTTLS=server: file
/etc/mail/certs/cert.pem unsafe: No such file or directory

These lines should probably be commented back out in the default
configuration, unless and until we somehow autogenerate appropriate
SSL certificates.

Version-Release number of selected component (if applicable):

Comment 1 Jay Turner 2004-09-01 22:55:24 EDT
An errata has been issued which should help the problem 
described in this bug report. This report is therefore being 
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, 
please follow the link below. You may reopen this bug report 
if the solution does not work for you.


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