![]() |
| reparse point support wanted for .NET2 installation |
|
tzuk
|
I tried running .Net installation sandboxed, and I recall that it failed, but not due to junction points. At that time it had to do with the installation of security catalogs and other little known Windows features.
As for the "access denied", it is by design. It is meant to protect against a sandboxed program creating a (sandboxed) junction to c:\program files (for example), so then when you delete the sandbox, c:\program files disappears as well. Not so good! At some future time I may extend the support for translation junction targets, but probably not soon. Too much to do as it is. |
||||||||||||
|
_________________ tzuk |
|||||||||||||
|
v2y
|
In this situation, junction is sandboxedfolder to sandboxedfolder,
so *partial* support for reparse point (pass only if sandboxed->sandboxed) will solve this issue, I realized. I'm looking forward to enhancement easygoingly, of course while keeping sandbox secure. // This operation is by calling from deep inside mscorwks.dll. |
||||||||||||
|
|
|||||||||||||
|
tzuk
|
Well, it's not really a question of pass/deny at this time, because Sandboxie strips the junction point creation rights in advance, and aside from that, it stays out of the junction point creation procedure. So there is no way to decide pass/deny at this time. But it is definately fixable and I will get around to it eventually.
|
||||||||||||
|
|
|||||||||||||
|
tzuk
|
Fixed in version 3.29.25.
|
||||||||||||
|
|
|||||||||||||
| reparse point support wanted for .NET2 installation |
|
||
|


Use the RSS feed to watch this topic for replies