-
Notifications
You must be signed in to change notification settings - Fork 608
Add security section #89
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -143,7 +143,7 @@ the container. For more information, see the [kernel cgroups documentation](http | |
| ## Linux capabilities | ||
|
|
||
| Capabilities is an array that specifies Linux capabilities that can be provided to the process | ||
| inside the container. Valid values are the string after `CAP_` for capabilities defined | ||
| inside the container. Valid values are the string after `CAP_` for capabilities defined | ||
| in [the man page](http://man7.org/linux/man-pages/man7/capabilities.7.html) | ||
|
|
||
| ```json | ||
|
|
@@ -208,7 +208,39 @@ rootfsPropagation sets the rootfs's mount propagation. Its value is either slave | |
| "rootfsPropagation": "slave", | ||
| ``` | ||
|
|
||
| ## Security | ||
| ## Selinux process label | ||
|
|
||
| **TODO:** security profiles | ||
| Selinux process label specifies the label with which the processes in a container are run. | ||
| For more information about SELinux, see [Selinux documentation](http://selinuxproject.org/page/Main_Page) | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. A more specific link would be nice. It might be obvious to SELinux users (I'm not one), but the main page didn't say anything about process labels. |
||
| ```json | ||
| "selinuxProcessLabel": "system_u:system_r:svirt_lxc_net_t:s0:c124,c675" | ||
| ``` | ||
|
|
||
| ## Apparmor profile | ||
|
|
||
| Apparmor profile specifies the name of the apparmor profile that will be used for the container. | ||
| For more information about Apparmor, see [Apparmor documentation](https://wiki.ubuntu.com/AppArmor) | ||
|
|
||
| ```json | ||
| "apparmorProfile": "acme_secure_profile" | ||
| ``` | ||
|
|
||
| ## Seccomp | ||
|
|
||
| Seccomp provides application sandboxing mechanism in the Linux kernel. | ||
| Seccomp configuration allows one to configure actions to take for matched syscalls and furthermore also allows | ||
| matching on values passed as arguments to syscalls. | ||
| For more information about Seccomp, see [Seccomp kernel documentation](https://www.kernel.org/doc/Documentation/prctl/seccomp_filter.txt) | ||
| The actions and operators are strings that match the definitions in seccomp.h from [libseccomp](https://github.com/seccomp/libseccomp) and are translated to corresponding values. | ||
|
|
||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. There are two seccomp.h that are visible to users. One is exported by linux kernel and the other is defined by libseccomp. I think we should mention libseccomp? |
||
| ```json | ||
| "seccomp": { | ||
| "defaultAction": "SCMP_ACT_ALLOW", | ||
| "syscalls": [ | ||
| { | ||
| "name": "getcwd", | ||
| "action": "SCMP_ACT_ERRNO" | ||
| } | ||
| ] | ||
| } | ||
| ``` | ||
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.
I think this would read easier as: