Llewellyn/exa
1
0
Fork 0
mirror of https://github.com/Llewellynvdm/exa.git synced 2024-11-05 04:17:51 +00:00
Code Issues Projects Releases Wiki Activity
90e0c5b60e
exa/xtests/permissions

25 lines
2.6 KiB
Plaintext
Raw Normal View History

Protect xtests against different default users The Vagrant tests assumed that there’d be a user called “vagrant” that would run the tests and create the files by default. Files would be owned by vagrant:vagrant by default, and this worked, until it came time to change that username. The naïve method was a search-and-replace, but this caused problems when the new user’s name wasn’t exactly the same length as the previous one. So to fix this, we now have our own user, named after the first animal I thought of, that makes the files’ owners and groups independent of the default user of whichever VM image the xtests are running on. Another place where it was hard-coded was the home directory, which was “/home/vagrant”, where the awkward testcases live. That last one has been changed to just “/testcases”, which has no mention of the user in it.
2017-04-28 18:34:23 +00:00
/testcases/permissions/forbidden-directory: Permission denied (os error 13)
Permissions Size User Group Date Modified Name
xtests for higher order bits Finally, re-do the permissions extended tests to include the setuid, setgid, and sticky bits, and rename the last two existing ones to match the others (files with the same names as their permissions).
2017-05-30 14:32:11 +00:00
.--------- 0 cassowary cassowary  1 Jan 12:34 000
Protect xtests against different default users The Vagrant tests assumed that there’d be a user called “vagrant” that would run the tests and create the files by default. Files would be owned by vagrant:vagrant by default, and this worked, until it came time to change that username. The naïve method was a search-and-replace, but this caused problems when the new user’s name wasn’t exactly the same length as the previous one. So to fix this, we now have our own user, named after the first animal I thought of, that makes the files’ owners and groups independent of the default user of whichever VM image the xtests are running on. Another place where it was hard-coded was the home directory, which was “/home/vagrant”, where the awkward testcases live. That last one has been changed to just “/testcases”, which has no mention of the user in it.
2017-04-28 18:34:23 +00:00
.--------x 0 cassowary cassowary  1 Jan 12:34 001
.-------w- 0 cassowary cassowary  1 Jan 12:34 002
.------r-- 0 cassowary cassowary  1 Jan 12:34 004
.-----x--- 0 cassowary cassowary  1 Jan 12:34 010
.----w---- 0 cassowary cassowary  1 Jan 12:34 020
.---r----- 0 cassowary cassowary  1 Jan 12:34 040
.--x------ 0 cassowary cassowary  1 Jan 12:34 100
.-w------- 0 cassowary cassowary  1 Jan 12:34 200
.r-------- 0 cassowary cassowary  1 Jan 12:34 400
xtests for higher order bits Finally, re-do the permissions extended tests to include the setuid, setgid, and sticky bits, and rename the last two existing ones to match the others (files with the same names as their permissions).
2017-05-30 14:32:11 +00:00
.rw-r--r-- 0 cassowary cassowary  1 Jan 12:34 644
.rwxr-xr-x 0 cassowary cassowary  1 Jan 12:34 755
.rwxrwxrwx 0 cassowary cassowary  1 Jan 12:34 777
.--------T 0 cassowary cassowary  1 Jan 12:34 1000
.--------t 0 cassowary cassowary  1 Jan 12:34 1001
.-----S--- 0 cassowary cassowary  1 Jan 12:34 2000
.-----s--- 0 cassowary cassowary  1 Jan 12:34 2010
.--S------ 0 cassowary cassowary  1 Jan 12:34 4000
.--s------ 0 cassowary cassowary  1 Jan 12:34 4100
.rwSrwSrwT 0 cassowary cassowary  1 Jan 12:34 7666
.rwsrwsrwt 0 cassowary cassowary  1 Jan 12:34 7777
Protect xtests against different default users The Vagrant tests assumed that there’d be a user called “vagrant” that would run the tests and create the files by default. Files would be owned by vagrant:vagrant by default, and this worked, until it came time to change that username. The naïve method was a search-and-replace, but this caused problems when the new user’s name wasn’t exactly the same length as the previous one. So to fix this, we now have our own user, named after the first animal I thought of, that makes the files’ owners and groups independent of the default user of whichever VM image the xtests are running on. Another place where it was hard-coded was the home directory, which was “/home/vagrant”, where the awkward testcases live. That last one has been changed to just “/testcases”, which has no mention of the user in it.
2017-04-28 18:34:23 +00:00
d--------- - cassowary cassowary  1 Jan 12:34 forbidden-directory
Reference in New Issue Copy Permalink