similar to: file.rename(): Guaranteed to be complete or not at all?

Is there an alternative to using link(2) to rename files in sftp-server? Some users use sftp to upload files to a vfat partition on an sftp-server, and then renaming doesn't work. This breaks konqueror, for example (from KDE, which u), which upload files first with a ".part" extension and then renames them removing this extension.

I'm working on setting up a semi-trusted sftp service, and to get it working, I need chroot capability. I've taken the /./ wuftpd magic token code from contrib/chroot.diff and put it into the sftp server. The main problem is that privileges have been dropped by the time the subsystem is exec'ed, so my patch requires that sftp-server be setuid root. Not ideal, I know, but I drop all

And while we are at it, can you please comment on these patches as well, originally submitted around one year ago. Oh, and I think we can agree, that the secsh-filexfer standardization is dead, so there's not much point in trying to support newer protocol versions, which don't have statfs anyway. Thanks, Miklos ----- This is needed to be able to support statfs operation on an SSH

Hello. These patches add a new mode of operation for the sftp server. It is located between the ordinary, unrestricted mode and read-only mode. It allows you to add files to the server, but only if these files do not exist on the server before. Changes to existing files - are prohibited. Please review them, maybe these patches will be useful not only to me. Thank you. -------------- next part

Hello, I am sending the following proposal to discuss issues and solutions regarding data races in concurrent ThinLTO processes. This caught my attention when we encountered a race condition in ThinLTO with caching. While looking into how ThinLTO deals with the problem of cache files reads/writes/deletes I spotted a lot of problems: some of them are related to data races, others - to

Hello, Here is V2 of the arm64 support for klibc patch set. Notable changes since the original series: * fp regs dropped from setjmp/longjmp * chmod, lstat and stat re-implemented with *at functions. * open64 merged into open. As with the original, this series is to be applied against the latest klibc, just after 25a66fa README.klibc: update build information V2 has been tested on x86_64

Hello, This series introduces arm64 support to klibc. I've rebased the work from Neil Williams and Anil Singhar into the following three patches. Most of the code changes are due to new syscall implementations being needed for arm64 as a only a minimal set of syscalls are defined in the arm64 kernel. This series is to be applied against the latest klibc, just after 25a66fa README.klibc:

Hi Katya Thanks for investigating this. Here is my thought inline. > On Mar 22, 2018, at 1:32 AM, katya.romanova at sony.com wrote: > > > Hello, > > I am sending the following proposal to discuss issues and solutions regarding data races in concurrent ThinLTO processes. > > This caught my attention when we encountered a race condition in ThinLTO with caching. >

Le jeu. 22 mars 2018 à 16:46, Steven Wu <stevenwu at apple.com> a écrit : > Hi Katya > > Thanks for investigating this. Here is my thought inline. > > On Mar 22, 2018, at 1:32 AM, katya.romanova at sony.com wrote: > > > Hello, > > I am sending the following proposal to discuss issues and solutions > regarding data races in concurrent ThinLTO processes. >

What to try: $ cd /tmp $ touch a b $ sftp localhost sftp> cd /tmp sftp> rename a b Couldn't rename file "/tmp/a" to "/tmp/b": Failure sftp> rm b Removing /var/tmp/b sftp> rename a b sftp> So, the sftp "rename" command refuses to rename a file to an existing one. Instead of using the rename(2) system call, which is present at least on

https://bugzilla.mindrot.org/show_bug.cgi?id=1447 Summary: sftp-server rename fails when EXDEV is returned Classification: Unclassified Product: Portable OpenSSH Version: 4.7p1 Platform: All

Hi everyone, I described the reflink operation at the Linux Storage & Filesystems Workshop last month. Originally implemented as an ocfs2-specific ioctl, the consensus was that it should be a syscall from the get-go. Here's some first-cut patches. For people who have not seen reflink, either at LSF or on the ocfs2 wiki, the first patch contains Documentation/filesystems/reflink.txt to

Sftp fails to correctly preserve permissions when fetching a file. It adds write permission for the owner (presumably so it can write the file). Sftp also fails to preserve the uid/gid. Added code so that if is running as root, uid and gid are preserved. patch is based on Openssh 3.4p1. *** sftp-client.c@@\main\1 Tue Oct 1 17:26:20 2002 --- sftp-client.c Tue Nov 5 10:22:52 2002

Hi Steven, Look at my replies inline (below your comments). Katya. From: stevenwu at apple.com <stevenwu at apple.com> Sent: Thursday, March 22, 2018 4:46 PM To: Romanova, Katya <katya.romanova at sony.com> Cc: Teresa Johnson <tejohnson at google.com>; Mehdi AMINI <joker.eph at gmail.com>; Rafael Avila de Espindola <rafael.espindola at gmail.com>; Peter Collingbourne

https://bugzilla.mindrot.org/show_bug.cgi?id=1535 Summary: rename doesn't fall back to rename syscall upon ENOSYS of link syscall Product: Portable OpenSSH Version: 5.1p1 Platform: ix86 OS/Version: Linux Status: NEW Keywords: patch Severity: normal Priority: P3 Component:

https://bugzilla.mindrot.org/show_bug.cgi?id=2948 Bug ID: 2948 Summary: implement "copy-data" sftp extension Product: Portable OpenSSH Version: -current Hardware: All URL: https://tools.ietf.org/html/draft-ietf-secsh-filexfer- extensions-00#section-7 OS: All Status: NEW

> On Mar 26, 2018, at 8:54 PM, Mehdi AMINI <joker.eph at gmail.com> wrote: > > > > Le jeu. 22 mars 2018 à 16:46, Steven Wu <stevenwu at apple.com <mailto:stevenwu at apple.com>> a écrit : > Hi Katya > > Thanks for investigating this. Here is my thought inline. > >> On Mar 22, 2018, at 1:32 AM, katya.romanova at sony.com

From: stevenwu at apple.com <stevenwu at apple.com> Sent: Monday, March 26, 2018 11:58 PM To: Mehdi AMINI <joker.eph at gmail.com> Cc: Romanova, Katya <katya.romanova at sony.com>; Teresa Johnson <tejohnson at google.com>; Rafael Espíndola <rafael.espindola at gmail.com>; Peter Collingbourne <peter at pcc.me.uk>; Hans Wennborg <hans at chromium.org>; Reid

Hi Peter, Thank you for the clarification ☺. I’m sure you have a very good understanding of how much efforts it will take to write a patch for legacy C LTO to implement caching the same way it’s done in new C++ LTO API. How easy/difficult do you think it will be (very roughly, in LOC)? Do you anticipate that a lot of existing legacy C LTO infrastructure will have to be rewritten? Could this also

Hi All I found that the rsync cannot fully sync permission although I have specified the -A option. The ACL is ok but the permission itself is not. rsync command: rsync -rtgoDAh --stats --files-from=flist.txt --log-file=$DetailLogPath $OldPath $NewPath & Old Server (rsync version 3.0.4): -rw-r-----+ 1 43810537 imopfs 246784 Jul 22 10:17 miki2.sas7bdat New Server (rsync version