[TAG] Linux FTP servers for uploads
Jay R. Ashworth
jra at baylink.com
Tue May 11 21:53:36 MSD 2004
On Tue, May 11, 2004 at 10:38:32AM +0530, Kapil Hari Paranjape wrote:
> On Mon, May 10, 2004 at 02:12:47PM -0400, Jay R. Ashworth wrote:
> > Alas, my client hasn't the pull. The data-originator end is
> > Conoco/Phillips; they have two standardized approaches to delivering it
> > ($LARGE_EXPENSIVE_ANNOYING_EDI_PROVIDER, and "we'll FTP it to your FTP
> > server"), and I think it unlikely that we'll be able to get them to
> > change, unless we're *really* lucky (yes, we *have* asked if they'll
> > contemplate setting up SCP).
>
> Here are some alternatives to "good old ftp" for pushing files to
> "incoming".
>
> 1. There is an ftp server that works with SSL. In Debian it is the
> ftpd-ssl package. This means that the session will be encrypted.
> You can even authenticate based on public key a la scp.
>
> 2. What about web based uploads? You create a web form which has
> a "file upload" entry. The user interface on most machines is quite
> straight forward---you type in (or use a file browser to select)
> the name of the file that you want to upload. The cgi that handles
> the form decides what to do with the file so that can be done *very*
> securely by writing a secure cgi script. HTTPS can also be used.
>
> Perhaps these alternatives will be more acceptable than SCP (though
> "why?" I cannot see!).
"Alas, my client hasn't the pull."
The vendor has specified what they will do, and they don't seem to be
bending.
Cheers,
-- jra
--
Jay R. Ashworth jra at baylink.com
Member of the Technical Staff Baylink RFC 2100
The Suncoast Freenet The Things I Think
Tampa Bay, Florida http://baylink.pitas.com +1 727 647 1274
"They had engineers in my day, too." -- Perry Vance Nelson
More information about the TAG
mailing list