many thanks
YoYo
My home LAN is up. (In fact, I'm typing this on the Windows98 machine,
telnetted into the linux machine.)
Many thanks to everyone who offered help and advice. I'm sure I'll have
more questions as I continue along. (Next up: samba and IP masquerade.)
--
----YoYo------...@tezcat.com------------and stuff------
"...and there are plenty of people joining in to help Tiger Woods
find his tee shot." -Mike Tirico
Jim Kingdon
> telnetted into the linux machine.)
Cool!
> Many thanks to everyone who offered help and advice. I'm sure I'll have
> more questions as I continue along. (Next up: samba and IP masquerade.)
I've been becoming more of a SOCKS fan lately (it does some of the
same things as IP masquerading, although the details are quite
different, with a different set of capabilities and drawbacks). I
even helped a friend (a virtual friend in Russia, no less) set up
a SOCKS server, so I guess that sort of means that I know about SOCKS
firsthand rather than just by reading the web pages.
YoYo
>I've been becoming more of a SOCKS fan lately (it does some of the
>same things as IP masquerading, although the details are quite
>different, with a different set of capabilities and drawbacks). I
>even helped a friend (a virtual friend in Russia, no less) set up
>a SOCKS server, so I guess that sort of means that I know about SOCKS
>firsthand rather than just by reading the web pages.
Can you tell me some more about this? What can you do with SOCKS?
Jim Kingdon
Uh oh. I was afraid I would get in this kind of trouble when I posted
that :-).
The basic deal with SOCKS is that you first connect to the SOCKS
server, and tell it where you are connecting. So the server can be
configured to let through particular kinds of connections, to identify
users in various ways, and any number of policies. At first glance the
bit about the client needing to talk the SOCKS protocol looks scary -
it would seem that every client would need to get rewritten. But
things aren't quite that bad - SOCKS supplies a shared library that
you can make your programs use (using LD_PRELOAD or whatever it is
called) and so in many cases, you don't need to recompile anything.
So the strength is that you can configure in various security policies
(connect to certain hosts, connect to certain ports, Kerberos, &c),
and that certain kinds of attacks on the non-gateway systems just
vanish (e.g. teardrop). Weaknesses? Maybe harder to set up than
masquerading? That's probably a documentation issue as much as
anything, and I didn't find the SOCKS documentation too bad (but that
could just be me). There are surely other strengths and weaknesses
which I'm not mentioning or don't know about.
Anyway, I've gone on long enough. The SOCKS web page is
http://www.socks.nec.com/
YoYo
>> Can you tell me some more about this? What can you do with SOCKS?
>
>Uh oh. I was afraid I would get in this kind of trouble when I posted
>that :-).
>
>The basic deal with SOCKS is that you first connect to the SOCKS
[snip]
Thanks. I'll look into it.