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

Allow FTP connections to preproduction-stage.build.mozilla.org

RESOLVED INVALID

Status

Infrastructure & Operations
RelOps
RESOLVED INVALID
7 years ago
4 years ago

People

(Reporter: rail, Unassigned)

Tracking

Details

(Reporter)

Description

7 years ago
This server is going to serve preproduction builds via FTP. Could you please unblock FTP protocol in firewall? At the moment connections are being refused by the server and there is no local firewall set on the machine.
You want ftp access from the world as a whole to preproduction-stage.b.m.o?

Short answer is 'no'. 

Long answer is we can do a security review on that host, or more likely, find a way to move files onto ftp.m.o or a similar host that is already exposed to the world.
(Reporter)

Comment 2

7 years ago
(In reply to comment #1)
> You want ftp access from the world as a whole to preproduction-stage.b.m.o?

I should have been more verbose, sorry. FTP access from build-vpn would be quite enough. Does this require security overview?
No, internal use is fine.

There shouldn't be any access restrictions from the build-vpn concentrator to that machine. nmapping that machine shows ports 20 and 21 to be closed, which makes me think it's not running an ftp daemon at all.

I can't log in to the host to look, however.
(Reporter)

Comment 4

7 years ago
My fault, a typo in hostname while trying to access the host. :/ I also stopped vsftpd after trying to access it. Works as expected. Sorry for the noise.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → INVALID
Component: Server Operations: RelEng → RelOps
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.