pkg/cmd/pr/list/http.go

.allstar/binary_artifacts.yaml

@@ -0,0 +1,63 @@
+# Ignore reason: These artifacts are used in unit tests or they are tools
+# used by the build. It's impractical to make changes at this stage of the
+# project to generate the tools from source.
+ignorePaths:
+- omaha/internal/tools/ApplyTag.exe
+- omaha/recovery/lib/bin/dbg/google_update_recovery.lib
+- omaha/recovery/lib/bin/opt/google_update_recovery.lib
+- omaha/testing/unittest_support/CodeRed.crx3
+- omaha/testing/unittest_support/GoogleUpdateHelper.msi
+- omaha/testing/unittest_support/GoogleUpdate_corrupted.exe
+- omaha/testing/unittest_support/GoogleUpdate_now_expired_cert.exe
+- omaha/testing/unittest_support/GoogleUpdate_old_signature.exe
+- omaha/testing/unittest_support/LongRunning.exe
+- omaha/testing/unittest_support/LongRunningSilent.exe
+- omaha/testing/unittest_support/Omaha_1.2.x_resources/goopdateres_ar.dll
+- omaha/testing/unittest_support/Omaha_1.2.x_resources/goopdateres_bg.dll
+- omaha/testing/unittest_support/Omaha_1.2.x_resources/goopdateres_ca.dll
+- omaha/testing/unittest_support/SaveArguments.exe
+- omaha/testing/unittest_support/SaveArguments_OmahaTestSigned.exe
+- omaha/testing/unittest_support/SaveArguments_different_ou.exe
+- omaha/testing/unittest_support/SaveArguments_multiple_cn.exe
+- omaha/testing/unittest_support/SaveArguments_no_cn.exe
+- omaha/testing/unittest_support/SaveArguments_unsigned_no_resources.exe
+- omaha/testing/unittest_support/SaveArguments_unsigned_wrong_markup_size.exe
+- omaha/testing/unittest_support/SaveArguments_unsigned_wrong_markup_value.exe
+- omaha/testing/unittest_support/SaveArguments_unsigned_wrong_resource_name.exe
+- omaha/testing/unittest_support/SaveArguments_wrong_cn.exe
+- omaha/testing/unittest_support/Sha1_4c40dba5f988fae57a57d6457495f98b.exe
+- omaha/testing/unittest_support/Sha1_4c40dba5f988fae57a57d6457495f98b_and_sha2_2a9c21acaaa63a3c58a7b9322bee948d.exe
+- omaha/testing/unittest_support/chrome_certificate_09E28B26DB593EC4E73286B66499C370.dll
+- omaha/testing/unittest_support/chrome_certificate_2912C70C9A2B8A3EF6F6074662D68B8D.dll
+- omaha/testing/unittest_support/chrome_setup.exe
+- omaha/testing/unittest_support/download_cache_test/{7101D597-3481-4971-AD23-455542964072}/livelysetup.exe
+- omaha/testing/unittest_support/download_cache_test/{89640431-FE64-4da8-9860-1A1085A60E13}/gears-win32-opt.msi
+- omaha/testing/unittest_support/download_cache_test/{C5CC8735-9BE0-45c5-804C-F117E96047C7}/GoogleUpdateSetup.exe
+- omaha/testing/unittest_support/old_google_certificate.dll
+- omaha/testing/unittest_support/omaha_1.0.x/GoogleUpdate.exe
+- omaha/testing/unittest_support/omaha_1.0.x/goopdate.dll
+- omaha/testing/unittest_support/omaha_1.1.x/GoogleUpdate.exe
+- omaha/testing/unittest_support/omaha_1.1.x/goopdate.dll
+- omaha/testing/unittest_support/omaha_1.1.x/goopdateres_en.dll
+- omaha/testing/unittest_support/omaha_1.2.131.7_shell/GoogleUpdate.exe
+- omaha/testing/unittest_support/omaha_1.2.183.9_shell/GoogleUpdate.exe
+- omaha/testing/unittest_support/omaha_1.2.x/GoogleUpdate.exe
+- omaha/testing/unittest_support/omaha_1.2.x/goopdate.dll
+- omaha/testing/unittest_support/omaha_1.2.x/goopdateres_en.dll
+- omaha/testing/unittest_support/omaha_1.2.x_newer/GoogleUpdate.exe
+- omaha/testing/unittest_support/omaha_1.3.x/GoogleUpdate.exe
+- omaha/testing/unittest_support/omaha_1.3.x/goopdate.dll
+- omaha/testing/unittest_support/omaha_1.3.x/goopdateres_en.dll
+- omaha/testing/unittest_support/sha1_06aea76bac46a9e8cfe6d29e45aaf033.sys
+- omaha/testing/unittest_support/sha1_14F8FDD167F92402B1570B5DC495C815.sys
+- omaha/testing/unittest_support/sha2_0c15be4a15bb0903c901b1d6c265302f.msi
+- omaha/testing/unittest_support/sha2_0e4418e2dede36dd2974c3443afb5ce5.msi
+- omaha/testing/unittest_support/sha2_2a9c21acaaa63a3c58a7b9322bee948d.exe
+- omaha/testing/unittest_support/unsigned.crx3
+- omaha/testing/unittest_support/valid.crx2
+- omaha/testing/unittest_support/valid_no_publisher.crx3
+- omaha/testing/unittest_support/valid_publisher.crx3
+- omaha/tools/MsiTagger.exe
+- omaha/tools/resmerge.exe
+- third_party/lzma/files/7zr.exe
+- third_party/lzma/files/lzma.exe

