[tahoe-lafs-trac-stream] [Tahoe-LAFS] #1050: open with SSH_FXF_TRUNC without SSH_FXF_CREAT violates SFTP spec, but everyone does it anyway

[Tahoe-LAFS]

#1050: open with SSH_FXF_TRUNC without SSH_FXF_CREAT violates SFTP spec, but
everyone does it anyway
----------------------------------------+----------------------------------
     Reporter:  bj0                     |      Owner:  bj0
         Type:  defect                  |     Status:  closed
     Priority:  major                   |  Milestone:  1.7.0
    Component:  code-frontend-ftp-sftp  |    Version:  1.6.1
   Resolution:  fixed                   |   Keywords:  sftp standards sshfs
Launchpad Bug:                          |
----------------------------------------+----------------------------------
Changes (by warner):

 * component:  code-frontend => code-frontend-ftp-sftp


Old description:

> It apparrently is against the SFTP spec (but not the POSIX) to open a
> file with SSH_FXF_TRUNC without including SSH_FXF_CREAT.
>
> Programs like OpenSSH server and sshfs ignore this little detail, though,
> and programs like "cp" fail if it is followed.
>
> workaround:
> SFTP frontend should accept FXF_WRITE | FXF_TRUNC.

New description:

 It apparrently is against the SFTP spec (but not the POSIX) to open a file
 with SSH_FXF_TRUNC without including SSH_FXF_CREAT.

 Programs like OpenSSH server and sshfs ignore this little detail, though,
 and programs like "cp" fail if it is followed.

 workaround:
 SFTP frontend should accept FXF_WRITE | FXF_TRUNC.

--

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1050#comment:12>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage