If throughput is not an issue, how about SSL? Put up a secure web server,
write some simple CGI scripts for authentication, then you don't even need
to give them "real" accounts on your server. Of course, if you have time
and want to get fancy, there is always various authentication methods, such
as mod_mysql (authentication against a MySQL database).
Password protect each client's directory so no one else can browse around.
Most firewalls allow ports 80 and 443.
Tin Le
----
Net Images - Premier Web Presence Provider http://www.netimages.com/~tin
Internet Security and Firewall Consulting
Tin Le - [EMAIL PROTECTED]
On Fri, 16 Jul 1999, Geoff Nordli wrote:
> At the request of a list member I will add some additional information.
>
> Throughput is not an issue. It is desinged for clients (<20) to pick up
> reports on a weekly basis. Reports generally range between 20-100K.
>
> It is essential that clients can not see other client's reports.
>
> I can't foresee any increase in activity. Once the system is in place it
> shouldn't need to change.
>
> Clients will be coming in from behind their respective firewall.
>
> Our ftp server is located in a DMZ.
>
> It really doesn't matter what FTP software I run on the linux box.
>
> I might as well ask about encrypting the datafiles. Does anyone have any
> ideas on what the best method is for this.
>
> I have complete control of how this is implemented. So I am totally open to
> new
> ideas.
>
> Ideally it would be best to have limited impact on the client side, since
> some companies
> I have no control over their systems.
>
> thanks
>
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
