Bug 40646 - Oid and FriendlyName for sha384
Summary: Oid and FriendlyName for sha384
Alias: None
Product: Class Libraries
Classification: Mono
Component: System.Security ()
Version: master
Hardware: PC Windows
: --- normal
Target Milestone: Untriaged
Assignee: Marek Safar
Depends on:
Reported: 2016-04-22 19:57 UTC by Hin-Tak Leung
Modified: 2016-05-05 07:20 UTC (History)
2 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on GitHub or Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Hin-Tak Leung 2016-04-22 19:57:32 UTC

around line 115, have sha256 and sha512, but not sha384.

The needed addition is simply these two lines:

		internal const string oidSha384 = "2.16.840.";
		internal const string nameSha384 = "sha384";

I filed and mentioned this, because sha384 is the last of the 5 which does not currently has a Oid/FriendlyName mapping in mono, of all the valid inputs to HashAlgorithm.Create()
Comment 1 Marek Safar 2016-05-05 07:20:09 UTC
Fixed in master