(title has a typo .. typed in "tmp or" twice, my apologies) Maybe the title of this post is not entirely clear, but I couldn't decide on a good title for this post. I enjoy my linux experience thus far. I find my system a bit more responsive, but that is subject to alot of things of course, maybe even a state of mind. Anyway, why is the tmp when located on a seperated partition not automatically set in /etc/fstab with nodev,nosuid,noexec and a chmod to 1777 or 3777 ? I've been searching on google about various basic security measures that are helpful in my opinion, but this particular tmp protection is not implemented in all distro's or the option is not in the initial installation options when manually configuring a partition setup. In case of /tmp and/or /var/tmp being on the same partition as where root is located you can create a loop device and mount it with nodev,nosuid,noexec. Anyway, I was just thinking if this helps preventing from programs being executed in a tmp location, why is this not enabled by default in all distro's ? I mean I don't mind looking for helpful security measures I can take myself, but just to be a bit safer right from the start would be nice I think. I forgot to mention /dev/shm but I realise that ubuntu has changed to /run I believe, so this may not be a universal security fix for all kinds of linuxes, except maybe for the /etc/fstab added parameters. Anyway, am I just being overconcerned or should the tmp environment be more hardened by default when installing a linux ? I was just wondering or maybe I'm just a bit thick and overlooking some issues I didn't think about. Maybe someone with more experience with security and linux can give a thought about this ? Cheers, Jan.