FileTransferProtocol

UMIACS provides FTP services for transferring data to and from external collaborators. Since the FTP protocol is conducted entirely in plaintext, external users login to the service as anonymous, and internal users can access the file directories internally. Users will never authenticate over FTP with their UMIACS account. Please see SFTP for more information on a secure file transfer protocol.

Getting data from Collaborators

Collaborators can drop data for users into their FTP incoming file system, located from the FTP service at

ftp://ftp.umiacs.umd.edu/incoming/<username>/

FTP logins can write to this space to upload data, but cannot list the files they have placed there. Users can then access the data in their ftpincoming space from

• /fs/ftp/incoming/<username> from supported unix machines. Click here to see a visual guide.
• \\umiacs-webftp\ftp-umiacs\incoming\<username> - from supported windows machines. Click here to see a visual guide.

/fs is an automounted file system. This means it will mount other file systems on demand. Although the ftp directory may not be visible to an ls command while in fs, one can still cd into ftp.

Please move your data as soon as possible after it is left for you - files older than 15 days are subject to deletion as necessary.

Publishing data sets via FTP

This part of our FTP service is deprecated in favor of the UMIACS Object Store. Please see OBJbox.

Users can place data to be externally accessible in their public FTP space, which is located from the FTP service as

ftp://ftp.umiacs.umd.edu/pub/<username>/

To upload data to your public site, you can upload data to,

• /fs/ftp/pub/<username> from supported unix machines
• \\umiacs-webftp\ftp-umiacs\pub\<username> - from supported windows machines

Effects of tmpwatch

There is a configuration of tmpwatch[1] in place on our FTP service that will remove any files, regardless of owner or permissions, from any /fs/ftp/incoming/ directory that have not been accessed in 30 days.