| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
This prevents the .NET ZipArchive (and friends) from keeping the whole
thing in memory, to support updating when we don't need to update the
Wixout when building a binary Wixlib.
|
| |
|
| |
|
|
|
|
| |
Closes 8589
|
|
|
|
|
|
|
|
| |
Generally, clean up the handling of getting the domain from a server name by
centralizing and simplifying it behind an improved GetDomainFromServerName()
based on the buggy GetServerName().
Fixes 8576
|
|
|
|
| |
Fixes 8630
|
|
|
|
| |
Fixes 8569
|
|
|
|
|
|
|
|
|
|
|
| |
Spillover from having more interactive controls. In WiX v3, showing a
page moved the focus as a typical person might expect. When WiX v4
added interactivity, the same code was used to update controls (e.g.,
when checking a checkbox set a property used in a `VisibleCondition` or
`EnableCondition` for another control on the same page). This change
prevents the focus-setting behavior if the same page is being shown.
Fixes https://github.com/wixtoolset/issues/issues/8144
|
|
|
|
|
|
| |
v143 output is compatible back to VS2017 (at least).
Fixes https://github.com/wixtoolset/issues/issues/8211.
|
| |
|
| |
|
|
|
|
| |
See issue 8033 for more details
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
...because SemVer is just a suggestion.
- Also fix missing NuGet cleanup.
- And update NuGet^2 packages because v6.3.1 has vulnerabilities.
|
| |
|
| |
|
|
|
|
| |
Fixes 7854
|
|
|
|
|
|
|
|
|
| |
Due to the handling of redundant symbols, which are only used by inline directory
syntax, the symbols were only defined in the first section encountered by the linker.
Fix that so at most one duplicated inline directory symbol is included when
referenced.
Fixes 7840
|
|
|
|
| |
Fixes 7837
|
|
|
|
| |
Fixes 7738
|
|
|
|
| |
Fixes 7612
|
| |
|
| |
|
|
|
|
| |
Fixes 7546
|
|
|
|
|
|
| |
Also add a few additional output types to built-in backends.
Fixes 7708
|
|
|
|
| |
FIxes https://github.com/wixtoolset/issues/issues/7677.
|
|
|
|
|
|
|
|
|
| |
Addresses two issues in the creation of configurable merge modules. First, the
ModuleConfiguration table Id should not be modularized. Second, the
ModuleSubstitution table was never created. Fixing both of those allows
configurable merge modules to work again.
Fixes 7559
|
|
|
|
|
|
|
|
| |
TrueType fonts are denoted by the empty string in the FontTitle field of the
FileSymbol. That means a non-null FontTitle field value means a font is being
installed.
Fixes 7593
|
|
|
|
|
|
|
|
|
|
| |
In the long ago, a share could have one user/permissions pair. That's
really limited, of course, so support for _n_ user/permissions pairs
was added. In the move to WiX v4, support for that single, legacy user
was removed from the extension side but not the custom action side.
Remove that support.
Fixes https://github.com/wixtoolset/issues/issues/7632.
|
| |
|
|
|
|
|
|
| |
IWindowsInstallerDecompileContext.TreatProductAsModule.
https://github.com/wixtoolset/issues/issues/7607
|
| |
|
|
|
|
| |
Fixes https://github.com/wixtoolset/issues/issues/7568,
|
| |
|
| |
|
|
|
|
|
|
| |
Also fix documentation in ResolveWixLibraryReferences target.
Fixes 7512
|
|
|
|
| |
Fixes https://github.com/wixtoolset/issues/issues/7522.
|
|
|
|
|
|
|
|
| |
A package's cached status is no longer set via the PackageState. The value was
removed in native code but the managed code was missed throwing off the enum
mapping.
Fixes 7399
|
|
|
|
| |
Fixes https://github.com/wixtoolset/issues/issues/7459.
|
|
|
|
| |
Fixes https://github.com/wixtoolset/issues/issues/7472.
|
|
|
|
|
|
|
| |
Fix duplicate NoMinimize attribute and
add attributes that were entirely missing.
Fixes https://github.com/wixtoolset/issues/issues/7482.
|