In article <[EMAIL PROTECTED]> you wrote: > The point of a protocol-proxy is that you want to provide services to > the outside world, but you don't trust your server software to be robust > against protocol-level attacks (buffer overflows, primarily).
It is also the other way around. Clients which you cant trust to be stable enough. Typical example are web browsers which display ActiveX. > Since one > of the points of Debian is to fix bugs in software, that's not > particularly a direction that's interested anyone recently. This is not true for Organisations running Desktops by a commercial vendor and Firewalls based on Debian. > However, the tools are in place to build your own. Generically, any > protocol can be diverted to another program by the packet filtering > system; A small List can be found on http://www.freefire.org/, but it is not Debian specific. > Look at packages simpleproxy, stone, totd, squid, xfwp, and in fact > everything you get from an "apt-cache search proxy". ... and I may need to add some of these :) Greetings Bernd -- eckes privat - http://www.eckes.org/ Project Freefire - http://www.freefire.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
