File Encryption just for the content not for the file name.

Hi
I want to know if it's possible to use File Encryption only to encrypt the file content but not the file name.

Thanks
Albert Torres

No, it is not possible atm. What is your use case?

We upload files to a partner and the partner that using a automatic process base on filename get the file form the server. For example we send the file customers_20190404.txt and their process look for a file called customers with today's date on the name.

Thanks!

How would they be able to process a file encrypted by WinSCP, even if it had a name they expect?

File tha required to be encrypted the automatic process based on file names move it to the right department where it will be decrypted by the right person usin powershell or a custom code. But while is on the sftp server should be protected nobody not even IT department that has access to servers should be allowed to open the file.

Albert Torres

Thanks!

OK. We will see, if more people ask for this.

sound good! we found a workaround for now, we are creating folder with the filename and date and put the encrypted file on it.

Thanks for a great product.

Albert Torres

I could really use the feature to not encrypt the file names.

In the meantime it there a way to get the encrypted filename(s) to do a separate rename? Would changing the file name interfere with the decryption process?

Also is the same file name always encrypted to the same string (not dependent on machine or date etc. just the key)? I could likely use this as a workaround.

tnx

AJC wrote:

I could really use the feature to not encrypt the file names.

I have added this request to the tracker:
https://winscp.net/tracker/1965
You can vote for it there.

In the meantime it there a way to get the encrypted filename(s) to do a separate rename? Would changing the file name interfere with the decryption process?

I do not understand.

Also is the same file name always encrypted to the same string (not dependent on machine or date etc. just the key)? I could likely use this as a workaround.

Of course not. The encrypted name is always different, due to a "salt" component.