I am maintaining a web server designed to work in a secure environment: for instance, all logins are with SSH (which is like an encrypted Telnet) and file transfers have up until recently been done with SCP (like a secure FTP, also operating through a secure tunnel).
Unfortunately, I have had to relax this restriction the first time we published our website from GoLive, which seems only to be able to publish with insecure FTP (in addition to HTTP which I don't think is appropriate in our case).
By "insecure" I don't mean that we are not taking the normal precautions, such as having a "webadmin" account as an FTP login with a nontrivial password. The fact the username and password for the FTP session are not sent over a secure channel effectively invalidates the other security mechanisms that we are using.
Does anyone know of a way of getting GoLive to use the SCP file-copying protocol? Such as a free or commercial plug-in? Alternatively, how would such a "plug-in" be written, and might it be something as simple as a chat script to deliver the login information after creating an SSL tunnel? (Our publishing client also has Cygwin installed, so UNIX scripting would also be available to us.)
So far the only solution I can think of us for the GoLive "Publish" operation to publish to a folder on the local machine, then invoking an "rsync" (a file-tree copying program in Cygwin that uses SCP by default) to update our web server over the secure channel.
Is there anyone else in this forum that is maintaining a web server in an environment where FTP is not an option? Please write if you know of how to obtain (or write) a plug in for this and I promise to immortalize you in the FAQ that I will be able to write when we can finally turn our FTP server off again. This FAQ should be of substantial interest to anyone using GoLive to maintain a website on a high-security server.
Best regards,
Robert
Unfortunately, I have had to relax this restriction the first time we published our website from GoLive, which seems only to be able to publish with insecure FTP (in addition to HTTP which I don't think is appropriate in our case).
By "insecure" I don't mean that we are not taking the normal precautions, such as having a "webadmin" account as an FTP login with a nontrivial password. The fact the username and password for the FTP session are not sent over a secure channel effectively invalidates the other security mechanisms that we are using.
Does anyone know of a way of getting GoLive to use the SCP file-copying protocol? Such as a free or commercial plug-in? Alternatively, how would such a "plug-in" be written, and might it be something as simple as a chat script to deliver the login information after creating an SSL tunnel? (Our publishing client also has Cygwin installed, so UNIX scripting would also be available to us.)
So far the only solution I can think of us for the GoLive "Publish" operation to publish to a folder on the local machine, then invoking an "rsync" (a file-tree copying program in Cygwin that uses SCP by default) to update our web server over the secure channel.
Is there anyone else in this forum that is maintaining a web server in an environment where FTP is not an option? Please write if you know of how to obtain (or write) a plug in for this and I promise to immortalize you in the FAQ that I will be able to write when we can finally turn our FTP server off again. This FAQ should be of substantial interest to anyone using GoLive to maintain a website on a high-security server.
Best regards,
Robert
