Hi!
I'm using yesterday's git checkout. Routing of the requests to our own RADIUS and germany's DFN Radius server is working OK!
Questions: ==========
* Currently, radsecproxy is running as root. Is that necessary? It's not binding to any privileged ports.
* Can radsecproxy run chrooted?
* during our 2 days of operation, it crashed three times - which is why I compiled the lasted version manually instead of using Ubuntu's packages:
Jul 5 14:51:43 radius-ext kernel: [5611.904760] radsecproxy[2710]: segfault at d8 ip 00007f0717424518 sp 00007f07183e4e20 error 6 in libc-2.23.so[7f071733c000+1c0000] Jul 6 09:28:46 radius-ext kernel: [72633.333687] radsecproxy[21034]: segfault at d8 ip 00007f5c647d8518 sp 00007f5c65798e30 error 6 in libc-2.23.so[7f5c646f0000+1c0000] Jul 6 12:15:19 radius-ext kernel: [82626.748886] radsecproxy[120425]: segfault at d8 ip 00007f1267ec5518 sp 00007f1268e3bd50 error 6 in libc-2.23.so[7f1267ddd000+1c0000]
How do I debug this; is it dumping cores even when running as root?
Hi,
On 6 Jul 2017, at 14:16, Ralf Hildebrandt Ralf.Hildebrandt@charite.de wrote:
Hi!
I'm using yesterday's git checkout. Routing of the requests to our own RADIUS and germany's DFN Radius server is working OK!
Questions:
- Currently, radsecproxy is running as root.
Is that necessary?
No, there is no need to run radsecproxy as root, this is not recommended.
You can run radsecproxy as any user.
It's not binding to any privileged ports.
Can radsecproxy run chrooted?
during our 2 days of operation, it crashed three times - which is
why I compiled the lasted version manually instead of using Ubuntu's packages:
Jul 5 14:51:43 radius-ext kernel: [5611.904760] radsecproxy[2710]: segfault at d8 ip 00007f0717424518 sp 00007f07183e4e20 error 6 in libc-2.23.so[7f071733c000+1c0000] Jul 6 09:28:46 radius-ext kernel: [72633.333687] radsecproxy[21034]: segfault at d8 ip 00007f5c647d8518 sp 00007f5c65798e30 error 6 in libc-2.23.so[7f5c646f0000+1c0000] Jul 6 12:15:19 radius-ext kernel: [82626.748886] radsecproxy[120425]: segfault at d8 ip 00007f1267ec5518 sp 00007f1268e3bd50 error 6 in libc-2.23.so[7f1267ddd000+1c0000]
How do I debug this; is it dumping cores even when running as root?
-- Ralf Hildebrandt Charite Universitätsmedizin Berlin ralf.hildebrandt@charite.de Campus Benjamin Franklin https://www.charite.de Hindenburgdamm 30, 12203 Berlin Geschäftsbereich IT, Abt. Netzwerk fon: +49-30-450.570.155 _______________________________________________ radsecproxy mailing list radsecproxy@lists.nordu.net https://lists.nordu.net/listinfo/radsecproxy
Mit freundlichen Grüßen/Best regards Ralf Paffrath -- Verein zur Förderung eines Deutschen Forschungsnetzes e.V. Alexanderplatz 1, D - 10178 Berlin
eduroam Beratung: Tel.: 030 88 42 99 91 21 eduroam technischer Support: Tel.: 030 88 42 99 91 20
email:eduroam@dfn.de
Fax: 030 88 42 99 370 http://www.dfn.de
Vorstand: Prof. Dr. Hans-Joachim Bungartz (Vorsitzender), Dr. Ulrike Gutheil, Dr. Rainer Bockholt Geschäftsführung: Dr. Christian Grimm, Jochem Pattloch
- Currently, radsecproxy is running as root. Is that necessary? It's not binding to any privileged ports.
I blame the packaging. Running as unprivileged user now...
Ralf Hildebrandt Ralf.Hildebrandt@charite.de wrote Thu, 6 Jul 2017 14:16:30 +0200:
- Can radsecproxy run chrooted?
As long as it can read its configuration file and write to a potential log file, it should work.
-
Linus Nordberg -
Ralf Hildebrandt -
Ralf Paffrath