From: Jochen H. <Joc...@Ha...> - 2007-03-17 15:57:27
|
>>>>> "MA" == Matthias Andree writes: MA> Well - Dante doesn't have run-time switches, it redirects all MA> the network-related functions to itself, MA> fetchmail has not means to circumvent SOCKS if linked against it. MA> Such run-time configuration would have to happen by means of socks.conf. >>>>> On Sat, 17 Mar 2007 15:18:02 +0100, >>>>> Michael Shuldman >>>>> (whose comments are cited below with " MS> "), >>>>> had this to say in article <200...@ba...> >>>>> in newsgroups gmane.network.socks.dante.general >>>>> concerning the subject of "Re: 2007-03-16 / how to tell socks enabled application to not go via the socks server" > Jochen Hayek wrote, >> But how can a socks enabled (compiled, linked, ...) application >> instruct the socks5 library to not go via the socks5 server >> other than by removing /etc/socks.conf ? MS> Maybe you could set the environmentvariable SOCKS_CONF. MS> What happens if you do "SOCKS_CONF=/dev/null application"? That does exactly what you and I expect. Thanks a lot! Now that we (the fetchmail community) know this, fetchmail can also get an internal putenv("SOCKS_CONF=/dev/null") somewhere around its SOCKSinit("fetchmail"); and than a command line switch (e.g. --socks_conf=/etc/socks.conf ) in order to change it back, so that somebody, who really wants to employ socks, actually makes use of it: putenv("SOCKS_CONF=/etc/socks.conf") But there are dozens of alternatives ... |