Age | Commit message (Collapse) | Author |
|
Enable SHA256, SHA384 and SHA512 hash algorithms to be used for
Authenticode signatures. This enables producing digital signatures that
are trustworthy using the `mono` tooling.
Fixes #7517
|
|
MD5 is considered insecure and switching the default to SHA1 should be better for everyone.
See the discussion on the mailing list: http://lists.ximian.com/pipermail/mono-devel-list/2015-December/043424.html
|
|
svn path=/trunk/mono/; revision=50638
|
|
svn path=/trunk/mono/; revision=39203
|
|
* chktrust.1: Added some details and documented the CAB format
restriction (not supported).
* makecert.1: Added missing options, details for existing options and
removed duplicate options.
* setreg.1: Minor changes.
* signcode.1: Added some details and documented the CAB format
restriction (not supported). Also added a warning when using both a
strongname and an Authenticode signature on a assembly.
svn path=/trunk/mono/; revision=25253
|
|
* chktrust.1: New. Man page for Authenticode chktrust.exe
* signcode.1: New. Man page for Authenticode signcode.exe
* sn.1: New. Man page for StrongName sn.exe
* man.xml: Added new (and missing) entries.
svn path=/trunk/mono/; revision=18911
|