Skip to content

Closes #1019 rename ThalesIgnite/crypto11 to ThalesGroup/crypto11#1020

Open
sastorsl wants to merge 1 commit intosmallstep:masterfrom
sastorsl:fix-ThalesGroup-dependency
Open

Closes #1019 rename ThalesIgnite/crypto11 to ThalesGroup/crypto11#1020
sastorsl wants to merge 1 commit intosmallstep:masterfrom
sastorsl:fix-ThalesGroup-dependency

Conversation

@sastorsl
Copy link
Copy Markdown

@sastorsl sastorsl commented May 8, 2026

Name of feature:

N/A

Pain or issue this feature alleviates:

Missing updates on the Thales crypto11 project as they have renamed / moved their repo to a new organization on github.

Why is this important to the project (if not answered above):

The old ThalesIgnite/crypto11 repo have not received updates for quite some time.
The new ThalesGroup/crypto11 repo receives steady updates from Thales.

Is there documentation on how to use this feature? If so, where?

N/A

In what environments or workflows is this feature supported?

N/A

In what environments or workflows is this feature explicitly NOT supported (if any)?

N/A

Supporting links/other PRs/issues:

sigstore/fulcio#2329

💔Thank you!

@CLAassistant
Copy link
Copy Markdown

CLAassistant commented May 8, 2026

CLA assistant check
All committers have signed the CLA.

@sastorsl sastorsl force-pushed the fix-ThalesGroup-dependency branch from d0f0977 to 491497d Compare May 8, 2026 08:11
…pto11

Signed-off-by: Stein Arne Storslett <sastorsl@users.noreply.github.com>
@sastorsl sastorsl force-pushed the fix-ThalesGroup-dependency branch from 491497d to 0e8e81d Compare May 8, 2026 08:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants