mirror/vcpkg
1
0
Fork 0
mirror of https://github.com/microsoft/vcpkg.git synced 2024-12-16 06:39:02 +08:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity
c66fd55f6f
vcpkg/ports/liblzma/build-tools.patch

21 lines
626 B
Diff
Raw Normal View History

Revert [liblzma] update to version 5.6.0 (#37199) (#37841) Resolves https://github.com/microsoft/vcpkg/issues/37839 Reverts #37199 See https://www.openwall.com/lists/oss-security/2024/03/29/4 Note that the version database is unmodified, only the baseline is changed. Because vcpkg builds liblzma from cmake sources downloaded from github and this backdoor required modifications only present in the release tarballs, it is our belief that vcpkg customers are not affected by this problem. However, we are reverting this version out of an abundance of caution as the threat actor clearly has broad access to liblzma infrastructure, and because we believe customers will start flagging this package by version as being a problem.
2024-03-30 18:30:28 +08:00
diff --git a/CMakeLists.txt b/CMakeLists.txt
index 03b8301..820d08e 100644
[liblzma] Update wrapper, add feature tools (#24708) * Fix liblzma wrapper for older CMake * Add feature for tools * Update versions * Test find_package(... REQUIRED)
2022-05-18 07:53:40 +08:00
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
Revert [liblzma] update to version 5.6.0 (#37199) (#37841) Resolves https://github.com/microsoft/vcpkg/issues/37839 Reverts #37199 See https://www.openwall.com/lists/oss-security/2024/03/29/4 Note that the version database is unmodified, only the baseline is changed. Because vcpkg builds liblzma from cmake sources downloaded from github and this backdoor required modifications only present in the release tarballs, it is our belief that vcpkg customers are not affected by this problem. However, we are reverting this version out of an abundance of caution as the threat actor clearly has broad access to liblzma infrastructure, and because we believe customers will start flagging this package by version as being a problem.
2024-03-30 18:30:28 +08:00
@@ -584,6 +584,7 @@ install(FILES "${CMAKE_CURRENT_BINARY_DIR}/liblzma-config.cmake"
COMPONENT liblzma_Development)
[liblzma] Update wrapper, add feature tools (#24708) * Fix liblzma wrapper for older CMake * Add feature for tools * Update versions * Test find_package(... REQUIRED)
2022-05-18 07:53:40 +08:00
+if(BUILD_TOOLS)
#############################################################################
Revert [liblzma] update to version 5.6.0 (#37199) (#37841) Resolves https://github.com/microsoft/vcpkg/issues/37839 Reverts #37199 See https://www.openwall.com/lists/oss-security/2024/03/29/4 Note that the version database is unmodified, only the baseline is changed. Because vcpkg builds liblzma from cmake sources downloaded from github and this backdoor required modifications only present in the release tarballs, it is our belief that vcpkg customers are not affected by this problem. However, we are reverting this version out of an abundance of caution as the threat actor clearly has broad access to liblzma infrastructure, and because we believe customers will start flagging this package by version as being a problem.
2024-03-30 18:30:28 +08:00
# getopt_long
[liblzma] Update wrapper, add feature tools (#24708) * Fix liblzma wrapper for older CMake * Add feature for tools * Update versions * Test find_package(... REQUIRED)
2022-05-18 07:53:40 +08:00
#############################################################################
Revert [liblzma] update to version 5.6.0 (#37199) (#37841) Resolves https://github.com/microsoft/vcpkg/issues/37839 Reverts #37199 See https://www.openwall.com/lists/oss-security/2024/03/29/4 Note that the version database is unmodified, only the baseline is changed. Because vcpkg builds liblzma from cmake sources downloaded from github and this backdoor required modifications only present in the release tarballs, it is our belief that vcpkg customers are not affected by this problem. However, we are reverting this version out of an abundance of caution as the threat actor clearly has broad access to liblzma infrastructure, and because we believe customers will start flagging this package by version as being a problem.
2024-03-30 18:30:28 +08:00
@@ -793,6 +794,7 @@ if(NOT MSVC AND HAVE_GETOPT_LONG)
endforeach()
[liblzma] Update to 5.4.0 (#28250) * [liblzma] Update to 5.2.9 * Update to 5.4.0
2023-01-05 21:01:34 +08:00
endif()
[liblzma] Update wrapper, add feature tools (#24708) * Fix liblzma wrapper for older CMake * Add feature for tools * Update versions * Test find_package(... REQUIRED)
2022-05-18 07:53:40 +08:00
endif()
Revert [liblzma] update to version 5.6.0 (#37199) (#37841) Resolves https://github.com/microsoft/vcpkg/issues/37839 Reverts #37199 See https://www.openwall.com/lists/oss-security/2024/03/29/4 Note that the version database is unmodified, only the baseline is changed. Because vcpkg builds liblzma from cmake sources downloaded from github and this backdoor required modifications only present in the release tarballs, it is our belief that vcpkg customers are not affected by this problem. However, we are reverting this version out of an abundance of caution as the threat actor clearly has broad access to liblzma infrastructure, and because we believe customers will start flagging this package by version as being a problem.
2024-03-30 18:30:28 +08:00
+endif()
[liblzma] Update to 5.4.0 (#28250) * [liblzma] Update to 5.2.9 * Update to 5.4.0
2023-01-05 21:01:34 +08:00
#############################################################################
Reference in New Issue Copy Permalink