Merged
Conversation
jkaczman
force-pushed
the
remove-openssl-from-camera-hub
branch
2 times, most recently
from
efc7af9 to
d2bb0e1
Compare
jkaczman
changed the title
…olchain container
migrated from old migrate-ssl PR
…' binary name for raspberry
… credentials during post-check
jkaczman
force-pushed
the
remove-openssl-from-camera-hub
branch
from
cfe3f71 to
642955c
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
TODO... fixes #48
Use Secluso OS within the deploy tool
[1] Do not use OpenSSL within the Camera Hub binary. Instead, link to Onnx Runtime through the dylib initialization scheme.
[2] Inject camera_secret and wifi_password into the /provision partition of the image.
[3] Modify release scheme to use top-level signatures and only have camera_hub/server binaries in the released runtime binaries.