If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Configure ssh://hg.mozilla.org to run on alternate port(s)

RESOLVED INCOMPLETE

Status

Developer Services
General
RESOLVED INCOMPLETE
5 years ago
3 years ago

People

(Reporter: kaie, Assigned: fox2mike)

Tracking

Details

(Reporter)

Description

5 years ago
I'm at a hotel that blocks outgoing connections on port 22, which makes it difficult to get work done.

I suggest to configure the ssh daemon on hg.mozilla.org to support alternative ports.
This is as simple as editing /etc/ssh/sshd_config and in addition to the existing "Port 22" line, add additional lines with additional port numbers.

I suggest to support
Port 21
Port 2222
Assignee: server-ops → server-ops-devservices
Component: Server Operations → Server Operations: Developer Services
QA Contact: jdow → shyam
(Reporter)

Comment 1

5 years ago
Just wanted to add: NOT urgent.

I was able to work around it using a VPN.
(Assignee)

Comment 2

5 years ago
(In reply to Kai Engert (:kaie) from comment #1)
> Just wanted to add: NOT urgent.
> 
> I was able to work around it using a VPN.

Kai, I think we already use 222 and 2222 for other services (hg.ecmascript.org for example). I'm not really sure we should open up more ports, CC Security Assurance for their thoughts on this as well. Working around with the VPN is a great option (compared to opening up more ports, IMHO).
(Assignee)

Comment 3

5 years ago
I don't think we'd want to open up more ports at this point. If needed we can look into it in the future.
Assignee: server-ops-devservices → shyam
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → INCOMPLETE
Component: Server Operations: Developer Services → General
Product: mozilla.org → Developer Services
You need to log in before you can comment on or make changes to this bug.