edugain-discuss AT lists.geant.org
Subject: An open discussion list for topics related to the eduGAIN interfederation service.
List archive
Re: [eduGAIN-discuss] Post-Quantum readiness and crypto-agility for federation aggregates
Chronological Thread
- From: Emmanuel Togo <ematogo AT garnet.edu.gh>
- To: Stefan Winter <stefan.winter AT restena.lu>, "edugain-discuss AT lists.geant.org" <edugain-discuss AT lists.geant.org>
- Subject: Re: [eduGAIN-discuss] Post-Quantum readiness and crypto-agility for federation aggregates
- Date: Tue, 3 Nov 2026 12:25:07 +0000
- Accept-language: en-GB, en-US
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=garnet.edu.gh; dmarc=pass action=none header.from=garnet.edu.gh; dkim=pass header.d=garnet.edu.gh; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=AvV+dYePPT+vl5K4BF3v5uogcc/ZqU+Ei9EBcss0Msg=; b=wJX0qRj2uzB1efoRDyzjfZ28UQPA4eUbEDhrTipE0O/MF60xp9ZLRrVoWtF73ZQHieaCiJR8Wz0j8RO7eYnCOvYxy/IfNMdx384dcfcJW7pTuc9rcyL0eiSB9j+tg1S8DveRKuLKu8NLq/qsz2sFEath1JVUqY3u9LrWjP4tJffOa/ic+XUdnqtr+o7Vc3vh2St9Qj74KE9LQMMSoARgZOtmV/u8ibn/GEQNZLr7977lyyktB57b/6ApMTUq2sJvPwHUPTqwN52N83BMalwBAsVxlwdJpAbT0Lox3NSvbLBjzPxiOytF+G2VZhbmMxiBeQG8BOZSTIyjssAyd1iiBA==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=hAHwAtBfR8EG3k4o7ftnK9oXWoyR43m0yFdbjf5xrOoSo8Ny9qOlY8fT3tZ917WspgKza1rNr1GHW77VsOsrz3kzJT2h6OiOo+fKqUGzRUHeL8rVek07vJ8wNRcSbJx7uRGyVZr2CoORgJuUbuCsMug6T1n+qkpbFTHXRnfGkTT4JwXYT88fDZ/VgHQzO28pgyLyVGyxBG+tmEJe5elKskgAV0VOxDz0a5CuJ90RXugVtJIPzH/OT9jTlWBCSTAUg0R5+4HvNEu0QYrlkIwxgPNfyrd+xtL33O2/RmcYYcIQbK5BGL1iTp1Dz3h2Ilw0fKzdCPcShCcrf4K6jNIpfQ==
- Authentication-results: mail.geant.org; dkim=pass (2048-bit key; unprotected) header.d=garnet.edu.gh header.i= AT garnet.edu.gh header.a=rsa-sha256 header.s=selector1 header.b=bziHyJqQ; dkim-atps=neutral
- Authentication-results: mx.microsoft.com 1; dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=garnet.edu.gh;
Sent from
Outlook for Android2
From: edugain-discuss-request AT lists.geant.org <edugain-discuss-request AT lists.geant.org> on behalf of Stefan Winter <edugain-discuss AT lists.geant.org>
Sent: Tuesday, 03 November 2026 11:00:13
To: edugain-discuss AT lists.geant.org <edugain-discuss AT lists.geant.org>
Subject: [eduGAIN-discuss] Post-Quantum readiness and crypto-agility for federation aggregates
Sent: Tuesday, 03 November 2026 11:00:13
To: edugain-discuss AT lists.geant.org <edugain-discuss AT lists.geant.org>
Subject: [eduGAIN-discuss] Post-Quantum readiness and crypto-agility for federation aggregates
Hello!
A recent discussion on federation metadata signature requirements
(require larger RSA keys soon) got me thinking about whether RSA still
has enough of a future ahead that it is worth "just" increasing key
sizes for federations that are below the cut.
Current recommendations regarding post-quantum readiness rather suggest
to move away from RSA entirely.
Unfortunately, it is less clear where to move *to* instead. ECDSA is on
the same way out that RSA is. PQC algorithms exist but they are
relatively new and it is not unthinkable that one or some will not stand
the test of time.
In these uncertain times, eduID Luxembourg is taking a step towards PQC,
while adding "crypto-agility" where there was none before.
From now on, we are publishing our federation aggregate with four
distinct signature algorithms: RSA/4096 bit, ECDSA/NIST P-521 curve,
ML-DSA/87 and SLH-DSA/256s. You can find our aggregates here:
https://restena.lu/en/document/354-implement-eduid-metadata
This is maybe not crypto-agile in a classic reading - every signature
stands on its own, with no relation to the others. But:
* as new algorithms become customary, we can simply enlarge the list;
* if an algorithm falls from cryptographers' grace, it can simply be
removed;
* all variants have identical content except for the <ds:Signature>
element. In case any subset of algorithms is /actually/ compromised and
used to sign bogus federation metadata, this becomes detectable by
comparing all four aggregate files and observing that there is a
difference in the payload.
To my knowledge, eduGAIN OT is already working on the ability to
validate all signature variants; if they were to add a four-way
comparison of all the file contents, we could consider this a full
PQC-ready crypto-agile setup.
Happy to hear your thoughts on this.
Greetings,
Stefan Winter
A recent discussion on federation metadata signature requirements
(require larger RSA keys soon) got me thinking about whether RSA still
has enough of a future ahead that it is worth "just" increasing key
sizes for federations that are below the cut.
Current recommendations regarding post-quantum readiness rather suggest
to move away from RSA entirely.
Unfortunately, it is less clear where to move *to* instead. ECDSA is on
the same way out that RSA is. PQC algorithms exist but they are
relatively new and it is not unthinkable that one or some will not stand
the test of time.
In these uncertain times, eduID Luxembourg is taking a step towards PQC,
while adding "crypto-agility" where there was none before.
From now on, we are publishing our federation aggregate with four
distinct signature algorithms: RSA/4096 bit, ECDSA/NIST P-521 curve,
ML-DSA/87 and SLH-DSA/256s. You can find our aggregates here:
https://restena.lu/en/document/354-implement-eduid-metadata
This is maybe not crypto-agile in a classic reading - every signature
stands on its own, with no relation to the others. But:
* as new algorithms become customary, we can simply enlarge the list;
* if an algorithm falls from cryptographers' grace, it can simply be
removed;
* all variants have identical content except for the <ds:Signature>
element. In case any subset of algorithms is /actually/ compromised and
used to sign bogus federation metadata, this becomes detectable by
comparing all four aggregate files and observing that there is a
difference in the payload.
To my knowledge, eduGAIN OT is already working on the ability to
validate all signature variants; if they were to add a four-way
comparison of all the file contents, we could consider this a full
PQC-ready crypto-agile setup.
Happy to hear your thoughts on this.
Greetings,
Stefan Winter
- [eduGAIN-discuss] Post-Quantum readiness and crypto-agility for federation aggregates, Stefan Winter, 03-Nov-2026
- Re: [eduGAIN-discuss] Post-Quantum readiness and crypto-agility for federation aggregates, Emmanuel Togo, 11/03/2026
- Re: [eduGAIN-discuss] Post-Quantum readiness and crypto-agility for federation aggregates, Muhammad Farhan SJAUGI, 03-Nov-2026
- Re: [eduGAIN-discuss] Post-Quantum readiness and crypto-agility for federation aggregates, Stefan Winter, 03-Nov-2026
- Re: [eduGAIN-discuss] Post-Quantum readiness and crypto-agility for federation aggregates, Scott Cantor, 03-Nov-2026
Archive powered by MHonArc 2.6.19+.
