-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tmpfolder can't be used on Ubuntu 22.04 due PrivateTmp Systemd option enabled by default #5066
Comments
@megothub which version are you using? |
FreeRADIUS Version 3.0.26 from Ubuntu repos |
actually, changing /etc/init.d/freeradius is not enough. Checking systemd script. /var/run/freeradius/tmp folder was not created while starting freeradius |
that's the article I've used to configure EAP I've found another issue linked to mine |
Creating a directory in /var/run/freeradius is best done with a systemd override. Try creating /etc/systemd/system/freeradius.service.d/override.conf containing
The last option will leave the directory available when the FreeRADIUS service is stopped - without that systemd tidies up runtime directories. |
What type of defect/bug is this?
Crash or memory corruption (segv, abort, etc...)
How can the issue be reproduced?
OS: Ubuntu 22.04
freeradius to be started as service
no issues if started with freeradius -X
Issue itself: tmpdir can't be used
(E.g. in case if EAP configuration with requirement to check certificates)
described in
/etc/freeradius.old/3.0/mods-enabled/eap
When directory created and configured as described above freeradius keeps failing with the following error (/var/log/syslog)
Jun 17 15:28:51 vm freeradius[233969]: tls: Failed changing permissions on /tmp/radiusd: No such file or directory
After investigation it is clear that default systemd script:
/lib/systemd/system/freeradius.service
has the following related setting causes issues:
When changed to false freeradius starts seeing that tmp folder.
It is expected behavior.
Now, to solve the issue for anyone who will try to enable tmp folder on Ubuntu systems I propose the following solution
a) change /etc/init.d/freeradius script as follows
b) change description and location of the tmp folder in the following conf files
/etc/freeradius.old/3.0/mods-available/eap
/etc/freeradius.old/3.0/sites-available/tls
to highlight that /var/run/freeradius/tmp should be used
Log output from the FreeRADIUS daemon
not applicable. Check description of the issue as freeradius -X doesn't show any issue due issue with start script.
Relevant log output from client utilities
not applicable. Check description of the issue that contains output from /var/log/syslog
Backtrace from LLDB or GDB
No response
The text was updated successfully, but these errors were encountered: