Skip to content
This repository was archived by the owner on Nov 25, 2020. It is now read-only.

class.AbstractAccessDriver::fixPermissions wrong CHMOD given #401

Closed
warhawk3407 opened this issue Dec 22, 2013 · 9 comments
Closed

class.AbstractAccessDriver::fixPermissions wrong CHMOD given #401

warhawk3407 opened this issue Dec 22, 2013 · 9 comments

Comments

@warhawk3407
Copy link
Contributor

Hello,

Using the SFTP_PSL plugin, we can see that the CHMOD octal number is wrong.

If the folder has "0755", pydio will display "0757" (using "more" -> "File Permissions").

The problem seems to come from the method fixPermissions in class.AbstractAccessDriver @ line 494.
I can't understand the different operations done...
The chmod given by the SFTP_PSL plugin is correct : "40755" (directory)

I can't debug the lines because the way it was coded is too obfuscated for me...

Regards

@warhawk3407
Copy link
Contributor Author

Any news about this issue ? :)

@cdujeu
Copy link
Member

cdujeu commented Oct 16, 2014

hi @warhawk3407 coming back on you on that, any news? I close it, please reopen if necessary.

@cdujeu cdujeu closed this as completed Oct 16, 2014
@warhawk3407
Copy link
Contributor Author

hi @cdujeu :-)

Tried today on 5.2.5, I have been able to reproduce the bug on my fresh set up :(

So for me, it is NOT FIXED.

See:
-> http://s13.postimg.org/h6tzwgnon/Capture.png
-> http://s1.postimg.org/gbwiojhcv/Capture2.png

I have compared the output from the terminal and ajaxplorer. They are different.

Regards

@cdujeu cdujeu reopened this Oct 31, 2014
@cdujeu
Copy link
Member

cdujeu commented Oct 31, 2014

ok ok i reopen it :-)
sorry

@cdujeu
Copy link
Member

cdujeu commented Oct 31, 2014

Mmm, re-reading, what value does your "fix permission" parameter have?? Because if it's set to "user", it's normal because it means "apply user right to all", so typically transform 7XX to 7X7.
-c

@warhawk3407
Copy link
Contributor Author

Here is the repo configuration:
http://awesomescreenshot.com/0213rpy338
http://awesomescreenshot.com/03c3rpyhb0

Now, if I create a file using my repository user (warhawk), with a default umask I have got this :
http://image.noelshack.com/fichiers/2014/44/1414888230-capture.png

To my mind, there is no reason to get a "rwx" on the "other group" in Pydio (CHMOD 646 in Pydio instead of 644 in the terminal).

Maybe Pydio is using this little "hack" to allow read/write perms on repos ?
When you mean "apply user right to all", do you mean Pydio users or Linux users ?
Could you explain me in details your reflection about this issue, that maybe not a real one but a misunderstanding about Pydio internal process ?

Concerning this plugin, I would like to see the real perms as displayed in the terminal when you are connected to the repository, as the user you entered in the repo settings :)

@warhawk3407
Copy link
Contributor Author

Up ? :)

@cdujeu
Copy link
Member

cdujeu commented Nov 21, 2014

Hi
The problem is that generally if you stick to the "User" right, as the user id is not the same as the current webserver user (generally apache or equivalent), php standard permission operations will think that the resource is not writeable. That's why we copy the "User" right to "Other", so that if it's writeable for the ssh user, Pydio will also see it writeable for Apache user.
-c

@warhawk3407
Copy link
Contributor Author

Ok so if it is a permission hack intentionally made for Pydio, I'm okay :-)

You can close this issue.

This was referenced May 22, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants