Actually my language was a bit woolly. The problem hasn't recurred so far, but I still think the configuration file looks bad because of the wildcard. We seem to have wandered away from security so anyone interested had better contact me offline. Bob On Mon, 3 Oct 2005, Christian Boltz wrote:
Hello,
Am Montag, 3. Oktober 2005 16:01 schrieb Bob Vickers: [...]
SuSE then released an updated package xinetd-2.3.13-45.2 which claimed to fix the problem, however it still looks bad to me.
Did you restart xinetd after installing the update?
[Fullquote moved to /dev/null]
Regards,
Christian Boltz -- Eine Windows-Kiste als Tor zu Welt - das wäre ja so, als würde man einen Blinden, einen Lahmen und einen Tauben als Wachschutz einsetzen. [Matthias Houdek in suse-linux]
-- Check the headers for your unsubscription address For additional commands, e-mail: suse-security-help@suse.com Security-related bug reports go to security@suse.de, not here
============================================================== Bob Vickers R.Vickers@cs.rhul.ac.uk Dept of Computer Science, Royal Holloway, University of London WWW: http://www.cs.rhul.ac.uk/home/bobv Phone: +44 1784 443691