Something about socksifying the xpilot client

The following is for Unix.
Win versions are also available, but i don't know anything at all about Micro$oft in principle :-)
Bucko mentioned being in investigations about this)

So far i just do:

• Local.config:
  >       DEFS_OTHER = -DSOCKS 
  >       EXTRALIB = -L/amd/lib/ -lsocks5 [...]
                        ^^ certainly our local stuff
  common/version.h.msub:
  >         #include "/amd/paket/socks5/include/socks.h"
  

  I compiled/installed socks5 here once but the server itself was already runing before.

  For the interested:
  (you might need to compile the library libsocks5.a yourself?
  Means it might not be installed, as not being needed after compiling the standard socksified programs like rtelnet, rftp etc )
  As it might not be very clear how to start compiling in the autoconfigured package, here my options:
  

  > ./configure --with-libconffile=/com/share/etc/libsocks5.conf \
  >  --with-srvconffile=/com/share/etc/socks.conf \
  >  --with-default-server=iris4.faw.uni-ulm.de \
  >  --prefix=/amd/paket/socks5-v1.0r7
  

  again: local paths, but in principle you see:
  - you have to know about the firewallhost
  - you need the locations of the socks5 config files - and acces to it (or at least copies)
  

• Another way: 'runsocks xpilot [...]'
  runsocks being a shellscript preloading libsocks5_sh.so and thus substituting the standard socket librarycalls.
  But you can't use this `shared libo' for linking against the xpilot binary! Thus the strange name...

  'runsocks' is also in the socks5 package. If not installed you might want to compile it yourself also.
  You can use it for any (non-suid-root etc) binary and so legally get through the firewall. (Perhaps there is a paranoid socks-server option against this, though?)

If you have probs/questions etc, don't hesitate to contact me.

ps: I always tend to complain other players to death about lag&co...
But beware: if your firewall has too few memory (as ours used to have long time) or has other jobs to do (www server etc.) [ as our has to ] - then believe me, you'll notice! :-)

ps2: Note that you can't socksify the server
(you can, it will happily contact the meta, but outerspace can't connect through your firewall :)