08-21-2020, 01:34 PM
>>I will have a look, but temporary files are not and have never been encrypted.
Definitely not expecting temporary files be encrypted, I was trying to eliminate temporary files altogether by using SendStream instead of links to cache files. It works correctly when not using async as there are no temp files left over from SendStream. The other issue is that the async temporary files don't get deleted after the session ends, they stay until the app shuts down or stay permanently if the app crashes. In my case the temp files contained plane text names and figures so I would have a hard time explaining that to a customer if there were an issue discovered. My plan was to deliver the data from encrypted database -> memory -> SSL connection but did not expect an intermediate plane text to disk step.
>> It is not that it is "unintended".
In the IW code it looks like for async SendStream a temp file is specifically created using the ctOneTime flag (delete after download) so it is probably failing somewhere in there.
>>it seems that this issue only happens on Chrome.
Also fails in Edge.
Definitely not expecting temporary files be encrypted, I was trying to eliminate temporary files altogether by using SendStream instead of links to cache files. It works correctly when not using async as there are no temp files left over from SendStream. The other issue is that the async temporary files don't get deleted after the session ends, they stay until the app shuts down or stay permanently if the app crashes. In my case the temp files contained plane text names and figures so I would have a hard time explaining that to a customer if there were an issue discovered. My plan was to deliver the data from encrypted database -> memory -> SSL connection but did not expect an intermediate plane text to disk step.
>> It is not that it is "unintended".
In the IW code it looks like for async SendStream a temp file is specifically created using the ctOneTime flag (delete after download) so it is probably failing somewhere in there.
>>it seems that this issue only happens on Chrome.
Also fails in Edge.