Add content interface to snap for sharing aziot_keys.so #645
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
arsing
approved these changes
Dec 16, 2024
damonbarry
force-pushed
the
snap-content-interface
branch
from
ea01601 to
91c3db6
Compare
This reverts commit fd9c1cb.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Our snap does not allow dependent snaps to access aziot_keys.so, so they cannot use our OpenSSL engine library for mTLS when their client certificate's private key is backed by our key store. This change adds a content interface for the $SNAP/lib/engines-3 folder, where aziot_keys.so lives.