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

[Code Signing Certificate]: Reactive Extensions for .NET (Rx.NET) #387

Open
5 of 6 tasks
idg10 opened this issue Jul 18, 2024 · 3 comments
Open
5 of 6 tasks

[Code Signing Certificate]: Reactive Extensions for .NET (Rx.NET) #387

idg10 opened this issue Jul 18, 2024 · 3 comments
Assignees
Labels
project support Use this label to request support for an existing .NET Foundation project triage The item has yet to be reviewed

Comments

@idg10
Copy link

idg10 commented Jul 18, 2024

Project Name

Reactive Extensions for .NET

LastPass Email

[email protected]

Onboarding Checklist

  • Register trade name @ChrisSfanos
  • Create configuration in Code Signing Service
  • Create organization with DigiCert
  • Request certificate from DigiCert
  • Received certificate and finalize sign service configuration
  • Provide credentials in shared folder in LastPass
@idg10 idg10 added project support Use this label to request support for an existing .NET Foundation project triage The item has yet to be reviewed labels Jul 18, 2024
@idg10
Copy link
Author

idg10 commented Jul 18, 2024

The Reactive Extensions for .NET project (https://github.com/dotnet/reactive) has not yet been updated to use the new(ish) sign tool. Apparently the old one continued to work for us as recently as May this year, so we hadn't actually got around to updating.

But we're now getting 500 server errors when we run the old tool, which is has finally reminded me that I never got around to doing this.

I'm looking at https://github.com/dotnet-foundation/wg-maintainers/issues/90 for guidance, and it says I need to ask for project support to kick the process off. Presumably I'm going to need different credentials than the ones we've been using with the old signing tool.

I see that apparently even fairly recent updates to projects already doing this are using preview versions of the tool:

https://github.com/dotnet/aspnet-api-versioning/blob/3fc071913dcded23eeb5ebe55bca44f3828488bf/.config/dotnet-tools.json#L6

@ChrisSfanos
Copy link
Collaborator

Hi Ian
Sorry for the delay - let me email you in a bit with the new signing info (and I'll check the status of your certificate expiration)

@glennawatson
Copy link
Collaborator

Is this solved now @idg10 ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
project support Use this label to request support for an existing .NET Foundation project triage The item has yet to be reviewed
Projects
None yet
Development

No branches or pull requests

3 participants