Bug 35670 - ProtectedData throws CryptographicException in OS X El Capitan
Summary: ProtectedData throws CryptographicException in OS X El Capitan
Status: NEW
Alias: None
Product: Class Libraries
Classification: Mono
Component: System.Security ()
Version: master
Hardware: Macintosh Mac OS
: Normal normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2015-11-08 19:12 UTC by john
Modified: 2015-12-23 04:21 UTC (History)
3 users (show)

Tags:
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 for Bug 35670 on GitHub or Developer Community if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: GitHub Markdown or Developer Community HTML
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:
Status:
NEW

Description john 2015-11-08 19:12:09 UTC
In OS X El Capitan, ProtectedData in per-machine scope will throw exception, complaining
"Could not create machine key store '/usr/share/.mono/keypairs'."

Following code can reproduce in Mono MDK 4.0.4.4, or, in Mono Preview package for El Capitan (4.2.1)


//
//
using System;
using System.Security.Cryptography;

static class Program
{
    static void Main()
    {
        byte[] bytes = ProtectedData.Protect(new byte[]{1,2,3}, new byte[] { 1, 2, 3 },DataProtectionScope.LocalMachine);
    }
}
Comment 1 john 2015-11-08 19:22:05 UTC
Once the 'System Integrity Protection' is disabled, the ProtectedData.Protect() call will succeed. 

Once the 'keypairs' was created (I assume), the ProtectedData.Protect() and ProtectedData.Unprotect() calls are OK, even when the 'System Integrity Protection' is turned on again.
Comment 2 Ross 2015-11-11 16:09:35 UTC
How about:
- Write the keypairs to a new location that 'System Integrity Protection' allows.
- Add fallback read logic which first attempts to load the keys from the new location, and if not found reads from the original location, maintaining backwards compatibility.