.clang-format

@@ -0,0 +1,28 @@
+# Defines the Chromium style for automatic reformatting.
+# http://clang.llvm.org/docs/ClangFormatStyleOptions.html
+BasedOnStyle: Chromium
+# This defaults to 'Auto'. Explicitly set it for a while, so that
+# 'vector<vector<int> >' in existing files gets formatted to
+# 'vector<vector<int>>'. ('Auto' means that clang-format will only use
+# 'int>>' if the file already contains at least one such instance.)
+Standard: Cpp11
+
+# Make sure code like:
+# IPC_BEGIN_MESSAGE_MAP()
+#   IPC_MESSAGE_HANDLER(WidgetHostViewHost_Update, OnUpdate)
+# IPC_END_MESSAGE_MAP()
+# gets correctly indented.
+MacroBlockBegin: "^\
+BEGIN_COM_MAP|\
+BEGIN_MSG_MAP|\
+BEGIN_OBJECT_MAP|\
+BEGIN_PROP_MAP|\
+BEGIN_REGISTRY_MAP|\
+BEGIN_SERVICE_MAP$"
+MacroBlockEnd: "^\
+END_COM_MAP|\
+END_MSG_MAP|\
+END_OBJECT_MAP|\
+END_PROP_MAP|\
+END_REGISTRY_MAP|\
+END_SERVICE_MAP$"

.github/workflows/scorecard.yml

@@ -0,0 +1,73 @@
+# This workflow uses actions that are not certified by GitHub. They are provided
+# by a third-party and are governed by separate terms of service, privacy
+# policy, and support documentation.
+
+name: Scorecard supply-chain security
+on:
+  # For Branch-Protection check. Only the default branch is supported. See
+  # https://github.com/ossf/scorecard/blob/main/docs/checks.md#branch-protection
+  branch_protection_rule:
+  # To guarantee Maintained check is occasionally updated. See
+  # https://github.com/ossf/scorecard/blob/main/docs/checks.md#maintained
+  schedule:
+    - cron: '35 20 * * 0'
+  push:
+    branches: [ "main" ]
+  workflow_dispatch:
+
+# Declare default permissions as read only.
+permissions: read-all
+
+jobs:
+  analysis:
+    name: Scorecard analysis
+    runs-on: ubuntu-latest
+    permissions:
+      # Needed to upload the results to code-scanning dashboard.
+      security-events: write
+      # Needed to publish results and get a badge (see publish_results below).
+      id-token: write
+      # Uncomment the permissions below if installing in a private repository.
+      # contents: read
+      # actions: read
+
+    steps:
+      - name: "Checkout code"
+        uses: actions/checkout@v4
+        with:
+          persist-credentials: false
+
+      - name: "Run analysis"
+        uses: ossf/[email protected]
+        with:
+          results_file: results.sarif
+          results_format: sarif
+          # (Optional) "write" PAT token. Uncomment the `repo_token` line below if:
+          # - you want to enable the Branch-Protection check on a *public* repository, or
+          # - you are installing Scorecard on a *private* repository
+          # To create the PAT, follow the steps in https://github.com/ossf/scorecard-action#authentication-with-pat.
+          # repo_token: ${{ secrets.SCORECARD_TOKEN }}
+
+          # Public repositories:
+          #   - Publish results to OpenSSF REST API for easy access by consumers
+          #   - Allows the repository to include the Scorecard badge.
+          #   - See https://github.com/ossf/scorecard-action#publishing-results.
+          # For private repositories:
+          #   - `publish_results` will always be set to `false`, regardless
+          #     of the value entered here.
+          publish_results: true
+
+      # Upload the results as artifacts (optional). Commenting out will disable uploads of run results in SARIF
+      # format to the repository Actions tab.
+      - name: "Upload artifact"
+        uses: actions/upload-artifact@v4
+        with:
+          name: SARIF file
+          path: results.sarif
+          retention-days: 5
+
+      # Upload the results to GitHub's code scanning dashboard.
+      - name: "Upload to code-scanning"
+        uses: github/codeql-action/[email protected]
+        with:
+          sarif_file: results.sarif

