Github messages for voidlinux
 help / color / mirror / Atom feed
From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: mit-krb5: update to 1.21.3, adopt
Date: Tue, 02 Jul 2024 08:52:47 +0200	[thread overview]
Message-ID: <20240702065247.6A2242132D@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-51025@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1261 bytes --]

There's a closed pull request on the void-packages repository

mit-krb5: update to 1.21.3, adopt
https://github.com/void-linux/void-packages/pull/51025

Description:
I use this package together with openldap which I adopted recently.

One thing I would like to do with this package when I have the time is to convert the build options to separate subpackages instead which would make them easier to use without rebuilding locally.
Another thing to look at is that currently the package uses the Berkely DB library from the distro, which in the build instructions at https://web.mit.edu/kerberos/krb5-latest/doc/build/options2configure.html is marked as unsupported. This could perhaps also be resolved by recommending to use the LMDB backend instead which I believe does not have this problem.

Relevant changes:
- Fix vulnerabilities in GSS message token handling [CVE-2024-37370, CVE-2024-37371].
- Fix a potential bad pointer free in krb5_cccol_have_contents()

#### Testing the changes
- I tested the changes in this PR: **briefly**

#### Local build testing
- I built this PR locally for my native architecture, (x86_64, x86_64-musl)
- I built this PR locally for these architectures:
  - aarch64-musl
  - armv7l
  - armv6l-musl
  - i686

      reply	other threads:[~2024-07-02  6:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-27 13:21 [PR PATCH] " klarasm
2024-07-02  6:52 ` classabbyamp [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240702065247.6A2242132D@inbox.vuxu.org \
    --to=classabbyamp@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).