Mirror of git.yoctoproject.org/meta-security.git https://git.enea.com/cgit/linux/meta-security.git/atom?h=styhead 2023-08-06T15:31:18+00:00 2023-08-06T15:31:18+00:00 Armin Kuster akuster808@gmail.com 2023-08-01T15:14:38+00:00 urn:sha1:39d373acd17f1b992c6c768cef62757371e1daa1 So that the security features in this layer can be used on the rt kernel. Signed-off-by: Armin Kuster <akuster808@gmail.com> 2023-06-03T14:04:32+00:00 Mikko Rapeli mikko.rapeli@linaro.org 2023-05-23T12:14:44+00:00 urn:sha1:e3156758b04244dde8b5f9a3a4d0ed106d525965 It's not used by linux-yocto bbappends in any configuration. Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org> Signed-off-by: Armin Kuster <akuster808@gmail.com> 2023-06-03T14:04:23+00:00 Mikko Rapeli mikko.rapeli@linaro.org 2023-05-23T12:14:43+00:00 urn:sha1:d30d8989a0e9d11d878b03d0eeaf341025f60e1a arm, arm64 and other machines can also have tpm and tpm2 devices and the config snippets tpm.scc and tpm2.scc work there too. Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org> Signed-off-by: Armin Kuster <akuster808@gmail.com> 2023-02-06T12:32:41+00:00 Mikko Rapeli mikko.rapeli@linaro.org 2023-01-30T11:01:06+00:00 urn:sha1:3529cfb43e47015aa0621755e7b6536b7947d295 These bbappends apply to multiple kernel versions so no need to make them version dependent. Fixes recipe parsing when using meta-security master branch on kirkstone. In our custom layer we set layer compatibility for kirkstone and I understand why meta-security upstream would not want to do that: LAYERSERIES_COMPAT_security-layer += 'kirkstone' LAYERSERIES_COMPAT_parsec-layer += 'kirkstone' LAYERSERIES_COMPAT_tpm-layer += 'kirkstone' While I work towards supporting also yocto master branch and newer releases than kirkstone, I would appreciate if I would not have to branch off layers over minor details like this. Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org> Signed-off-by: Armin Kuster <akuster808@gmail.com> 2023-01-28T15:17:03+00:00 Armin Kuster akuster808@gmail.com 2023-01-28T15:17:03+00:00 urn:sha1:92f04c78f0ed202b14e274367bec3fbc12cc0305 Signed-off-by: Armin Kuster <akuster808@gmail.com> 2022-09-25T15:29:43+00:00 Michael Haener michael.haener@siemens.com 2022-09-21T08:10:08+00:00 urn:sha1:014f9dab784972b4d1ec6d14476caa3148a826ab 2021-08-01T15:47:08+00:00 Armin Kuster akuster808@gmail.com 2021-07-29T23:31:50+00:00 urn:sha1:c7632b927c4cb31d77caebe1390da21c630cfe0e Signed-off-by: Armin Kuster <akuster808@gmail.com> 2021-06-06T20:03:37+00:00 Armin Kuster akuster808@gmail.com 2021-06-02T01:58:22+00:00 urn:sha1:35e1b6175005334fab7a3714133c6e7b98e0a80f Signed-off-by: Armin Kuster <akuster808@gmail.com> 2020-03-08T21:13:07+00:00 André Draszik git@andred.net 2020-03-05T20:12:44+00:00 urn:sha1:d7ca573c36706f3b5423fabcc1d5e652f513d0bc As linux-yocto upgraded to 5.x in oe-core, update the bbappend to 5.x to remove the warning ERROR: No recipes available for: .../meta-security/meta-tpm/recipes-kernel/linux/linux-yocto_4.%.bbappend This patch hasn't been verified any further than allowing bitbake to complete with a non-linux-yocto kernel. In particular options could be different, or new ones needed / desired. Signed-off-by: André Draszik <git@andred.net> Signed-off-by: Armin Kuster <akuster808@gmail.com> 2017-05-14T14:56:52+00:00 Armin Kuster akuster808@gmail.com 2017-05-08T19:47:05+00:00 urn:sha1:6d7b18dc22247ca6235081281def435c23ba2204 Signed-off-by: Armin Kuster <akuster808@gmail.com>