changes=EXIT - bug
-
- Contributor
- Posts: 638
- Joined: 26 Jun 2013, 14:03
- Distribution: x64 Openbox
- Location: Poland
- Contact:
changes=EXIT - bug
If /etc/changes-exit.conf contains nonexistent path, for example /home/guest/.config/test/test.conf then after reboot /home/guest/.config/test is created and owned by root, but it shouldn't be created if it doesn't exist (it could damage system if guest can't edit his configurable files). BTW I think that changes-exit.conf should work also for files, now only dirs are available.
No intelligence, no life, no information and no love can exist without prior intelligence, life, information or love. You won't find nonexistent thing/idea.
-
- Samurai
- Posts: 134
- Joined: 18 Sep 2012, 20:56
- Distribution: Porteus 64bit KDE4
- Location: Absurdistan
Re: changes=EXIT - bug
I thing the failure are in:
/opt/porteus-scripts/dump-session
line 45
/opt/porteus-scripts/dump-session
line 45
Code: Select all
...
MNAME=/mnt/live/memory/images/changes
...
FOLDERS=`grep '^/' /etc/changes-exit.conf | sed s/^.//g`
...
cp -af $FOLDERS $MNAME 2>/dev/null
...
Re: changes=EXIT - bug
to add to tome post
If you copy a file with root powers to say /home/guest/Downloads
that dir becomes owned by root....YMMV
I wonder if a sticky permission might resolve that?
If you copy a file with root powers to say /home/guest/Downloads
that dir becomes owned by root....YMMV
I wonder if a sticky permission might resolve that?