[GH-ISSUE #90] [Change Request]: Please change the column named Signed to be StrongNamed #75

Closed
opened 2026-02-25 21:30:36 +03:00 by kerem · 1 comment
Owner

Originally created by @Smurf-IV on GitHub (Jan 20, 2023).
Original GitHub issue: https://github.com/brutaldev/StrongNameSigner/issues/90

This is to allow also checking if the binary has been actually signed with a digital certificate, which is independent of the "String naming" operation with a certificate.

Originally created by @Smurf-IV on GitHub (Jan 20, 2023). Original GitHub issue: https://github.com/brutaldev/StrongNameSigner/issues/90 This is to allow also checking if the binary has been actually `signed` with a digital certificate, which is independent of the "String naming" operation with a certificate.
kerem closed this issue 2026-02-25 21:30:36 +03:00
Author
Owner

@brutaldev commented on GitHub (Jan 21, 2023):

In the context of the application (strong-name signing) the column is not ambiguous since this has nothing to do with digital certificates or authenticode signing and it's referring to strong-name signing. Still changed it to "Strong-named" because of #91

<!-- gh-comment-id:1399314263 --> @brutaldev commented on GitHub (Jan 21, 2023): In the context of the application (strong-name signing) the column is not ambiguous since this has nothing to do with digital certificates or authenticode signing and it's referring to strong-name signing. Still changed it to "Strong-named" because of #91
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/StrongNameSigner#75
No description provided.