Package: freeradius Version: 1.1.3-3 Hi,
It's currently impossible to get the RADIUS client software from the FreeRADIUS distribution without getting the server, which opens a network port, which is obviously bad for security when you just wanted a client, and if you disable the server you have to maintain a heap of needless software on the system and a conffile change, yadda yadda yadda. It's just wrong (against the spirit of the packaging system and the practice of every other client-server software package in Debian). The following binaries should be in a package called freeradius-client or something like that: /usr/bin/radclient /usr/bin/radeapclient /usr/bin/radtest They are all generic RADIUS client software that doesn't depend on a FreeRADIUS server in particular, and they don't depend on a RADIUS server on localhost either. The other /usr/bin binaries from the current freeradius package could also easily be split out into a separate package, let's say freeradius-utils. But most of them are inherently tied to the FreeRADIUS server, so I won't complain if they stay. Yet, the smbencrypt binary is a complete mystery to me - why in the heaven's name is this a user-runnable binary in the RADIUS server package? There's a number of other things that can generate the LM/NT password hashes, such as a trivial implementation of libcrypt-smbhash-perl... In any case - after the clients are split out, the freeradius package can still depend on the new package(s), so no functionality would be lost for the users. Please fix this. TIA. -- 2. That which causes joy or happiness. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]