This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: cvs read behind firewall?
- To: "Joe Buck" <jbuck at racerx dot synopsys dot com>
- Subject: Re: cvs read behind firewall?
- From: Christian Jönsson <chj at lin dot foa dot se>
- Date: Thu, 14 Dec 2000 19:09:23 +0100
- Cc: "gcc" <gcc at gcc dot gnu dot org>
- Organization: Sweden's Defence Research Est.
- References: <200012141737.JAA18997@racerx.synopsys.com>
Thanks for your comments. This is one way of achieving
teh objective, to access the GCC code repository from
behind a firewall. However, I suspect that my specific
problem perhaps could be resolved also by allowing
the sshd at gcc.gnu.org this read-only acces to the
machine. Perhaps this idea is a good idea only it's not
possible with today's ssh/sshd. Perhaps it is, but it's not
configured to allow it. I simply don't know.
Anyway, here's what happens when I try to slogin
at gcc.gnu.org, again, using a bash shell...
administrator@BOTTEN ~
$ slogin -P -l anoncvs gcc.gnu.org
Permission denied.
administrator@BOTTEN ~
an to an other host outside of the firewall...
administrator@BOTTEN ~
$ slogin -P -l cj merlin.isy.liu.se
Warning: Server lies about size of server public key: actual size is 767
bits vs
. announced 768.
Warning: This may be due to an old implementation of ssh.
cj@merlin.isy.liu.se's password:
administrator@BOTTEN ~
where I aborted the slogin...
So, in summary, I can ssh myself through the firewall, but not cvs read
gcc.gnu.org...
Cheers,
/ChJ
----- Original Message -----
From: "Joe Buck" <jbuck@racerx.synopsys.com>
To: "Christian Jönsson" <chj@lin.foa.se>
Cc: "gcc" <gcc@gcc.gnu.org>
Sent: Thursday, December 14, 2000 6:37 PM
Subject: Re: cvs read behind firewall?
> > Any help with getting cvs access through my firewall is greatly
appreciated.
>
> Ask the people who administer your firewall if they will open up port 2401
> only for connections to gcc.gnu.org. They may well agree to open up
> access to a trusted site, even if they are reluctant to open it up
> unconditionally.
>
>
>
>