Sure, I will do that. I have started asking them and the response I
get is (in India) "Policies set by the parent company/HQ and has been
handed down to us". I have not yet got a straight to the point answer
yet! The other common answer is, "The firewall is not in our
administra
Hi,
On 7/18/07, Richard Stallman <[EMAIL PROTECTED]> wrote:
You may be right, but we still need to know what the sysadmins say
when they are _asked_ to allow these connections.
Dhruva, would you please ask them?
Sure, I will do that. I have started asking them and the response I
get is (in In
> Please try asking your sysadmins and tell us what they say.
> We need to know!
Most likely the firewall doesn't block 2401 specifically, instead it only
lets through a few specific ports such as 80 and 443 and blocks
everything else.
You may be right, but we still need to kn
> In my current work
> place, we use CVS internally. Maybe, that is the reason for preventing
> the that port for external access. From what little I know, a version
> control system is another form of easy means to deposit data
> (versioned). May be, there exists a paranoid fea
In my current work
place, we use CVS internally. Maybe, that is the reason for preventing
the that port for external access. From what little I know, a version
control system is another form of easy means to deposit data
(versioned). May be, there exists a paranoid feaar that so
Hello,
Thank you very much for a detailed explaination of the comlexities
involved in providng such a service.
I have no direct way to find out the reason due to which CVS port
(2401) is blocked. The earlier companies I worked for blocked that as
part of blocking a whole lot of ports. I could not
On Tue, Jul 10, 2007 at 11:33:44AM +0530, dhruva wrote:
> Hi,
> I went through the complete document and suggested methods (tor did
> not work either). For port 443 approach, the catch is here.
>
> -- Part of the document from the link you had sent
> Note: we implemented that method, without
The have enabled 443 as an alternative to 22. Port 22 is used only by
project members with commit access. It does not really help people
like me (involved in the emacs project but not part of the core).
Maybe we need to make pserver available on port 443 on some IP.
Savannah people, is
Hi,
I went through the complete document and suggested methods (tor did
not work either). For port 443 approach, the catch is here.
-- Part of the document from the link you had sent
Note: we implemented that method, without warranty, for project member
SSH access only - not anonymous access
