public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Michal Schorm <mschorm@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/mariadb-connector-c] f43: [bugfix] Declare bundled 'ed25519-ref10' in 'client_ed25519' plugin
Date: Thu, 25 Jun 2026 18:20:03 GMT	[thread overview]
Message-ID: <178241160397.1.2727261733932296927.rpms-mariadb-connector-c-24fa8eadcdf2@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/mariadb-connector-c
            Branch : f43
            Commit : 24fa8eadcdf2efbf23128e650b22d91ba97c326d
            Author : Michal Schorm <mschorm@redhat.com>
            Date   : 2026-06-24T00:40:24+02:00
            Stats  : +7/-1 in 1 file(s)
            URL    : https://src.fedoraproject.org/rpms/mariadb-connector-c/c/24fa8eadcdf2efbf23128e650b22d91ba97c326d?branch=f43

            Log:
            [bugfix] Declare bundled 'ed25519-ref10' in 'client_ed25519' plugin

The 'client_ed25519' authentication plugin bundles a modified copy of
the SUPERCOP/NaCl Ed25519 "ref10" reference implementation by
D.J. Bernstein et al. ('plugins/auth/ref10/').

The code is public domain and unversioned (SUPERCOP uses dated
snapshots, not releases; the ref10 field arithmetic has been stable
since ~2012). MariaDB's copy modifies 'sign.c': the original
'crypto_sign()' is replaced with 'ma_crypto_sign()', which takes a
password and hashes it internally instead of accepting a pre-derived
secret key. This modified API is not exposed by any system library,
so the code cannot be unbundled.

Per Fedora Packaging Guidelines, bundled libraries must be declared
even when unbundling is not possible. Also add
'LicenseRef-Fedora-Public-Domain' to the 'License' field for the
bundled public domain code.

https://docs.fedoraproject.org/en-US/packaging-guidelines/#bundling

Co-Authored-By: Claude AI <noreply@anthropic.com>

---
diff --git a/mariadb-connector-c.spec b/mariadb-connector-c.spec
index f9c801f..4755ac6 100644
--- a/mariadb-connector-c.spec
+++ b/mariadb-connector-c.spec
@@ -16,7 +16,7 @@ Name:           mariadb-connector-c
 Version:        3.4.8
 Release:        5%{?with_debug:.debug}%{?dist}
 Summary:        The MariaDB Native Client library (C driver)
-License:        LGPL-2.1-or-later AND PHP-3.0 AND PHP-3.01
+License:        LGPL-2.1-or-later AND PHP-3.0 AND PHP-3.01 AND LicenseRef-Fedora-Public-Domain
 Source:         https://archive.mariadb.org/connector-c-%{version}/%{name}-%{version}-src.tar.gz
 Source2:        my.cnf.in
 Source3:        client.cnf
@@ -38,6 +38,12 @@ BuildRequires:  libcurl-devel
 # auth_gssapi_client plugin
 BuildRequires:  krb5-devel
 
+# The client_ed25519 plugin bundles a modified copy of the SUPERCOP/NaCl
+# Ed25519 "ref10" implementation (public domain, unversioned).
+# The sign function is modified to take a password instead of a secret key.
+# Cannot be unbundled -- the connector uses the modified internal API.
+Provides:       bundled(ed25519-ref10)
+
 %description
 The MariaDB Native Client library (C driver) is used to connect applications
 developed in C/C++ to MariaDB and MySQL databases.

                 reply	other threads:[~2026-06-25 18:20 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=178241160397.1.2727261733932296927.rpms-mariadb-connector-c-24fa8eadcdf2@fedoraproject.org \
    --to=mschorm@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