ILSpy

94 Tags

91 MiB

Tree: 44cb31abae

Author	SHA1	Message	Date
Siegfried Pammer	67533d767f	Compute public-key tokens with a managed SHA-1 On FIPS-mode systems the platform crypto provider refuses to create SHA-1 instances (OpenSSL: error:03000098 invalid digest), so merely displaying a strong-named assembly's identity failed. The public-key token is a non-secret identity hash whose algorithm is fixed by ECMA-335, so the two token sites now use dotnet/runtime's managed Sha1ForNonSecretPurposes, vendored with its license header intact and shielded from the repo formatter via generated_code in .editorconfig so future upstream syncs diff cleanly. IncrementalHash was considered and rejected: like SHA1.Create(), it resolves the digest through the host crypto policy, and Roslyn's equivalent token code also relies on the platform SHA-1, so it offers no precedent for FIPS safety. Assisted-by: Claude:claude-fable-5:Claude Code	3 months ago
Peter Crabtree	e1e16b64f5	dev: Strip BOM mark from text files	1 year ago
Christoph Wille	b1a4ab15c4	Fix NETCORE to NET8(or newer) directive	2 years ago
Daniel Grunwald	e84df3ff20	Move BitOperations to namespace System.Numerics.	3 years ago
Siegfried Pammer	09691bd27e	#3075 : Add NextSetBit operation to BitSet to avoid looking at every store bit individually in ReachingDefinitionsVisitor.GetStores()	3 years ago