Finally, this can be closed as everything works now. The file names problem above is a silly one: just needed to create /etc/freeradius in $chroot for the file names to be the same (I didn't)... Then, evidently, not ALL the files from /etc/freeradius are needed in /$chroot/etc/freeradius. But that's not a big problem to copy ALL of them.
Also mount --bind /dev to $chroot/dev, /var/run/freeradius to $chroot/var/run/freeradius and /var/log/freeradius to $chroot/var/log/freeradius And copied the openssl binary along with its libs into the $chroot (also all the freeradius libs). That's it! No static linking was needed, after all. Though I only implement EAP-TLS authentication, but the method seems to work. So it works, and I assume the freeradius documentation is not supposed to include explanations about a chroot? Just for some reason, FreeBSD version works fine with user=freerad group=freerad without a chroot... So I think the bug can be closed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1730362 Title: fails to start as user/group freerad (recommended!) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeradius/+bug/1730362/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
