Re: workaround suggestion
@gabri.ns: Sorry, but I'm lost. What are "A" and "B"?
Before posting, please read how to report bug or request support effectively.
Bug reports without an attached log file are usually useless.
If the target file exists and it is not write-able, but the target directory is, the file will may be transferred anyway with automatic resume. The error overwriting the file will occur only after the transfer finishes. It is because the file is first transferred into temporary file.
dd
or cat
to overwrite file, eg: cat temp > orig
OK, I did not think very far when I wrote this extra point. Still for most files, the observed result is that the original (group) ownership is preserved. Only in special cases, the (group) ownership is changed. The documentation that you mentioned says nothing about (group) ownership. If we know about this other documented behavior, we can see the connection, but that does NOT make this special (group) ownership behavior a documented behavior. It is NOT a documented behavior, but if it was, I would consider this even worst. Who in is right mind would want such a behavior ?
Unprivileged (regular) users who wish to change the group of a file that they own may use chgrp.
For obvious security reasons, the ownership of a file may only be altered by a super-user. Similarly, only a member of a group can change a file's group ID to that group.
It is strange that WinSCP can even do that. It requires root permission and I don't provide the required ROOT credential.