martin wrote:

This bug has been added to the tracker:
https://winscp.net/tracker/762

Just tested on version 5.0.4 beta with no luck. Getting deeper into the problem I just discovered that problem is probably related to SFTP server (wrong umask used) rather than to WinSCP client. It seems that no chmod operation is performed after mkdir by default using different sftp client (and WinSCP behaves the same way).

In any case, thanks for the fix made in "Create folder" dialog. It's now a bit simplier for users to force normal permissions to be set from client side as a work-around.

This bug has been added to the tracker:
https://winscp.net/tracker/762

Thanks for your post. I'll check it.

When creating a new directory on some target systems over SFTP-3 connection, wrong permissions are set due to a missing 'x' attribute (implicit settings). Also, when customizing permissions under "Create folder" dialog, 'x' attribute for 'ugw' is unchecked by default. The default value should be 0755 octal instead of 0644 for a new directory.

Tested on Winscp version 4.3.5 (WinXP SP3), but previous versions are probably affected by the issue.