Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge 3.0-dev into 3.0 #9473

Merged
merged 41 commits into from
Jun 24, 2024
Merged

Merge 3.0-dev into 3.0 #9473

merged 41 commits into from
Jun 24, 2024

Conversation

anphel31
Copy link
Member

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

  • The toolchain has been rebuilt successfully (or no changes were made to it)
  • The toolchain/worker package manifests are up-to-date
  • Any updated packages successfully build (or no packages were changed)
  • Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
  • Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
  • All package sources are available
  • cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
  • LICENSE-MAP files are up-to-date (./SPECS/LICENSES-AND-NOTICES/data/licenses.json, ./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md, ./SPECS/LICENSES-AND-NOTICES/LICENSE-EXCEPTIONS.PHOTON)
  • All source files have up-to-date hashes in the *.signatures.json files
  • sudo make go-tidy-all and sudo make go-test-coverage pass
  • Documentation has been updated to match any changes to the build system
  • If you are adding/removing a .spec file that has multiple-versions supported, please add @microsoft/cbl-mariner-multi-package-reviewers team as reviewer (Eg. golang has 2 versions 1.18, 1.21+)
  • Ready to merge

Summary

What does the PR accomplish, why was it needed?

Change Log
  • Change
  • Change
  • Change
Does this affect the toolchain?

YES/NO

Associated issues
  • #xxxx
Links to CVEs
Test Methodology
  • Pipeline build id: xxxx

mandeepsplaha and others added 30 commits June 12, 2024 11:00
Co-authored-by: minghe <rmhsawyer>
Change #7761 upgraded shadow-utils and took part of a change from upstream that modifies /etc/login.defs so that USERGROUPS_ENAB is set to no. This makes all users be created in the same group (in our case users) rather than created with their own group.

This change undoes that, so users will once again be created with their own group with the same name as the user.
LLMNR poisoning is a MitM attack used to capture credential material by tampering with LLMNR request and response messages.

To prevent LLMNR poisoning, disable LLMNR in systemd. LLMNR is actively being phased out in favor of mDNS.

Signed-off-by: Chris Co <[email protected]>
nicogbg and others added 11 commits June 19, 2024 16:06
Co-authored-by: CBL-Mariner Servicing Account <[email protected]>
Azure Linux's primary supported container runtime is containerd. We will provide CRI-O as an option for users to try, but will be community maintained in the Extended repository.

Signed-off-by: Chris Co <[email protected]>
Renaming package name argparse-manpage -> python-argparse-manpage

To be consistent, all python pypi modules are named python- the
package argparse-manpage does not follow this convention, updating base
package name to be consistent.
@anphel31 anphel31 requested review from a team as code owners June 23, 2024 21:40
@anphel31 anphel31 merged commit bb57b03 into 3.0 Jun 24, 2024
12 checks passed
@anphel31 anphel31 deleted the anphel/3-pull-dev-changes-jun-23 branch June 24, 2024 16:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.