.gitignore

@@ -16,11 +16,9 @@
 *.idb
 *.pdb
 *.pyc
+.vs/
 .vscode/
 omaha/common/omaha_customization_proxy_clsid.h
 omaha/proxy_clsids.txt
-omaha/scons-out/**
-third_party/breakpad/**
-third_party/googletest/**
-third_party/libzip/**
-third_party/zlib/**
+omaha/scons-out/
+third_party/lzma/files/**/obj/

.gitmodules

@@ -0,0 +1,12 @@
+[submodule "third_party/breakpad"]
+	path = third_party/breakpad
+	url = https://github.com/google/breakpad.git
+[submodule "third_party/googletest"]
+	path = third_party/googletest
+	url = https://github.com/google/googletest.git
+[submodule "third_party/libzip"]
+	path = third_party/libzip
+	url = https://github.com/nih-at/libzip.git
+[submodule "third_party/zlib"]
+	path = third_party/zlib
+	url = https://github.com/madler/zlib.git

CHANGELOG.txt

@@ -1,3 +1,6 @@
+# CHANGELOG.txt is not going to be be updated beyond this point
+# To see what is being changed, please inspect the git log.
+
 ## 2019-06-05 @247089589,251531419
 
 ### Changes

README.md

@@ -2,8 +2,8 @@
 
 ## This is not an official Google product.
 
-Omaha is the open-source version of Google Update, a program to install requested software and keep it up to date.  The Google-branded version of Omaha is used to support software patching (both background updating, and on-demand update checks) for Google Chrome, Earth, and a variety of other Google products on Windows.
+Omaha is the open-source version of Google Update, a program to install requested software and keep it up to date.  The Google-branded version of Omaha is used to support software patching (both background updating, and on-demand update checks) for Google Chrome, Earth, and a variety of other Google products on Windows 7, 8, and 10.
 
-We know that keeping software updated is both important and hard, and so by open-sourcing this project, our hope is that perhaps we can help others solve this problem. So, if you'd like to get involved, or even use Omaha to support your own software projects, then just follow the instructions in the [Developer Setup Guide](https://github.com/google/omaha/blob/master/doc/DeveloperSetupGuide.md), and you'll be good to go!
+For a quick overview of how Omaha works, you can see [this unofficial tutorial](https://fman.io/blog/google-omaha-tutorial/). Please note that it was written by a third party so we cannot guarantee its availability, accuracy or safety.
 
-There is also an unofficial [tutorial](https://fman.io/blog/google-omaha-tutorial/). Please note that it was written by a third party so we cannot guarantee its availability, accuracy or safety.
+We know that keeping software updated is both important and hard, and so by open-sourcing this project, our hope is that perhaps we can help others solve this problem. So, if you'd like to get involved, or even use Omaha to support your own software projects, then just follow the instructions in the [Developer Setup Guide](https://github.com/google/omaha/blob/master/doc/DeveloperSetupGuide.md), and you'll be good to go!

common/certificate_tag/README

@@ -13,3 +13,9 @@ arbitrary data in extensions. Since they are also not hashed when verifying
 signatures, that data can also be changed without invalidating it.
 
 More details are here: http://b/12236017
+
+The tool was updated in 2020 to support MSI files: b/172261939, b/165818147.
+
+The test file is integrated from google3, but is modified here to make it
+easier to run outside of google3; see the comment near the beginning of
+certificate_tag_test.go