Reduce probability of temp file permission errors

[Crevax]

Even though the app runs as Administrator, I believe Windows can still restrict access to the system's temp directory. I've seen multiple reports around temp file access being denied, so this should help avoid those cases.

[lauralex]

@Crevax Add + "\\" at the end, otherwise it won't work

[Crevax]

Thanks, good catch! I was part-way through using Path methods instead of string concatenation, but after seeing a bunch more people in a Discord post issues I wanted to get this out quick.

[lauralex]

@Crevax Going to test it today and I'll approve the PR

[lauralex]

Already closed in this pr: #45

@Crevax I preferred to use the SYSTEM TEMP instead of the LOCAL USER TEMP. Instead, I implemented a simple Privilege Escalation exploit to get from HIGH integrity level to SYSTEM integrity level, so there's shouldn't be any permission problem (in theory)

[Crevax]

What's your reasoning for preferring the system temp path? It is because debug mode is being leveraged to hook into DWM, so process escalation is essentially keeping the app out of a user context?

Typically I want to leverage core language methods and systems APIs instead of doing anything directly, but I understand that this app needs to circumvent the standard process with the lack of APIs for DWM so things have to get weird.

[lauralex]

What's your reasoning for preferring the system temp path? It is because debug mode is being leveraged to hook into DWM, so process escalation is essentially keeping the app out of a user context?

Typically I want to leverage core language methods and systems APIs instead of doing anything directly, but I understand that this app needs to circumvent the standard process with the lack of APIs for DWM so things have to get weird.

Because otherwise I had to change the dll project (which expects the LUTs in the SYSTEM TEMP folder). Also, privilege escalation to SYSTEM integrity level prevents possible permission-related issues.

[Crevax]

What's your reasoning for preferring the system temp path? It is because debug mode is being leveraged to hook into DWM, so process escalation is essentially keeping the app out of a user context?

Typically I want to leverage core language methods and systems APIs instead of doing anything directly, but I understand that this app needs to circumvent the standard process with the lack of APIs for DWM so things have to get weird.

Because otherwise I had to change the dll project (which expects the LUTs in the SYSTEM TEMP folder). Also, privilege escalation to SYSTEM integrity level prevents possible permission-related issues.

Haha, oh right. I don't do any C++ development so I totally forgot about that component as well.