3 ms·

> instead of putting it in /var/tmp/usercache-<username> directory? Can't use fixed paths in tmp dirs, that's either a security issue or a denial of service at

> instead of putting it in /var/tmp/usercache-<username> directory? Can't use fixed paths in tmp dirs, that's either a security issue or a denial of service attack waiting to happen. I can `mkdir /var/tmp/usercache-prmoustache`. > Put that into /usr/local/<username> instead! Not writable to regular users, and not meant for that.

prmoustache 3y ago
> Can't use fixed paths in tmp dirs, that's either a security issue or a denial of service attack waiting to happen. I can `mkdir /var/tmp/usercache-prmoustache`. Well we don't even need a fixed dir, a session generated dir with an env variable set to it is enough. Or we could put that somewhere else in var. We created /var/run/<users> dirs, there is no reason we couldn't do other directories for other uses. >> Put that into /usr/local/<username> instead! > >Not writable to regular users, fixable > and not meant for that. I am pretty sure I have used some BSD in the past where the home directories were in /usr/home and /usr/local is a pretty good spot to put what is -- wait for it -- local to the machine! There is no reason we couldn't have all our user owned binaries in /usr/local/<username>/bin and /usr/local/<username>/lib and our configs in /usr/local/<username>/etc It would just have to be created at user creation with correct user rights but that is no big deal. Users would just put their files in their /home, be able to sync it accross machines/ possibly different OSes without necessarily synchronising config files that do not apply to it or worse, unneeded cache files. Their /usr/local/<username>/etc could be a git (or other versionning system) repo Their /usr/local/<username>/bin lib share whatever could be saved and restored easily And all the variable/ephemeral shit/cache could go to var where they belong.

3 ms·

> instead of putting it in /var/tmp/usercache-<username> directory? Can't use fixed paths in tmp dirs, that's either a security issue or a denial of service at

by yencabulator 3y ago

prmoustache 3y ago
> Can't use fixed paths in tmp dirs, that's either a security issue or a denial of service attack waiting to happen. I can `mkdir /var/tmp/usercache-prmoustache`. Well we don't even need a fixed dir, a session generated dir with an env variable set to it is enough. Or we could put that somewhere else in var. We created /var/run/<users> dirs, there is no reason we couldn't do other directories for other uses. >> Put that into /usr/local/<username> instead! > >Not writable to regular users, fixable > and not meant for that. I am pretty sure I have used some BSD in the past where the home directories were in /usr/home and /usr/local is a pretty good spot to put what is -- wait for it -- local to the machine! There is no reason we couldn't have all our user owned binaries in /usr/local/<username>/bin and /usr/local/<username>/lib and our configs in /usr/local/<username>/etc It would just have to be created at user creation with correct user rights but that is no big deal. Users would just put their files in their /home, be able to sync it accross machines/ possibly different OSes without necessarily synchronising config files that do not apply to it or worse, unneeded cache files. Their /usr/local/<username>/etc could be a git (or other versionning system) repo Their /usr/local/<username>/bin lib share whatever could be saved and restored easily And all the variable/ephemeral shit/cache could go to var where they belong.