With the new security consideration in mind, how does one validate code signing of assembies merged
- Dominant language
- No language data
- Stars
- 4.8k
- Forks
- 6.1k
- Avg merge
- 15h 21m
- Merged PRs (30d)
- 370
Description
with the PublishSingleFile being enabled and optionally compression how does one know if the assemblies are code signed and how can one access the codesign data opening the certificate using code will not work:
`System.Security.Cryptography.X509Certificates.X509Certificate.CreateFromSignedFile(Assembly.Location)`
How does one validate the certificate from embedded assemblies?
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: e1932751-7c2b-ce92-936e-e97f8581d5fa
* Version Independent ID: de677d1f-386a-e4c3-fdd0-6806b3ef2c0e
* Content: [Single file application - .NET](https://docs.microsoft.com/en-us/dotnet/core/deploying/single-file?source=docs)
* Content Source: [docs/core/deploying/single-file.md](https://github.com/dotnet/docs/blob/main/docs/core/deploying/single-file.md)
* Product: **dotnet-fundamentals**
* GitHub Login: @LakshanF
* Microsoft Alias: **lakshanf**
Contributor guide
Assessment
This issue has not been assessed yet.