| Commit message (Collapse) | Author | Files | Lines |
|
|
|
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.
|
|
When deleting directories recursively, an elevated custom action
following junctions in a user-writable location could recurse into
any directory, including some that you might not want to be deleted.
Therefore, avoid recursing into directories that are actually
junctions (aka "reparse points").
This applies to:
- The RemoveFoldersEx custom action (which doesn't actually do deletions
but would instruct elevated MSI to delete on your behalf).
- DTF's custom action runner.
|
|
Take this breaking change opportunity to simplify the header files used by
BA devs.
|
|
|
|
Fixes https://github.com/wixtoolset/issues/issues/8059.
|
|
It's a formatted field but was too short.
Fixes https://github.com/wixtoolset/issues/issues/8043.
|
|
|
|
|
|
Fixes https://github.com/wixtoolset/issues/issues/8040.
|
|
Fixes https://github.com/wixtoolset/issues/issues/8036.
|
|
|
|
|
|
|
|
|
|
Also renames WixToolet.BextUtil nupkg to WixToolset.BootstrapperExtensionApi.
|
|
|
|
|
|
|
|
|
|
This will prevent elevated processes from accidentally following a junction
from a user-writable directory to a per-machine directory and erroneously
deleting the per-machine contents.
|
|
|
|
|
|
Fixes wixtoolset/issues#7709.
|
|
And *Sequence/Show works thusly, even with somewhat funky ids.
|
|
|
|
|
|
|
|
|
|
Implements https://github.com/wixtoolset/issues/issues/7857.
Like [naked files](https://github.com/wixtoolset/issues/issues/7696),
`Files` elements can appear where `Component` elements do in WiX v4. The
optimizer enumerates files and directories, generating single-file
components as it goes. MSBuild-like wildcards (including `**`) are
supported. `Excludes` child elements lets you exclude files that would
otherwise be captured by wildcards.
|
|
Fixes https://github.com/wixtoolset/issues/issues/7935.
|
|
Fixes https://github.com/wixtoolset/issues/issues/7798.
|
|
|
|
...from `Overridable="yes"`.
Fixes https://github.com/wixtoolset/issues/issues/7981 for WiX v5.
|
|
|
|
|
|
ExePackage, BundlePackage, and related bundles
|
|
|
|
|
|
|
|
Plus a couple small clean-ups in a couple of dutil files.
|
|
When BootstrapperApplications move out of proc there will be another set of
pipes in Burn that behave differently from the inter-Burn communication pipes
that exist now. So renaming the existing pipe related files now to better
reflect that it is related to Burn talking to Burn when elevated or embedded.
|
|
Implements https://github.com/wixtoolset/issues/issues/7696.
`File` elements can appear where `Component` elements do in WiX v4. The
compiler generates an appropriate per-file component. Naked files under
`Directory`, `DirectoryRef`, `Fragment`, `StandardDirectory`, or
`Package` elements are included in a package via the [default-feature
feature](https://github.com/wixtoolset/issues/issues/7581). Naked files
appearing under `ComponentGroup`, `Feature`, `FeatureRef`, and
`FeatureGroup` generate the component and the reference to the parent
element.
Components and naked Files default to being installed to INSTALLFOLDER
(including a default INSTALLFOLDER if one isn't otherwise authored).
|
|
It's a bit overzealous.
Fixes https://github.com/wixtoolset/issues/issues/7579.
|
|
...to load DLLs from System32 only.
(Belt and suspenders to current approaches.) See
https://devblogs.microsoft.com/oldnewthing/20230328-00/?p=107978.
Fixes https://github.com/wixtoolset/issues/issues/7319.
|
|
It was never implemented and ass-u-mes containers are cabs,
which hopefully won't be the case forever.
Fixes https://github.com/wixtoolset/issues/issues/7490.
|
|
...TreatProductAsModule to KeepModularizationIds to better describe what
it does.
Fixes https://github.com/wixtoolset/issues/issues/7607.
|
|
|
|
Add Package/@UpgradeStrategy to allow `none` to suppress major upgrade.
Implements https://github.com/wixtoolset/issues/issues/7605.
Requires https://github.com/wixtoolset/wix/pull/435.
|
|
If INSTALLFOLDER is referenced and not defined, define one with
reasonable default values.
Implements WIP https://github.com/wixtoolset/issues/issues/7588.
|