aboutsummaryrefslogtreecommitdiffstats
path: root/meta-security/recipes-core
AgeCommit message (Collapse)AuthorFilesLines
2018-12-18smack-system-setup: Update udev rulesJosé Bollo1-0/+4
Add rules to correctly tag devices with *. The most general rule is that devices should be protected using DAC rules (user and group). Bug-AGL: SPEC-2006 Change-Id: Ie18f79353f8f7645c2b615a359c65ec3a6984958 Signed-off-by: José Bollo <jose.bollo@iot.bzh>
2018-12-14systemd: Cleanup of recipe of meta-securityJosé Bollo12-1012/+9
The recipe for systemd that belongs to meta-security was carrying lot of history for probably no purpose. If history is needed, curious people can still refer to https://github.com/intel/meta-intel-iot-security Change-Id: I8762da7feb2084de2a97025498eb47ef815c7954 Signed-off-by: José Bollo <jose.bollo@iot.bzh>
2018-12-14systemd: Refactor build using smack-system-setupJosé Bollo8-69/+144
This changes introduces the new recipe meta-security/recipes-core/smack-system-setup/smack-system-setup_1.bb The purpose is to split the recipe of systemd in two parts: - A part specific to systemd and only systemd It actually includes Smack patches for systemd and a renaming of udev-rules. - A part more oriented on putting the system in order to run with Smack activated. At the end, it will probably save many rebuilds as systemd recipe will evolve less in relation with the setup of the system. As example, the udev rule file "55-udev-smack-default.rules" that setup udev rules specific to smack is no more brought by systemd but by smack-system-setup. Also at the same time, some cleanup and refactoring is done. Note that the ".bbappend" file for systemd is now fixed in version and is including a common file file that records the several known versions. No cleanup was made on the versioned patch for the sake of memory. The cleanup of the history is to be achieved later... Bug-AGL: SPEC-2045 Change-Id: Iacf772142a381729dfdbe98d133a3effc4d6cf68 Signed-off-by: José Bollo <jose.bollo@iot.bzh>
2018-04-06dbus-cynara: Fix a missing RDEPENDSJosé Bollo1-0/+2
dbus-cynara is a separate package of dbus because it allows to break the dependency loop dbus -> cynara -> ... -> dbus coming from the fact that many many usefull things depend on dbus: documentation generators, test handlers, ... In other words, dbus-cynara is the same as dbus. As such, it uses the subpackage dbus-lib (known as libdbus). This has to be set as a RDEPENDS, otherwise bitbake complains: QA Issue: dbus-cynara rdepends on dbus-lib, but it isn't a builds dependency, missing dbus in DEPENDS or PACKAGECONFIG? Change-Id: I72472dc9e6e8f21d0aabc9a1186f1cb7d8343445 Signed-off-by: José Bollo <jose.bollo@iot.bzh>
2018-04-04dbus-cynara: Avoid dependency loopJosé Bollo17-6279/+75
The dependency loop appeared when compiling with DISTRO_FEATURE ptest. To avoid it, I restore the logic implemented before in meta-intel-iot-security. I also remove unless files. Bug-AGL: SPEC-1334 Change-Id: Ibe8b9359a65fec034df2534c5fceb4769e63aa99 Signed-off-by: José Bollo <jose.bollo@iot.bzh>
2018-02-13dbus-cynara: Upgrade to 1.10.20José Bollo18-255/+5794
The main patches from dbus to make it cynara aware are cherry-picked on top of the dbus 1.10.20 that is the upstream version for rocko. Change-Id: Ib7b07f335543cb56c4c96ef8f55305e61bc69b5c Signed-off-by: José Bollo <jose.bollo@iot.bzh>
2018-02-13Remove smack recipeJosé Bollo3-4/+4
smack user space library is provided by meta-security Change-Id: Ifb5e88e5f5a1aab3e695ab91a56d8c55c33fd004 Signed-off-by: José Bollo <jose.bollo@iot.bzh>
2018-02-13Integrate parts of meta-intel-iot-securityJosé Bollo29-0/+7742
Adds the recipes of the sub layers - meta-security-framework - meta-security-smack Change-Id: I618608008a3b3d1d34adb6e38048110f13ac0643 Signed-off-by: José Bollo <jose.bollo@iot.bzh>