- Package:
- rtc.debian.org
- Source:
- rtc.debian.org
- Submitter:
- Daniel Pocock
- Date:
- 2015-11-22 11:18:04 UTC
- Severity:
- wishlist
package: rtc.debian.org severity: wishlist We need to get radcli into Debian[1], backport it and have it deployed on vogler Future versions of reSIProcate should use this instead of freeradius-client by default. It provides better logging of errors and improved stability. Upstream is more active. Discussed in DSA RT ticket #6015, send email to rt@rt.debian.org with subject prefix [rt.debian.org #6015] 1. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802684
Now that we found a workaround for making freeradius-client work, it is not as urgent to change to radcli, but it is still desirable because it has more upstream support and better syslog messages about problems. Process: Wait for upstream feedback on these two issues: https://github.com/radcli/radcli/issues/3 https://github.com/radcli/radcli/issues/5 Review packaging if necessary based on that feedback. https://packages.qa.debian.org/r/radcli.html Review the first installation config file migration issue for change from freeeradius-client to radcli: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805771 This should be dealt with and the radcli package installed and we should verify that config files appear to have the correct settings before a newer version of reSIProcate comes through jessie-backports with a dependency on radcli If manual config file migration is the outcome of #805771, then copy the necessary changes from /etc/radiusclient/* to /etc/radcli Finally, resiprocate linked with radcli should be put into jessie-backports and installed onto vogler.debian.org