SSH for the SPEEDE Server

Frequently Asked Questions

Does the SPEEDE server offer secure ftp using SSH protocol?

Yes. The SPEEDE server uses scp2 (secure copy using SSH protocol) to send documents securely. The SPEEDE server also allows for institutions to send to it via secure ftp using SSH protocol (hereafter referred to in this document as ‘sftp’).

What SSH software does the SPEEDE server use?

The SPEEDE server is currently using SSHcomm's SSH-1.99-3.2.3 SSH Secure Shell.

What do I need to do to set up having the SPEEDE server send via sftp to me?

The SPEEDE server administrators need to connect to your server to complete an initial handshake, which involves uploading our public key to your server. Thus, at the very basic level, you need to have an ftp server that is running a version of SSH. You also need to send us a username and password, along with the host name or IP address. We will then upload our public key and confirm that we can connect to your ftp server securely using public key authentication. Once this is confirmed, our system is ready to send your electronic documents to you via scp2.

Can the SPEEDE server send via sftp without public key authentication?

No, the SPEEDE server needs to use public key authentication when sending documents. Using a password is an interactive step (waiting for a prompt on the screen) whereas the SPEEDE server sends via sftp in batch format.

Your service offers 'put' and 'append' using regular ftp. Do you offer the same choices through sftp?

The answer to this is: Yes and No. As in – yes, we offer both of these options for sftp, but no, the append option works a little differently than in the regular ftp delivery. As you may know, in regular ftp – we use ‘put’ to put a uniquely named document (with a two digit counter built in to the document name) and we use ‘append’ to append to an existing document (if the document does not already exist, the append command creates it). Using sftp – if you choose the ‘put’ option, we will secure copy the document with the counter imbedded in the name. But if you choose to append, we will put (secure copy does not append) the document with the same name every time. Thus, it is important for you to process each document before it is overwritten. (It is best to have the SPEEDE server send once a day in this case, allowing you to process each incoming document, and remove it from your receiving ftp server before the next document is put.)

What do I need to do to be able to send to the SPEEDE server via sftp?

The answer to this question assumes that you already have a regular ftp account with the SPEEDE server. Basically, you need only inform us (at regist@ediserver.reg.utexas.edu) that you are going to be sending via sftp. We will then change your regular ftp account to a sftp account. You may choose whether you prefer to connect to the SPEEDE server using a password or public key authentication. If you choose public key authentication, then we will need your public key installed in your sftp directory on the SPEEDE server.

I am using OpenSSH. Is that compatible with the SSH program the SPEEDE server is using?

Yes, the two systems are compatible. It requires only a conversion of our public key from SSHcomm format to OpenSSH format on your sftp server.

Where do I get SSH?

You can find OpenSSH at www.openssh.com and SSHComm’s SSH at www.ssh.com.

How do I install SSH?

Please see www.ssh.com/support/downloads/ for downloading instructions of SSHComm’s SSH, and http://www.openssh.com/faq.html#1.1 for information about OpenSSH.