From: "Alex Bennee" <alex@bennee.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Allowing CVS, RCP & SCP
Date: Thu, 04 Jul 2002 13:01:07 +0000 [thread overview]
Message-ID: <marc-lartc-102578768520352@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102578552518735@msgid-missing>
A. Peter Mee said:
> Hi all,
>
> Could someone give me some pointers to achieving stable cvs and rcp
> access through a fairly restrictive firewall. I'm using a 2.4.18
> kernel which defaults to dropping everthing, then punching holes where
> needed and SNATting the internal network. Single-socket protocols
> (http, smtp, pop3) do currently function correctly through the firewall
> so I'm assuming the cvs and rcp/scp protocols are not single-socket.
> The ftp and irc protocols also function correctly through the firewall.
ssh is a single socket protocol. If you can ssh through your firewall then
you can use scp. You can even tunnel other ports over the single ssh
connection (e.g. X).
CVS isn't a network protocol. You generally run it using remote shell tools,
in the CVS manual it allows you to specifify how with the CVS_RSH evrionment
variable.
r* tools are bad. Do you need them?
> If something more specific about my configuration is needed, I'll be
> happy to oblige. ;-)
>
> TIA
>
> Cheers,
>
> Pete Mee
>
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Alex
www.bennee.com/~alex/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-07-04 13:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-04 11:40 [LARTC] Allowing CVS, RCP & SCP A. Peter Mee
2002-07-04 13:01 ` Alex Bennee [this message]
2002-07-04 14:34 ` bert hubert
2002-07-04 15:04 ` Alex Bennee
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=marc-lartc-102578768520352@msgid-missing \
--to=alex@bennee.com \
--cc=lartc@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.