From: "Alex Bennee" <alex@bennee.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Allowing CVS, RCP & SCP
Date: Thu, 04 Jul 2002 15:04:09 +0000 [thread overview]
Message-ID: <marc-lartc-102579506826916@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102578552518735@msgid-missing>
bert hubert said:
> On Thu, Jul 04, 2002 at 02:01:07PM +0100, Alex Bennee wrote:
>> A. Peter Mee said:
>> > <snip>
>> > Could someone give me some pointers to achieving stable cvs and rcp
>> > access through a fairly restrictive firewall.
>> > <snip>
>>
>> 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.
>
> CVS 'pserver' lives on port 2401. Use netstat -an to see which ports
> have LISTENing sockets, and open up those ports.
Quite correct of course.
There are numerous ways of accessing remote CVS repositries (see
http://www.cvshome.org/docs/manual/cvs_2.html#SEC26). CVS over ssh seems to
be the preffered method of large development communities (sourceforge and
savanah at least). Once you've got ssh working you don't need to do any
additional (network level) work to get CVS running. I would generally be
wary of just opening up ports that are listening without being aware of the
security implications of using that protocol. The CVS documentation suggests
Kerboros over pserver for security. ssh works just as well (the documention
only refers to rsh which isecure but replaceable by ssh).
Alex
www.bennee.com/~alex/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-07-04 15:04 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
2002-07-04 14:34 ` bert hubert
2002-07-04 15:04 ` Alex Bennee [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=marc-lartc-102579506826916@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.