-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: fixup paths for selinux #547
chore: fixup paths for selinux #547
Conversation
Can you also update the example on https://github.com/fedora-iot/fido-device-onboard-rs/blob/main/HOWTO.md?plain=1#L448-L454 and add a comment on https://github.com/fedora-iot/fido-device-onboard-rs/blob/main/HOWTO.md?plain=1#L493-L494 ? |
9a7683a
to
728da9a
Compare
fixed, should be good now |
You can cherry-pick the commit from #548 (or we can merge and rebase) to make the clippy test pass |
Using the service-info-api server with selinux requires us to put anything we want to send to the device under /var/lib/fdo as that directory, and its files, will now get the correct selinux label. The previous approach opens up for security issues by leaving the process basically accessing the whole host. Signed-off-by: Antonio Murdaca <[email protected]>
Signed-off-by: Irene Diez <[email protected]>
728da9a
to
98e9479
Compare
done |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
Using the service-info-api server with selinux requires us to put anything we want to send to the device under /var/lib/fdo as that directory, and its files, will now get the correct selinux label. The previous approach opens up for security issues by leaving the process basically accessing the whole host.