Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I know i can do it, but is it a bad practice? It will look like this:

(System)TEMP -> E:\TEMP
(User)TEMP -> E:\TEMP
(System)TMP -> E:\TEMP
(User)TMP -> E:\TEMP

share|improve this question
Did you want to ask this? (System)TMP -> E:\TEMP (System)TEMP -> E:\TEMP (User)TMP -> E:\TEMP (User)TEMP -> E:\TEMP (swapped one TMP and one TEMP) – Hennes Jun 7 '13 at 13:06
@Hennes yes! sorry, I'll edit my question. – flagg19 Jun 7 '13 at 15:20
up vote 1 down vote accepted

As always: it depends.

If your TEMP folder has an access control list giving almost all access to anyone on new files and folders and if there is a system process that is

  1. storing sensitive information in TEMP
  2. not locking the files
  3. not changing the default access rights
  4. not cleaning the files up

then you might end up with a user being able to read this information. Or even worse with a user being able to modify this information. There are known attacks on Unix with processes using temp files and not handling them in a secure way.

So in my opinion it is not good practice to use the same TEMP folder for SYSTEM and users. BTW, why would you want to do so? And what about the LocalService and NetworkService accounts, why not change these also?

share|improve this answer
The reason is kind of silly, i always keep a RAMDisk active and for saving SSD life i want to prevent any unnecessary write on it (SSD). I tought RAMDisk would be a great place for a temp folder, and the software i use to make it has an option to re-create a folder named TEMP at startup. Just one folder..."Why not merge them?" i asked myself, and here we are :D. I'm the only user on this pc, i'll give it a try, thanks for the answer. – flagg19 Jun 7 '13 at 15:18
If you want to do it, go ahead. If you want to make it safer, you can set the access rights so that everyone can create new files and folders under TEMP, but the created objects can only be accessed (read, written, deleted) by the owner. – Werner Henze Jun 10 '13 at 7:07

I would call it great practice, unless there is some confidential info that's to be stored in a user's temp folder (which is likely why every user has their own, and system has a separate one). It all should be deleted in the end, but that's the worst downside I could think of.

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .