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

[Snyk] Upgrade kerberos from 2.0.1 to 2.2.0 #106

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

MedNoun
Copy link
Owner

@MedNoun MedNoun commented Oct 15, 2024

Snyk has created this PR to upgrade kerberos from 2.0.1 to 2.2.0.

As this is a private repository, Snyk-bot does not have access. Therefore, this PR has been created automatically, but appears to have been created by a real user.

✨ Snyk has automatically assigned this pull request, set who gets assigned.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 7 versions ahead of your current version.
  • The recommended version was released a month ago, on 2024-09-11.
Release notes
Package name: kerberos
  • 2.2.0 - 2024-09-11

    2.2.0 (2024-09-05)

    The MongoDB Node.js team is pleased to announce version 2.2.0 of the kerberos package!

    Release Notes

    protect is now an option for KerberosClient.wrap()

    protect can be provided to KerberosClient.wrap(). When configured, wrapped message will be encrypted.

    Thanks @ arabull for this contribution!

    Features

    Documentation

    We invite you to try the kerberos library immediately, and report any issues to the NODE project.

  • 2.1.2 - 2024-08-12

    2.1.2 (2024-08-12)

    The MongoDB Node.js team is pleased to announce version 2.1.2 of the kerberos package!

    Release Notes

    MacOS builds reverted to use dynamic linking

    We recently made runtime linking with system kerberos libraries (#165) the default for Linux and MacOS (#188) platforms due to the fact that system kerberos libraries often link against the system SSL library. However, Node.js ships with it's own SSL library, and having both loaded when they are different versions would crash the addon. Inadvertently this did not work as intended on MacOS, so we're reverting the change for that platform, other platforms are unaffected.

    Bug Fixes

    Documentation

    We invite you to try the kerberos library immediately, and report any issues to the NODE project.

  • 2.1.1 - 2024-08-06

    2.1.1 (2024-07-16)

    The MongoDB Node.js team is pleased to announce version 2.1.1 of the kerberos package!

    Release Notes

    Fix segfault when running kerberos on systems with 1.x OpenSSL versions and Node.js 18+

    Kerberos depends on OpenSSL and Node.js always bundles a copy of OpenSSL. Unfortunately an incompatiblity arises when Node's SSL version is not compatible with the version that the system kerberos library was built with.

    Kerberos will now load the system library by default with runtime dynamic linking. This enables us to specify that kerberos use the SSL version it was built against (RTLD_DEEPBIND) so it does not adopt the symbols available in Node.js' address space.

    Starting in Node 18+ these Node's SSL symbols are from OpenSSL 3+, whereas on RHEL 8 the system SSL library is 1.1.1k.

    Add Spectre Mitigation and Control Flow Guard

    On Windows only, we have added the SpectreMitigation and /guard:cf flags, thanks to a contribution from @ rzhao271! If you are building on Windows yourself you may need to install Spectre-mitigated libraries for Visual Studio. Those using the prebuilds should not need any changes.

    MacOS universal builds

    In a previous PR we made our MacOS prebuilds be universal binaries so the same build works on both M1 and Intel. This PR moves the universal build flags under a condition so that when building a static library only the platform being built for is included.

    Bug Fixes

    Documentation

    We invite you to try the kerberos library immediately, and report any issues to the NODE project.

  • 2.1.1-alpha.0 - 2024-06-28

    2.1.1-alpha.0 (2024-06-28)

    The MongoDB Node.js team is pleased to announce version 2.1.1-alpha.0 of the kerberos package!

    Release Notes

    Bug Fixes

    Documentation

    We invite you to try the kerberos library immediately, and report any issues to the NODE project.

  • 2.1.0 - 2023-11-21

    The MongoDB Node.js team is pleased to announce version 2.1.0 of the kerberos package!

    Features

    • NODE-5746: The kerberos library now provides the ability to build from source to use a runtime linked system kerberos library. To enable this flag use GYP_DEFINES='kerberos_use_rtld=true' npm i --build-from-source

    We invite you to try the kerberos library immediately, and report any issues to the NODE project.

  • 2.0.3 - 2023-09-12

    The MongoDB Node.js team is pleased to announce version 2.0.3 of the kerberos package!

    Features

    • NODE-5600: Resolves glibc compatibility issues. This fixes issues installing 2.0.2 on Node 16 due to the glibc requirement being too high.

    We invite you to try the kerberos library immediately, and report any issues to the NODE project.

  • 2.0.2 - 2023-08-29

    The MongoDB Node.js team is pleased to announce version 2.0.2 of the kerberos package!

    Features

    • NODE-5505: Resolves compiler warnings and downstream BinSkim issues, fixes string length casts on username.

    We invite you to try the kerberos library immediately, and report any issues to the NODE project.

  • 2.0.1 - 2022-07-14

    The MongoDB Node.js team is pleased to announce version 2.0.1 of the kerberos package!

    Bug Fixes

    • NODE-4297: Update version of prebuild-install to v7.1.1

    We invite you to try the kerberos library immediately, and report any issues to the NODE project.

from kerberos GitHub release notes
Commit messages
Package name: kerberos
  • c35b125 chore(main): release 2.2.0 [skip-ci] (#204)
  • 515f4bf feat(NODE-6333): Allow callers to specify the 'protect' flag (#198)
  • 281d076 ci(NODE-6359): specify build-from-source once (#203)
  • 9854213 ci(NODE-6359): actually run tests in CI (#202)
  • 28eada5 docs(NODE-6339): update README testing section (#199)
  • b13c729 chore(NODE-6271): update dev deps and add dependabot config (#192)
  • 919afbe chore(NODE-6322): fix codeQL CI checks (#195)
  • 21a1496 chore(main): release 2.1.2 [skip-ci] (#194)
  • d382b56 fix(NODE-6320): macos runtime linking name conflict with SSL (#193)
  • c2acb18 chore(main): release 2.1.1 [skip-ci] (#187)
  • 3487a52 chore: prepare for non-prerelease (#191)
  • 54b9799 fix(NODE-6265): add Spectre Mitigation and CFG (#190)
  • 04044d2 fix(NODE-6253): use runtime linking against system kerberos libraries by default (#188)
  • ec3ab7a fix(MONGOSH-1808): only build universal macos binaries when creating loadable_library (#186)
  • 65573c7 chore(main): release 2.1.1-alpha.0 [skip-ci] (#185)
  • a39dfcb fix: release versioning (#184)
  • 6edb909 chore: Release-As: 2.1.1-alpha.0 (#183)
  • dc46555 chore: specify ignore-scripts in all GHA when setting up dependencies (#182)
  • 7252848 chore(main): release 2.1.1-alpha (#175)
  • 08f0eca chore: prepare for alpha of kerberos (#181)
  • 7bbb22c chore: remove extra steps from release action (#180)
  • 36b0da7 chore: full SSDLC compliance workflow (#179)
  • 2e71058 chore(NODE-6212): generate sarif report and upload sbom file to s3 (#178)
  • 658c858 chore(NODE-6178): enable codeql scans (#176)

Compare


Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

👩‍💻 Set who automatically gets assigned

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

@MedNoun MedNoun self-assigned this Oct 15, 2024
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.

2 participants