Gnus development mailing list
 help / color / mirror / Atom feed
From: Karl Kleinpaste <karl@jprc.com>
Subject: Re: Connecting through rlogin (ssh)
Date: 04 Nov 1998 11:13:18 -500	[thread overview]
Message-ID: <vxkiugva129.fsf@pocari-sweat.jprc.com> (raw)
In-Reply-To: Andy Eskilsson's message of "04 Nov 1998 12:36:10 +0100"

I think this is a type of problem that should be solved outside Gnus,
because it's not a Gnus-specific sort of problem.  Fortunately, ssh
already provides exactly what you need:

ssh -q -f -x -L8080:real.news.server:119 your.login.host sleep 100000000

In this contrived example, the result is that connections to
"localhost" at port 8080 will be sent to "your.login.host," where you
have normal shell access, whereupon the server side of ssh will
forward the connection to "real.news.server" on port 119.

Add "-g" to make the forwarded port on your own system into a
promiscuous one, accessible by any other host.  By default, port
forwarding works on "localhost" only.  Beware of this becoming known
and accessible to outsiders, or you will become very...popular.

Once you've set up the forwarded port with ssh, then all you need in
your select method is:

	(nntp "localhost" (nntp-port-number 8080))

We use this at JPRC to support a suck-feed into our news server from
CMU CS.  (And I don't admit to which port or host have the promiscuous
port for the aforementioned "popularity" reason.)  That's why I think
this is a problem to be solved outside Gnus, because I need it both
for direct Gnus access to certain groups available at CMU CS, while
simultaneously wanting the identical capability for the sake of our
newsfeed.  One ssh invocation solves both problems.

--karl


      parent reply	other threads:[~1998-11-04 16:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-11-04 11:36 Andy Eskilsson
1998-11-04 12:34 ` Jan Vroonhof
1998-11-04 12:38 ` Andy Eskilsson
1998-11-04 12:42   ` Andy Eskilsson
1998-11-04 15:35 ` Randal Schwartz
1998-11-04 16:13 ` Karl Kleinpaste [this message]

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=vxkiugva129.fsf@pocari-sweat.jprc.com \
    --to=karl@jprc.com \
    /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).