Re^3: Customer data encryption

SFTP is actually a full featured remote file system protocol. Using it, it would be posible to process the data without downloading it first to the local harddisk. You could even write the output file directly on the remote host so sensible data never gets stored on your system.

Net::SFTP or Net::SFTP::Foreign would allow you to do so.

For maximun security, ssh keys should be protected by a keyphrase, but that would require to launch the process manually.

Comment on Re^3: Customer data encryption

Replies are listed 'Best First'.
Re^4: Customer data encryption by 0xbeef (Hermit) on Mar 01, 2007 at 14:28 UTC
Regarding SFTP, I would not like to make to make many assumptions about the customer. Consider the network policies of the institution. At most banks where I provide support, almost every outgoing protocol (FTP/SSH/SFTP) is blocked. Some organisations ONLY allow HTTP/HTTPS, so I would then have to set up a SSH tunnel over HTTP, which adds additional complexity and assumptions into the mix. In other words, if I do provide an SSH/SFTP mechanism, I would consider it a secondary method. Niel	[reply]

Replies are listed 'Best First'.

Re^4: Customer data encryption
by 0xbeef (Hermit) on Mar 01, 2007 at 14:28 UTC

In other words, if I do provide an SSH/SFTP mechanism, I would consider it a secondary method.

Niel

[reply]