Closed Bug 741714 Opened 14 years ago Closed 13 years ago

Allow access to IM protocols on Mozilla Guest

Categories

(Infrastructure & Operations Graveyard :: NetOps: DC ACL Request, task)

All
Other
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mrbkap, Assigned: ravi)

Details

Currently, Mozilla Guest blocks access to ports that are used by various IM clients. During a visit to the Paris office from one of the IT people, it was indicated the reason these ports were blocked was that nobody had asked to use them and that it's a simple matter to unblock them. The two clients currently blocked (that I know about) are MSN and Jabber. Thanks.
Looks like jabber uses the following ports: 5222/TCP 5223/TCP (old SSL/TLS) MSN uses a lot of ports ( http://support.microsoft.com/kb/927847 ) and I'm not inclined to open all of them, but will investigate the minimum needed for basic chat functionality. IRC is Mozilla's primary method for chat and all the common IRC ports are open. I question why we would need to offer additional services.
Assignee: network-operations → ravi
Group: infra
Severity: minor → enhancement
Status: NEW → ASSIGNED
(In reply to Ravi Pina [:ravi] from comment #1) > IRC is Mozilla's primary method for chat and all the common IRC ports are > open. I question why we would need to offer additional services. So, especially with the new Mozilla Spaces stuff, we're hoping to attract more community members to come hang out and help out with Mozilla stuff. In order to be as welcoming as possible, I think it's important that contributors who come to Mozilla are able to work and communicate over protocols, even if we don't use them internally. That being said, I think that chat functionality is all that is needed out of the MSN messaging stuff.
Group: infra
We also have a community member that needs the port 18022 to be open because she can't access her community server from our office, could you open this port please? Thanks
According to bug 709199, some users also need port 119/tcp for newsgroups
Blocks: 709199
No longer blocks: 709199
Port tcp 5228 is used by google services on Android "for syncing your Gmail, Calendar events, contacts, for backing up your settings, and so on", it would be great to have it opened.
Below is a list of all ports that are permitted which is all we are inclined to open at this moment. This list has been sufficient for events and meetings over the last year. android-market (5228/tcp) bbb-desktopSharing (9123/tcp) cpudpencap (2746/udp) dns-tcp (53/tcp) dns-udp (53/udp) esp (protocol 50) fw1-rpc (259/udp) git (9418/tcp) http (80/tcp) https (443/tcp) imap4-ssl (585/tcp) imaps (993/tcp) ipsec-nat-t (4500/udp) ipsec-udp (10000/udp) ircd (6667/tcp) ircd-ssl (6697/tcp) ircd-ssl-alt (7070/tcp) ircd-w3c (6665/tcp) isakmp (500/udp) nntp (119/tcp) openvpn (1194/udp) pop3s (995/tcp) rtmp (1935/tcp) smtps (465/tcp) smtps-alt (587/tcp) ssh (22/tcp) svn (3690/tcp) xmpp-bosh (5280/tcp) xmpp-client (5222/tcp) xmpp-xfer (8010/tcp) xmpps-client (5223/tcp)
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Product: mozilla.org → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.