You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
with the new copy-to-tmp setting/code, it seems like copy-to-tmp being 1 breaks sharing under some circumstances (only observed with ssl so far).
there seems to be garbage memory before the actual userfile (45,000 bytes in one instance).
client stores the userfile but fails on loading it (no sanity check apparently), suggesting scripts/weed conversion and dies.
Found by: OUTsider (helped track down the issue)
The text was updated successfully, but these errors were encountered:
…490
Found by: OUTsider, simple, Geo, ...
Patch by: Cizzle
Fixes: #490
The userfile being received is now properly being sent to a tmpfile first if copy-to-tmp is set.
* Use tmpfile for receiving userfile when copy-to-tmp is enabled.
* Alter docs regarding copy-to-tmp.
with the new copy-to-tmp setting/code, it seems like copy-to-tmp being 1 breaks sharing under some circumstances (only observed with ssl so far).
there seems to be garbage memory before the actual userfile (45,000 bytes in one instance).
client stores the userfile but fails on loading it (no sanity check apparently), suggesting scripts/weed conversion and dies.
Found by: OUTsider (helped track down the issue)
The text was updated successfully, but these errors were encountered: