On Wednesday, April 3, 2002, at 05:48 , Bruno Figueira wrote:
[..]
>
> I guess that from this point you can improve your scripts. A socket
> connection is just an interface between two scripts/applications. You'll
> have to build your protocols above this "layer" so that one side is making
> resquets and and other is providing the answers. That's a client/server
> application.
[..]
good Point and it should be underlined - getting the socket
connection to work is one thing - getting a protocol specification
for what gets PASSED on that connection is a totatlly differnt
ballyWick all together....
> You actually don't need to use a client a this time. Certainly you can,
> but,
> to make this simpler, just telnet to the server in that port (telnet
> 192.168.1.120 9500) and issue commands. Their output will return to you.
> Pretty unsafe...
p1: in general we agree that 'telnet' connections are subSafe.
p2: but minor nit here:
just a reminder:
http://www.cis.ohio-state.edu/cgi-bin/rfc/rfc1918.html
the 192.168.0.0 IP address space is 'reserved' and hence not
on the 'internet' - so your worst threat here is that someone
inside of your own 'NAT' "group" will mis use your code.
ciao
drieux
---
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
