|
> > 1) The encrypted .zip seems the simplest solution and in the interest of > > expediency we might go with something like that - assuming that is > > 'secure' enough to suit our client. > > Unless something has changed since I last looked into it, the encryption > on a ZIP file is relatively weak. Scott, I am leaning towards an HTTPS solution, but will retain the encrypted email option as 'Plan B'. Thanks for the clarification on those *nix things. The utility I recall seeing was a CMD and CL front-end to a port of a C-language gzip utility so I guess it wouldn't have handled encryption anyway... JK
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.