NUnit Framework

Using Path.GetTempPath() causes conflicts in shared temporary folders

Bug #719187 reported by David Schmitt
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
NUnit Framework
Fix Released
High
Charlie Poole
NUnit Framework 2.9.6

Bug Description

Mono uses /tmp as base directory for temporary paths. This can cause collisions for multiple users using nunit on the same machine (e.g local developer and CI system). This can be mitigated by using a random base path (also reducing the possibility for /tmp race attacks) or just documenting the problem when it occurs and suggesting to use the TMP environment variable when running under linux

Related branches

lp:nunit-3.0
Revision history for this message
David Schmitt (david-dasz) wrote :

See http://stackoverflow.com/q/16656/4918 for creating randomized directories

Revision history for this message
Charlie Poole (charlie.poole) wrote :

This should be fixed in DomainManager.cs, the only place we use Path.GetTempPath()

Changed in nunit-3.0:
status: New → Triaged
importance: Undecided → High
assignee: nobody → Charlie Poole (charlie.poole)
milestone: none → 2.9.6
Revision history for this message
Charlie Poole (charlie.poole) wrote :

Shadow copy cache is now in user local application data.

Changed in nunit-3.0:
status: Triaged → Fix Committed
Charlie Poole (charlie.poole)
Changed in nunit-3.0:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.