From: Stainless Steel Rat <ratinox@peorth.gweep.net>
Subject: Re: tunneling nntp connection
Date: 31 Oct 2000 10:05:41 -0500 [thread overview]
Message-ID: <m38zr5qce2.fsf@peorth.gweep.net> (raw)
In-Reply-To: Peter Makholm's message of "Tue, 31 Oct 2000 14:14:35 GMT"
* Peter Makholm <peter@makholm.net> on Tue, 31 Oct 2000
| Why nc instead of telnet? Any reasons except that it is a more minimal
| solution to the problem (which is a quite good reason if you ask me)
No stdin EOF problems. It stays running until the network side closes.
It can pass arbitrary 8-bit data. No diagnostic output. Is smaller. Is
faster. Lots of other reasons.
--
Rat <ratinox@peorth.gweep.net> \ When not in use, Happy Fun Ball should be
Minion of Nathan - Nathan says Hi! \ returned to its special container and
PGP Key: at a key server near you! \ kept under refrigeration.
next prev parent reply other threads:[~2000-10-31 15:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-31 13:28 Paul Stevenson
2000-10-31 13:51 ` Karl Kleinpaste
2000-10-31 14:50 ` Randal L. Schwartz
2000-10-31 15:03 ` Paul Stevenson
2000-10-31 13:51 ` Stainless Steel Rat
2000-10-31 14:14 ` Peter Makholm
2000-10-31 15:05 ` Stainless Steel Rat [this message]
2000-10-31 14:44 ` Jake Colman
2000-10-31 15:07 ` Paul Stevenson
2000-10-31 15:21 ` Peter Makholm
2000-10-31 16:15 ` Paul Stevenson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m38zr5qce2.fsf@peorth.gweep.net \
--to=ratinox@peorth.gweep.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).