Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do we continue one more year with SSL.com for code signing #119

Open
benoit74 opened this issue Mar 3, 2025 · 1 comment
Open

Do we continue one more year with SSL.com for code signing #119

benoit74 opened this issue Mar 3, 2025 · 1 comment

Comments

@benoit74
Copy link
Collaborator

benoit74 commented Mar 3, 2025

In #88, we've decided to use SSL.com for code signin.

We've bought 1200 sign operations, and as of today 750 remains (but this year has been a bit special probably, since we've not much update WikiVoyage for instance).

Renewal will be on Jul 10, 2025 (but we need to get prepared).

Does someone has strong arguments / needs / desire to change or do we continue ?

@rgaudin
Copy link
Member

rgaudin commented Mar 3, 2025

It sure is not representative in that:

  • More than expected signatures to deploy the tools and workflows.
  • Less than expected given custom apps could not be released as usual due to missing ZIMs.

That said, we started in late August and are on a path to using 900 out of our 1,200 quota.

There is thus no forseeable risk in continuing. I'd advise we only renew for a year, hoping to have a better view next year. Given we monitor those weekly, we can still take actions should we start running low.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants