Bug 13197 - CU 177 Testing - message on start rngd fails to open libssl.so.1.1
Summary: CU 177 Testing - message on start rngd fails to open libssl.so.1.1
Status: CLOSED FIXED
Alias: None
Product: IPFire
Classification: Unclassified
Component: --- (show other bugs)
Version: 2
Hardware: unspecified Unspecified
: - Unknown - Minor Usability
Assignee: Arne.F
QA Contact:
URL:
Keywords:
: 13196 (view as bug list)
Depends on:
Blocks:
 
Reported: 2023-07-28 10:32 UTC by Adolf Belka
Modified: 2023-08-07 11:17 UTC (History)
3 users (show)

See Also:


Attachments
Error message from rng with Core Update 177 Testing (42.74 KB, image/png)
2023-07-28 10:32 UTC, Adolf Belka
Details
Error message re rngd symlink after fix applied (42.58 KB, image/png)
2023-07-29 07:28 UTC, Adolf Belka
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Adolf Belka 2023-07-28 10:32:22 UTC
Created attachment 1229 [details]
Error message from rng with Core Update 177 Testing

Back in CU174 when rngd-tools was moved to an addon the existing files

/usr/sbin/rngd
/usr/bin/rngtest

were not removed from users system by the upgrade script.

Therefore everyone still had rngd running on their system linked to the old openssl library.

With CU177 Testing openssl-1.1.1 is removed and now the fact that rngd is still present becomes visible with the attached failure message.

Anyone who has installed rng-tools as an addon will not see this error message.
If rng-tools has been installed and removed then those old rng files will be removed.
If rng-tools has been installed and is present for CU177 Testing there will also be no problem as in the Core Update when Openssl was changed to 3.x, rng-tools was updated and will therefore have the new library linked in.

The old files need to be removed from users systems but if they have the rng-tools addon installed then it needs to be updated and shipped so that those users don't lose their rng files.
Comment 1 Michael Tremer 2023-07-28 10:34:07 UTC
*** Bug 13196 has been marked as a duplicate of this bug. ***
Comment 2 Michael Tremer 2023-07-28 17:23:04 UTC
These binaries (and other scripts) will now be properly removed from all systems that don't have the add-on installed:

> https://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=8ffe9b67de2fad230ea28200cd5c5b79d586c793
Comment 3 Adolf Belka 2023-07-29 07:28:45 UTC
Created attachment 1230 [details]
Error message re rngd symlink after fix applied

I tested out doing an upgrade to CU177 Testing with the latest nightly dated 2023-07-28 19:48

/usr/sbin/rngd and /usr/bin/rngtest were removed but after reboot I got the message shown in the attachment.

That symlink should also have been removed by the patch from @arne but it appears to not have been for some reason.
Comment 5 Adolf Belka 2023-07-29 16:22:46 UTC
Update patch has been merged into Core Update 177 Testing
Comment 6 Adolf Belka 2023-07-29 16:32:11 UTC
Tested an update from CU176 to CU177 Testing master/d95a414c and the reboot has no fail messages at all now.

Fix confirmed working.
Comment 7 Jon 2023-07-30 19:29:33 UTC
I see this error in the message log:

Jul 30 13:51:53 ipfireAPU kernel: <27>udevd[696]: failed to execute '/etc/rc.d/init.d/rngd' '/etc/rc.d/init.d/rngd udev-event': No such file or directory


Tested on:
APU4D4
IPFire 2.27 (x86_64) - Core-Update 177 Development Build: master/d95a414c

If this is not related let me know and I will open a new bug
Comment 8 Michael Tremer 2023-07-31 13:48:36 UTC
> https://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=91443f923429d41c79a850295796ccaf1cd8ec4b

Thank you for the report.

It is somewhat related, and I removed the rules file entirely from all systems.