Can Someone Confirm if the FTP Permissions Settings are Broken?

[indivision]

Hello.

I'm trying to confirm whether the FTP permissions settings are broken in Scale.

You can see the permission settings in System Settings > Services > FTP (Advanced Settings).

In my tests, setting any Execute permission does not result in the FTP uploaded files having any Execute permissions as they are supposed to.

Can some good soul confirm that they are seeing the same thing? Or, not? (Should take just a minute to test for someone with any FTP set up.)

For the record, I tried to set up a ticket for this, here: https://ixsystems.atlassian.net/browse/NAS-122761

For some reason, they entered the ticket as "Lowest" priority (for a broken feature?!). Also, they wouldn't answer a basic question about why a debug was needed to verify this specific bug. Uploading server details is a non-trivial request when a server can contain confidential business documents. So, I don't think it is unreasonable to ask whether or not that is really necessary for a specific report. I'm open to the possibility that something could be wrong on my server causing this. But, frankly, it doesn't seem likely with this particular feature.

Thank you for any help anyone can offer.

 

[Patrick M. Hausen]

The client sending the file defines the access bits in FTP.

 

[indivision]

The client sending the file defines the access bits in FTP.

Thank you. In that case, what is the purpose of the file permission settings in the Scale GUI?

 

[indivision]

The client sending the file defines the access bits in FTP.

An additional side note: if I change the permissions in the Scale GUI, it does affect the permissions that the uploaded files have. It's only the Execute parameter that won't change.

Are you saying that only the Execute parameter has to be changed by the client?

FWIW, these are files being uploaded to the server from a printer/scanner (Dell 2155cdn). I looked through the server settings and it doesn't appear to have a file permissions config...

It used to work with SMB. But, I think it requires an old version that is no longer included with Scale...

 

[Patrick M. Hausen]

My guess is that the permissions work similar to Samba - as the maximum that the client is allowed to set. Why would you need the execute permission on scanned documents?

 

[indivision]

My guess is that the permissions work similar to Samba - as the maximum that the client is allowed to set. Why would you need the execute permission on scanned documents?

That is what it looks like. There is a max number it allows and anything higher gets converted to the max.

The Paperless-ngx app needs to have Execute rights to newly scanned files in order for it to process them.

I had hoped that just running a cron task that updates the perms periodically would work. But, the way Paperless works, it keeps track of files as they are added to the folder and only attempts to process them once at the moment of detection. After that, you have to restart the app to get it to "see" the file again.

Now, I'm thinking I'll need to make a task that fixes the perm and also moves the files to a separate folder that Paperless is watching...