Re: [cifs-protocol] [REG:117050715700170] SMB1 processing of FileRnameInfo

2017-05-17 Thread Bryan Burgin via cifs-protocol
>From usermode using Win32 APIs on a Windows client, I believe it is impossible >to create the transaction you're trying to emit on-the-wire. I used your program and made one of my own, too. When either of our programs calls SetFileInformationByHandle() it calls Win32Rename(), based on the info

Re: [cifs-protocol] [REG:117050715700170] SMB1 processing of FileRnameInfo

2017-05-17 Thread Uri Simchoni via cifs-protocol
Back to my client code - - Both smbclient and my modified smbtorture3 RENAME test use a leading '\' in file name. BTW, SMB2 and later, that leading '\' is cleared by the client library, that is - the application requests '\file'. - When I remove the leading '\', it worked as you predicted. - When t

Re: [cifs-protocol] [REG:117050715700170] SMB1 processing of FileRnameInfo

2017-05-17 Thread Bryan Burgin via cifs-protocol
Concurrently, after shifting focus from the Win32 API question, I found our validation code on the server side. We have code that " If there are any path separators in the name, then we do not support this operation." Are you sure about " That means rename+replace in SMB1 is limited to dest bein