Bug 1672285
Summary: | FreeRADIUS should not generate certificates at package installation | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Stephen Gallagher <sgallagh> |
Component: | freeradius | Assignee: | Alex Scheel <ascheel> |
Status: | CLOSED ERRATA | QA Contact: | Filip Dvorak <fdvorak> |
Severity: | medium | Docs Contact: | lmcgarry |
Priority: | unspecified | ||
Version: | 8.0 | CC: | ascheel, extras-qa, fdvorak, fhanzelk, lemenkov, lmcgarry, nikolai.kondrashov, pasik, rharwood, tscherf |
Target Milestone: | rc | ||
Target Release: | 8.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | freeradius-3.0-8030020200806223029.1e4bbb35 | Doc Type: | Bug Fix |
Doc Text: |
.FreeRADIUS no longer generates certificates during package installation
Previously, FreeRADIUS generated certificates during package installation, resulting in the following issues:
* If FreeRADIUS was installed using Kickstart, certificates might be generated at a time when entropy on the system was insufficient, resulting in either a failed installation or a less secure certificate.
* The package was difficult to build as part of an image, such as a container, because the package installation occurs on the builder machine instead of the target machine. All instances that are spawned from the image had the same certificate information.
* It was difficult for an end-user to generate a simple VM in their environment as the certificates would have to be removed and regenerated manually.
With this update, the FreeRADIUS installation no longer generates default self-signed CA certificates nor subordinate CA certificates. When FreeRADIUS is launched via `systemd`:
* If all of the required certificates are missing, a set of default certificates are generated.
* If one or more of the expected certificates are present, it does not generate new certificates.
|
Story Points: | --- |
Clone Of: | 1672284 | Environment: | |
Last Closed: | 2020-11-04 03:58:12 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1574783, 1672284, 1717880, 1720667 | ||
Bug Blocks: | 1842946 |
Description
Stephen Gallagher
2019-02-04 13:16:03 UTC
*** Bug 1857230 has been marked as a duplicate of this bug. *** Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: freeradius:3.0 security and bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:4799 It came to my attention recently that some customers don't like this behavior. To avoid this, use a systemd override file (execute `sudo systemctl edit radiusd.service` to create one) with the contents: [Service] ExecStartPre= ExecStartPre=/usr/sbin/radiusd -C to disable certificate generation at service startup. This can be tested with `sudo systemctl restart radiusd.service`. Please refer to the systemd docs for more information about unit file overrides. I do not recommend editing the original systemd unit file we ship with FreeRADIUS RPM in RHEL as it is package configuration and subject to change in a future release. |