Minor version bump from 4.1.1 to 4.1.3, containing two fixes: 4.1.3 - 2020-06-02 * tpm2_create: Fix issue with userauth attribute being cleared if policy is specified. 4.1.2 - 2020-05-18 * Fix

Hello, Topposting since the problem is in the screenshot. The issue is the naming of the shared object. Linux convention is that a shared object contains the version number e.g.

tpm2_import used a fixed AES key for the inner wrapper, which means that a MITM attack would be able to unwrap the imported key. Even the use of an encrypted session will not prevent this. The TPM

if you are using linux-yocto for kernel then it is surely supported , so as long as it is added to kernel recipe it should work ok. On Tue, Mar 15, 2022 at 3:58 AM Monsees, Steven C (US)

I would take an update to 4.1.3. Thanks for the analysis, much appreciated. Missing the Standard OE patch format. The patch itself needs this additional meta

Current Dev Position: YP 3.5 M4 Next Deadline: 4th April. 2022 YP 3.5 M4 build Next Team Meetings: Bug Triage meeting Thursday Mar. 17th 7:30 am PDT

Otherwise recipies that need sed like strace fail with "requires /bin/sed, but no providers found in RDEPENDS" when building. --- recipes-extended/sed/sed_4.1.2.bb | 2 ++ 1 file changed, 2

When you say: " you might have to look into this kernel recipe and ensure that it has enabled merging configs feature from kernel" Are you talking about inheriting from "kernel-yocto" in order to

Hi, Please find the below error snapshot. I am trying to integrate OMADM (Open mobile alliance device management) on the top of yocto 3.4.2 (honister) poky. And facing the following issue with bitbake

Hi Mingrui, Richard, "Mingrui Ren" <jiladahe1997@...> wrote: I have found myself using a sed one-liner to alter that variable list in the fetcher code in order to pass through to git

Hi all, Intel and WR YP QA is planning for QA execution for YP build yocto-3.1.15.rc1. We are planning to execute following tests for this cycle: OEQA-manual tests for following module: 1.

All, YP M+ or high bugs which moved to a new milestone in WW11 are listed below: Priority Bug ID Short Description Changer Owner Was Became Medium+ 5876 Add a test for the kernel -c

All, The below were the owners of enhancements or bugs closed during the last

All, Below is the list as of top 44 bug owners as of the end of WW11 of who have open medium or higher bugs and enhancements against YP 3.5. There are 33 possible work days left until the final

All, The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on

A build flagged for QA (yocto-3.1.15.rc1) was completed on the autobuilder and is available at: /srv/autobuilder/autobuilder.yocto.io/pub/releases/yocto-3.1.15.rc1 Build hash information:

A build flagged for QA (yocto-3.1.15.rc1) was completed on the autobuilder and is available at: /srv/autobuilder/autobuilder.yocto.io/pub/releases/yocto-3.1.15.rc1 Build hash information:

On Mon, Mar 14, 2022 at 12:57 PM Monsees, Steven C (US) via lists.yoctoproject.org <steven.monsees=baesystems.com@...> wrote: these are some config files for doing what ? from what

Under my aarm64 platform ../recipes-core/images I have a file “aiox-swdebugfs.inc” Which basically contains: EXTRAPATHS_prepend := "$(THISDIR}/files:" LIC_FILES_CHKSUM =

tpm2_import: fix fixed AES key CVE-2021-3565 Upstream commit (with offset adjusted) https://github.com/tpm2-software/tpm2-tools/commit/c069e4f179d5e6653a84fb236816c375dca82515 Signed-off-by: Ralph