Commit Graph

4 Commits

Author SHA1 Message Date
duraki
1a23054800 Enables CAN networking subsystem (introduced Linux 2.6.25 2008-04-17), to
support SPI in container environment (introduced Linux 4.12 2017-06-02).

Abstraction define interface EP for CAN module in containered environment. This
namespace is available and introduced with Linux Kernel 4.12 by M.  Kicherer
and later O. Hartkopp, to allow containers bridging such device.

@see linux-kernel/net/can@fc4c581

Although KSPP did not explicilty noted `CAN` as secure kernel flag, this
would aim to bring such conclusion. As for security concerns, CAN protocol did
not yield any user-land or host-level vulnerabilities since introduced as
SocketCAN module in Linux Kernel. Lower-layer [protocol] standards is not
secured by default since applications are supposed to implement their own
security mechanism.

This global abstraction currently supports CAN raw, proc and af_can
codes. Does not support GW and BCM. Namespace uses _NEWNET on pseudo-file
system.  Allows modprobe to environment, works by recv `pnet` for the given
interface.

Signed-off-by: Halis Duraki <duraki@linuxmail.org>
2018-08-31 13:22:19 +02:00
Jose Carlos Venegas Munoz
f2569c0e75 clear-containers: Enable kernel security options used by moby
Signed-off-by: Jose Carlos Venegas Munoz <jose.carlos.venegas.munoz@intel.com>
2017-04-14 09:26:10 +00:00
Jose Carlos Venegas Munoz
844f058689 clear-containers: enable PAGE POISONING ZERO
Signed-off-by: Jose Carlos Venegas Munoz <jose.carlos.venegas.munoz@intel.com>
2017-04-14 09:26:04 +00:00
Jose Carlos Venegas Munoz
2b1fb70f35 projects: Add Clear Containers intial support
Signed-off-by: Jose Carlos Venegas Munoz <jose.carlos.venegas.munoz@intel.com>
2017-04-14 09:23:37 +00:00