public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Michael Catanzaro <mcatanzaro@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/glib2] cve-2026-58016-f44: Fix gnutls-hmac.patch
Date: Tue, 11 Aug 2026 10:37:43 GMT	[thread overview]
Message-ID: <178644466363.1.7044837262815741493.rpms-glib2-75642e63a78d@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/glib2
Branch : cve-2026-58016-f44
Commit : 75642e63a78d501ce03f09db182aa50acd4f78cc
Author : Michael Catanzaro <mcatanzaro@redhat.com>
Date   : 2022-07-14T18:03:02-05:00
Stats  : +3/-3 in 1 file(s)
URL    : https://src.fedoraproject.org/rpms/glib2/c/75642e63a78d501ce03f09db182aa50acd4f78cc?branch=cve-2026-58016-f44

Log:
Fix gnutls-hmac.patch

---
diff --git a/gnutls-hmac.patch b/gnutls-hmac.patch
index 8274810..16b02b7 100644
--- a/gnutls-hmac.patch
+++ b/gnutls-hmac.patch
@@ -1025,15 +1025,15 @@ index 3ac3206df..2fa447984 100644
 +  GHmac *copy;
 +
 +  /* No MD5 in FIPS mode. */
-+  hmac = g_hmac_new (G_CHECKSUM_MD5, "abc123", sizeof ("abc123"));
++  hmac = g_hmac_new (G_CHECKSUM_MD5, (guchar *)"abc123", sizeof ("abc123"));
 +  g_assert_null (hmac);
 +
 +  /* SHA-256 should be good. */
-+  hmac = g_hmac_new (G_CHECKSUM_SHA256, "abc123", sizeof ("abc123"));
++  hmac = g_hmac_new (G_CHECKSUM_SHA256, (guchar *)"abc123", sizeof ("abc123"));
 +  g_assert_nonnull (hmac);
 +
 +  /* Ensure g_hmac_update() does not crash when called with -1. */
-+  g_hmac_update (hmac, "You win again, gravity!", -1);
++  g_hmac_update (hmac, (guchar *)"You win again, gravity!", -1);
 +
 +  /* Ensure g_hmac_copy() does not crash. */
 +  copy = g_hmac_copy (hmac);

                 reply	other threads:[~2026-08-11 10:37 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=178644466363.1.7044837262815741493.rpms-glib2-75642e63a78d@fedoraproject.org \
    --to=mcatanzaro@redhat.com \
    --cc=git-commits@fedoraproject.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