Skip to content
This repository has been archived by the owner on Jul 14, 2021. It is now read-only.

Adding entitlement for unsigned memory execution #2748

Merged
merged 1 commit into from
Feb 2, 2020

Conversation

jonsmorrow
Copy link
Contributor

@jonsmorrow jonsmorrow commented Feb 2, 2020

Description

ffi loads c code into memory in an unsigned way and this allows dk
to work with the hardened runtime.

Signed-off-by: Jon Morrow jmorrow@chef.io

Related Issue

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Chore (non-breaking change that does not add functionality or fix an issue)

Checklist:

  • I have read the CONTRIBUTING document.
  • I have run the pre-merge tests locally and they pass.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • All new and existing tests passed.
  • All commits have been signed-off for the Developer Certificate of Origin.

ffi loads c code into memory in an unsigned way and this allows workstation
to work with the hardened runtime.

Signed-off-by: Jon Morrow <jmorrow@chef.io>
@jonsmorrow jonsmorrow requested review from a team as code owners February 2, 2020 00:09
@jonsmorrow
Copy link
Contributor Author

@tas50 tas50 merged commit 0927944 into master Feb 2, 2020
@chef-expeditor chef-expeditor bot deleted the jm/add_unsigned_memory_entilement branch February 2, 2020 23:50
@tas50
Copy link
Contributor

tas50 commented Feb 2, 2020

@jonsmorrow Can you make sure to backport the notarization and entitlement stuff to the dk3 branch as well.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants