| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Fixes 8914
|
| |
|
|
|
|
|
| |
The "bundle id" always had more in common with the PackageCode from the Windows
Installer. With the introduction of an actual Id attribute on the Bundle
element, there is potential for confusion, so there is finally real motivation
to rename "bundle id" to "bundle code".
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When running elevated, Burn uses the Windows Temp folder as its working folder
to prevent normal processes from tampering with the files. Windows Temp does
allow non-elevated processes to write to the folder but they cannot see the
files there. Unfortunately, contrary to our belief, non-elevated processes
can read the files in Windows Temp by watching for directory changes. This
allows a malicious process to lie in wait, watching the Windows Temp folder
until a Burn process is launched elevated, then attack the working folder.
Mitigate that attack by protecting the working folder to only elevated users.
Managed custom actions also fall back to using the Windows Temp folder in
some cases and thus can be exposed in a similar fashion as an elevated Burn
process. Remove that possibility.
|
| | |
|
| |
|
|
| |
Fixes 6818
|
| | |
|
| |
|
|
| |
Fixes #5830
|
| |
|
|
| |
Initialize them explicitly to make it clearer when that happens.
|
| |
|
|
|
|
| |
This behavior makes it work similar to the root package cache folder and avoids performance problems when there are many payloads in the package.
#4774
|
| | |
|
| |
|
