Timeline for Why does Unix ask for password when I try to pull a file with permission 777 using scp?
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 16, 2019 at 11:25 | history | edited | Stephen Kitt | CC BY-SA 4.0 |
Merge muru’s explanation.
|
| Apr 16, 2019 at 10:38 | comment | added | daedalus_hamlet | @muru your comment clarifies it. Thanks. | |
| Apr 16, 2019 at 10:26 | comment | added | muru | @daedalus_hamlet when the password is being requested, SSH hasn't even started to look at the file. Only after the user is authenticated will SSH look for the file and check permissions. So the permissions being 777 are absolutely irrelevant until your user is authenticated with SSH. | |
| Apr 16, 2019 at 10:12 | comment | added | daedalus_hamlet | user is the owner of the file. I did not mention it due to the irrelevancy of relationship when the permission is set as 777 | |
| Apr 16, 2019 at 10:02 | comment | added | Stephen Kitt |
The first triple applies to the owner, the middle triple to the group, and the last triple to everyone else; but you haven’t specified what user’s relationship to alpha.txt is, which is why I wrote that the relevant permissions are those which apply to user (not “owner”, the specific user you’re accessing the file as). If user is alpha.txt’s owner, then the owner permissions apply; if user is a member of alpha.txt’s owning group, then the group permissions apply; otherwise, the other permissions apply.
|
|
| Apr 16, 2019 at 9:59 | comment | added | daedalus_hamlet | I understand that it is SSH that asks for the password but I think that this line "the relevant permissions for alpha.txt are only those which apply to user" is wrong. Does not the LSB in 777 apply for everyone and MSB for the owner of the file? | |
| Apr 16, 2019 at 9:51 | history | answered | Stephen Kitt | CC BY-SA 4.0 |