Bug 44045 – urandom deactivation (-boot) needs to be fixed for systemd

Bug 44045 - urandom deactivation (-boot) needs to be fixed for systemd


Summary:	urandom deactivation (-boot) needs to be fixed for systemd

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	System setup
Version:	UCS 4.2
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UCS maintainers
QA Contact:	UCS maintainers

URL:
Keywords:	systemd

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2017-03-23 15:17 CET by Janek Walkenhorst
Modified:	2020-07-03 20:54 CEST (History)
CC List:	1 user (show)

See Also:	43841
What kind of report is it?:	Development Internal
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

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

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

Description Janek Walkenhorst

2017-03-23 15:17:48 CET

univention-system-setup-boot.postinst:
 # Remove urandom init-script from runlevels (Bug #30034). Will be reactivated by scripts/10_basis/20initscripts
 update-rc.d -f urandom remove
 rm /var/lib/urandom/random-seed

20initscripts:
 # Activate urandom init script, was deactivated when installing univention-system-setup-boot
 # Runlevel settings should equal initscripts.postinst values
update-rc.d urandom start 55 S . start 30 0 6 . || exit $?


setup.log:
__NAME__:10_basis/20initscripts Configuring init-scripts
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults

This needs to be updated for systemd, probably systemd-random-seed.service

Comment 1 Ingo Steuwer

2020-07-03 20:54:12 CEST

This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.