And if he encrypts using the http server's ssl cert, he doesn't even
have to worry about decryption issues - the https server can dwcrypt
and toss it to the downloading user.
Security? What's that? His looks more like a business/audit issue.
Am I jaded that I can now see giving the users what they want, instead
of what I think is correct? Then again, who am I to determine what is
correct.
On 5/18/07, L. V. Lammert <[EMAIL PROTECTED]> wrote:
At 03:31 PM 5/18/2007 -0400, stuart van Zee wrote:
>I have just been handed a new project and would like to
>know if anyone has any software suggestions that would
>fit the requirements or at least a point in the right
>direction.
>
>We need to have an https server running that users can
>upload un-encrypted files to and have those files encrypted
>on the fly and safely stored away until they are needed.
Sounds like a simple Ruby/Python/Perl/Python script to handle the upload,
saving as a temporary file until the upload is complete, then encrypting.
Might be a tad tricky to ensure the upload is complete first, but should
not be a big problem.
>Those same people will need to be able to download their
>files as they need them and have them decrypted for them
>and sent over https so that they can use their web browser
>to retrieve the files.
Just the opposite for retrieval?
HTH,
Lee
--
"This officer's men seem to follow him merely out of idle curiosity."
-- Sandhurst officer cadet evaluation.
