[ale] piping to a port

[Chris Fowler]

You make valid points.  I enjoy writing the code for educational purposes.  When I see an opp, I usually might try to reinvent the wheel.  Reinventing the wheel gave us Linux.  Linus used minix code and sun documentation to determine what the POSIX system calls and library calls were supposed to do.  He never had a standard.  I have an old one but rarely look at it.



-----Original Message-----
From: Joseph Andrew Knapka [mailto:jknapka at earthlink.net]
To: ale at ale.org
Sent: Thursday, August 16, 2001 6:59 AM
To: Chris Fowler
Cc: 'Jonathan Rickman'; Tommie M. Jones; ale at ale.org
Subject: Re: [ale] piping to a port



> Chris Fowler wrote:
> 
> Actually.  It whould not bee too difficult to do this using a little C
> code.  Try Beej's Socket Programming guide to get started.


But it would be a whole lot easier to just use the existing,
well-known tool for doing this task. Most people would rather
have a root canal than write any code at all, and even those of
us who genuinely enjoy writing code would prefer not to
reinvent the wheel :-)


- Joe


> -----Original Message-----
> From: Jonathan Rickman [mailto:jonathan at xcorps.net]
> Sent: Thursday, August 16, 2001 10:35 AM
> To: Tommie M. Jones
> Cc: ale at ale.org
> Subject: Re: [ale] piping to a port
> 
> On Thu, 16 Aug 2001, Tommie M. Jones wrote:
> 
> > Is there a simple way to pipe to a port from the command line in
> linux.
> > I have a file that I would like to redirect the tail to port 8002 so
> I can
> > see it from any machine on the LAN for debugging purposes.
> 
> netcat is pretty good at stuff like that.
> 
> http://xcorps.net/ftp/pub/tools/scanners/nc110.tgz
> 
> --
> Jonathan Rickman
> X Corps Security
> http://www.xcorps.net
> 
> --
> To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" in
> message body.


-- 
# Joe Knapka
# "You know how many remote castles there are along the
#Â  gorges? You can't MOVE for remote castles!" - Lu Tze re. Uberwald
# 2nd Lbl A + 1 = 2nd Pause 2nd Prt A