FreeFileSync Forum

Thank you for your response. What I'm trying to say is that if the parent directory has facl permissions, or the group in the parent directory has SGIDs set, then newly created directories and files will not inherit these features.

When creating a new file or folder, can the permissions set by sftp be changed to inherit the permissions of the parent folder?

afs/sftp.cpp:67:50: error: ‘MAX_SFTP_READ_SIZE’ was not declared in this scope
67 | const size_t SFTP_OPTIMAL_BLOCK_SIZE_READ = 8 * MAX_SFTP_READ_SIZE;

FFS doesn't change the server's umask. Regarding permissions: Not sure if setting permissions for all files is the best solution. Maybe instead, FFS should try to preserve the permissions of existing files:
https://freefilesync.org/forum/viewtopic.php?t=6881


Thank you for your reply.
Yes, it is ...

In file included from ../../zen/globals.h:12,
from ../../zen/i18n.h:12,
from <command-line>:
../../libcurl/curl_wrap.h: In function ‘std::wstring zen::{anonymous}::formatCurlStatusCode(CURLcode)’:
../../libcurl/curl_wrap.h:140:41: error: ‘CURLE_QUIC_CONNECT_ERROR’ was not declared in this scope ...

Is it possible to let the server decide the value of the umask, or add the option to set the umask. Prior to version 10.19, the value of UMASK was determined by the service. In the current version, whatever value the server has set umask to is invalid, it becomes the fixed value 0022 set by FFS.

I need group members to have permission to write. The server tried various ways to set the default umask, such as alternate-sftp -u 002, pam_umask.so umask=002, and modify the umask of login.defs to 002. Also I'm using the latest ubuntu server

Before version 10.19, the server's umask settings were valid, but starting with version 10.20, the server's umask settings are invalid.

Is it possible to add settings for sftp umask, or to use server system settings instead