Hello, 

I don't know if this is a sensitive subject, but I'm trying to implement
security on the network, and I'm currently using a mix of socks5 and ip
masq.  Obviously socks will not work without sockified clients (under
windows that isn't true, as they have a winsock plugin), but for the
services that could use both socks or ipmasq, the question becomes which
to chose.  I've come up with some pros and cons, and i'm looking for
peoples thoughts.

socks (version5) pros:
can use advanced authentication (login/kerberos) for access.
more sophisticated logging.
doesn't need dns resolution on the clients side.

ipmasq pros:
presumably more services supported (as clients don't have to be coded for it)
done in the kernel so is faster?
actively supported and promoted (NEC states they don't care much about
the reference implementation).

i would appreciate people adding to and challenging this list.. unless
that this isn't the appropiate forum for this question.

Thanks,

Ken



_______________________________________________
Masq maillist  -  [EMAIL PROTECTED]
http://tiffany.indyramp.com/mailman/listinfo/masq
Admin requests can be handled by web (above) or [EMAIL PROTECTED]

Reply via email to