Re: [yocto] [meta-security][PATCH v3] parsec-service: update from 1.1.0 to 1.2.0-rc1

2023-04-10 Thread Anton Antonov 
On Mon, Apr 10, 2023 at 04:17 AM, Armin Kuster wrote:

> 
> Something in latest master may have introduced another issue, this time
> the runtime testing.  I am see this new error:
> 
> self.check_packageconfig("TS")
> File
> "/home/akuster/oss/maint/meta-security/meta-parsec/lib/oeqa/runtime/cases/parsec.py",
> line 64, in check_packageconfig
> if prov not in self.tc.td['PACKAGECONFIG:pn-parsec-service']:
> KeyError: 'PACKAGECONFIG:pn-parsec-service'
> 
> Any ideas on how to fix or what might be causing this? I thought I had a
> fix but the test hangs.

The default value of PACKAGECONFIG is not included into tc.td if it's not 
defined in local.conf for whatever reason.

I will send a fix soon.

Cheers,

Anton

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59657): https://lists.yoctoproject.org/g/yocto/message/59657
Mute This Topic: https://lists.yoctoproject.org/mt/97876594/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [meta-security][PATCH v3] parsec-service: update from 1.1.0 to 1.2.0-rc1

2023-04-10 Thread Armin Kuster 



On 4/6/23 8:41 AM, Anton Antonov wrote:

On Thu, Apr 6, 2023 at 05:38 AM, Armin Kuster wrote:

1.2.0 released yesterday. Is someone planning on sending  a new
series. If not, I can give it a shot.

Yes, we're testing the new recipes atm. We will send them asap.



Something in latest master may have introduced another issue, this time 
the runtime testing.  I am see this new error:



 self.check_packageconfig("TS")
  File 
"/home/akuster/oss/maint/meta-security/meta-parsec/lib/oeqa/runtime/cases/parsec.py", 
line 64, in check_packageconfig

    if prov not in self.tc.td['PACKAGECONFIG:pn-parsec-service']:
KeyError: 'PACKAGECONFIG:pn-parsec-service'


Any ideas on how to fix or what might be causing this? I thought I had a 
fix but the test hangs.


-armin


Cheers,

Anton







-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59654): https://lists.yoctoproject.org/g/yocto/message/59654
Mute This Topic: https://lists.yoctoproject.org/mt/97876594/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [meta-security][PATCH v3] parsec-service: update from 1.1.0 to 1.2.0-rc1

2023-04-06 Thread Anton Antonov 
On Thu, Apr 6, 2023 at 05:38 AM, Armin Kuster wrote:

> 
> 1.2.0 released yesterday. Is someone planning on sending  a new series. If
> not, I can give it a shot.

Yes, we're testing the new recipes atm. We will send them asap.

Cheers,

Anton

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59629): https://lists.yoctoproject.org/g/yocto/message/59629
Mute This Topic: https://lists.yoctoproject.org/mt/97876594/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [meta-security][PATCH v3] parsec-service: update from 1.1.0 to 1.2.0-rc1

2023-04-06 Thread Armin Kuster 



On 4/3/23 6:53 AM, Anton Antonov wrote:

On Sat, Apr 1, 2023 at 05:50 AM, Armin Kuster wrote:

parsec-service 1.1.0 fails to compile with latest tpm2-tss update
in meta-security:

Thanks for the update.
This patch is currently in a test build.
Just a note. If this version ends up being the official one being
supported in the upcoming 4.2 release, when parsec-service 1.2.0
official drops and is added, we will need to us "EPOCH" as I
believe "-rc1" being dropped will signal the version going backwards.

I think Parsec would fail to be built with this patch after these 
patches in OE-core:


https://git.yoctoproject.org/poky/commit/?id=2b12c58724d250d1faf24072128e2de75dfe2c15

https://git.yoctoproject.org/poky/commit/?id=4d9886e1435dba3785973cc920865f8ab67e644d

Updates for cargo-update-recipe-crates are under review and the 1.2.0 
release recipe would solve the issue.




1.2.0 released yesterday. Is someone planning on sending  a new series. 
If not, I can give it a shot.


- Armin


Cheers,

Anton







-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59628): https://lists.yoctoproject.org/g/yocto/message/59628
Mute This Topic: https://lists.yoctoproject.org/mt/97876594/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [meta-security][PATCH v3] parsec-service: update from 1.1.0 to 1.2.0-rc1

2023-04-03 Thread Armin Kuster 



On 4/3/23 6:53 AM, Anton Antonov wrote:

On Sat, Apr 1, 2023 at 05:50 AM, Armin Kuster wrote:

parsec-service 1.1.0 fails to compile with latest tpm2-tss update
in meta-security:

Thanks for the update.
This patch is currently in a test build.
Just a note. If this version ends up being the official one being
supported in the upcoming 4.2 release, when parsec-service 1.2.0
official drops and is added, we will need to us "EPOCH" as I
believe "-rc1" being dropped will signal the version going backwards.

I think Parsec would fail to be built with this patch after these 
patches in OE-core:


https://git.yoctoproject.org/poky/commit/?id=2b12c58724d250d1faf24072128e2de75dfe2c15

https://git.yoctoproject.org/poky/commit/?id=4d9886e1435dba3785973cc920865f8ab67e644d



Yep, I am dealing with this on two other rust recipes. Fun.

-armin


Updates for cargo-update-recipe-crates are under review and the 1.2.0 
release recipe would solve the issue.


Cheers,

Anton







-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59597): https://lists.yoctoproject.org/g/yocto/message/59597
Mute This Topic: https://lists.yoctoproject.org/mt/97876594/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [meta-security][PATCH v3] parsec-service: update from 1.1.0 to 1.2.0-rc1

2023-04-03 Thread Anton Antonov 
On Sat, Apr 1, 2023 at 05:50 AM, Armin Kuster wrote:

> 
> 
>> parsec-service 1.1.0 fails to compile with latest tpm2-tss update
>> in meta-security:
> 
> Thanks for the update.
> This patch is currently in a test build.
> Just a note. If this version ends up being the official one being
> supported in the upcoming 4.2 release, when parsec-service 1.2.0 official
> drops and is added, we will need to us "EPOCH" as I believe "-rc1" being
> dropped will signal the version going backwards.

I think Parsec would fail to be built with this patch after these patches in 
OE-core:

https://git.yoctoproject.org/poky/commit/?id=2b12c58724d250d1faf24072128e2de75dfe2c15

https://git.yoctoproject.org/poky/commit/?id=4d9886e1435dba3785973cc920865f8ab67e644d

Updates for cargo-update-recipe-crates are under review and the 1.2.0 release 
recipe would solve the issue.

Cheers,

Anton

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59596): https://lists.yoctoproject.org/g/yocto/message/59596
Mute This Topic: https://lists.yoctoproject.org/mt/97876594/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [meta-security][PATCH v3] parsec-service: update from 1.1.0 to 1.2.0-rc1

2023-04-03 Thread Anton Antonov 
On Sat, Apr 1, 2023 at 05:50 AM, Armin Kuster wrote:

> 
> 
>> parsec-service 1.1.0 fails to compile with latest tpm2-tss update
>> in meta-security:
> 
> Thanks for the update.
> This patch is currently in a test build.
> Just a note. If this version ends up being the official one being
> supported in the upcoming 4.2 release, when parsec-service 1.2.0 official
> drops and is added, we will need to us "EPOCH" as I believe "-rc1" being
> dropped will signal the version going backwards.

We're planning to include Parsec 1.2.0 release into 4.2. I'm not sure what to 
do with this rc1 recipes tbh.

Miko, can you wait for the Parsec release?

Cheers,

Anton

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59595): https://lists.yoctoproject.org/g/yocto/message/59595
Mute This Topic: https://lists.yoctoproject.org/mt/97876594/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [meta-security][PATCH v3] parsec-service: update from 1.1.0 to 1.2.0-rc1

2023-04-01 Thread Armin Kuster 



On 3/27/23 2:16 AM, Mikko Rapeli wrote:

parsec-service 1.1.0 fails to compile with latest tpm2-tss update
in meta-security:

Thanks for the update.

This patch is currently in a test build.

Just a note. If this version ends up being the official one being 
supported in the upcoming 4.2 release, when parsec-service 1.2.0 
official drops and is added, we will need to us "EPOCH" as I believe 
"-rc1" being dropped will signal the version going backwards.


- armin


| error: failed to run custom build command for `tss-esapi v7.1.0`
|
| Caused by:
|   process didn't exit successfully:
`/oe/build/tmp_trs-qemuarm64/work/cortexa57-trs-linux/parsec-service/1.1.0-r0/build/target/release/build/tss-esapi-5b5d9342bd16db73/build-script-build`
(exit status: 101)
|   --- stderr
|   thread 'main' panicked at 'Unsupported TSS version: 4',
/oe/build/tmp_trs-qemuarm64/work/cortexa57-trs-linux/parsec-service/1.1.0-r0/cargo_home/bitbake/tss-esapi-7.1.0/build.rs:9:22

and also latest meta-clang changes break the build with:

|   thread 'main' panicked at 
'"enum_(unnamed_at_/oe/build/tmp_trs-qemuarm64/work/cortexa57-trs-linux/parsec-service/1_1_0-r0/build/target/aarch64-trs-linux-gnu/release/build/psa-crypto-sys-b4f9ce2b7d8846b2/out/include/mbedtls/cipher_h_205_1)"
 is not a valid Ident', 
/oe/build/tmp_trs-qemuarm64/work/cortexa57-trs-linux/parsec-service/1.1.0-r0/cargo_home/bitbake/proc-macro2-1.0.43/src/fallback.rs:730:9
|   stack backtrace:
|  0: rust_begin_unwind
|  1: core::panicking::panic_fmt
|  2: proc_macro2::fallback::validate_ident
|  3: proc_macro2::fallback::Ident::_new
|  4: proc_macro2::fallback::Ident::new
|  5: proc_macro2::imp::Ident::new
|  6: proc_macro2::Ident::new
|  7: bindgen::ir::context::BindgenContext::rust_ident_raw
|  8: bindgen::ir::context::BindgenContext::rust_ident
|  9: ::codegen
| 10: ::codegen
| 11: ::codegen
| 12: ::codegen::{{closure}}
| 13: ::codegen
| 14: ::codegen
| 15: bindgen::codegen::codegen::{{closure}}
| 16: bindgen::ir::context::BindgenContext::gen
| 17: bindgen::codegen::codegen
| 18: bindgen::Bindings::generate
| 19: bindgen::Builder::generate
| 20: build_script_build::common::generate_mbed_crypto_bindings
| 21: build_script_build::operations::script_operations
| 22: build_script_build::main
| 23: core::ops::function::FnOnce::call_once
|   note: Some details are omitted, run with `RUST_BACKTRACE=full` for a 
verbose backtrace.

In both cases fix is to update to the master branch or 1.2.0-rc1 pre-release.
Porting the individual patches did not work due to complex rust crate depencies.

Added LICENSE file checksum. Using cargo-update-recipe-crates.bbclass from
poky to maintain list of crates in the .inc file, but removed entries
for fuzz/Cargo.lock. Tested on qemu that parsec.service stars correctly
and works with swtpm use cases.

Signed-off-by: Mikko Rapeli 
---
  ...ce_1.1.0.inc => parsec-service-crates.inc} | 239 +-
  ...e_1.1.0.bb => parsec-service_1.2.0-rc1.bb} |  14 +-
  2 files changed, 134 insertions(+), 119 deletions(-)
  rename meta-parsec/recipes-parsec/parsec-service/{parsec-service_1.1.0.inc => 
parsec-service-crates.inc} (50%)
  rename meta-parsec/recipes-parsec/parsec-service/{parsec-service_1.1.0.bb => 
parsec-service_1.2.0-rc1.bb} (91%)

v3: change to gitsm fetcher

v2: removed crates for fuzz/Cargo.lock from SRC_URI
 https://lists.yoctoproject.org/g/yocto/message/59518

v1: https://lists.yoctoproject.org/g/yocto/message/59495
diff --git a/meta-parsec/recipes-parsec/parsec-service/parsec-service_1.1.0.inc 
b/meta-parsec/recipes-parsec/parsec-service/parsec-service-crates.inc
similarity index 50%
rename from meta-parsec/recipes-parsec/parsec-service/parsec-service_1.1.0.inc
rename to meta-parsec/recipes-parsec/parsec-service/parsec-service-crates.inc
index c04bcbd..fe80b42 100644
--- a/meta-parsec/recipes-parsec/parsec-service/parsec-service_1.1.0.inc
+++ b/meta-parsec/recipes-parsec/parsec-service/parsec-service-crates.inc
@@ -1,223 +1,232 @@
-# This file is created from parsec repository Cargo.lock using cargo-bitbake 
tool
+# Autogenerated with 'bitbake -c update_crates parsec-service'
  
+# from Cargo.lock

  SRC_URI += " \
  crate://crates.io/ahash/0.7.6 \
-crate://crates.io/aho-corasick/0.7.19 \
+crate://crates.io/aho-corasick/0.7.20 \
  crate://crates.io/ansi_term/0.12.1 \
-crate://crates.io/anyhow/1.0.64 \
+crate://crates.io/anyhow/1.0.69 \
+crate://crates.io/asn1-rs/0.3.1 \
  crate://crates.io/asn1-rs-derive/0.1.0 \
  crate://crates.io/asn1-rs-impl/0.1.0 \
-crate://crates.io/asn1-rs/0.3.1 \
  crate://crates.io/atty/0.2.14 \
  crate://crates.io/autocfg/1.1.0 \
-crate://crates.io/base64/0.13.0 \
+crate://crates.io/base64/0.13.1 \
  crate://crates.io/bincode/1.3.3 \
  crate://crates.io/bindgen/0.57.0 \
-crate://crates.io/bindgen/0.59.2 \
+crate://crates.io/bindgen/0.63

Re: [yocto] [meta-security][PATCH v3] parsec-service: update from 1.1.0 to 1.2.0-rc1

2023-03-27 Thread Anton Antonov 
On Sun, Mar 26, 2023 at 11:16 PM, Mikko Rapeli wrote:

> 
> ...ce_1.1.0.inc => parsec-service-crates.inc} | 239 +-
> ...e_1.1.0.bb => parsec-service_1.2.0-rc1.bb} | 14 +-
> 2 files changed, 134 insertions(+), 119 deletions(-)
> rename meta-parsec/recipes-parsec/parsec-service/{parsec-service_1.1.0.inc
> => parsec-service-crates.inc} (50%)
> rename meta-parsec/recipes-parsec/parsec-service/{parsec-service_1.1.0.bb
> => parsec-service_1.2.0-rc1.bb} (91%)
> 
> v3: change to gitsm fetcher

Ack, although this recipe will be replaced with 1.2.0 release version in a week 
of two.

Cheers,
Anton

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59528): https://lists.yoctoproject.org/g/yocto/message/59528
Mute This Topic: https://lists.yoctoproject.org/mt/97876594/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] [meta-security][PATCH v3] parsec-service: update from 1.1.0 to 1.2.0-rc1

2023-03-26 Thread Mikko Rapeli 
parsec-service 1.1.0 fails to compile with latest tpm2-tss update
in meta-security:

| error: failed to run custom build command for `tss-esapi v7.1.0`
|
| Caused by:
|   process didn't exit successfully:
`/oe/build/tmp_trs-qemuarm64/work/cortexa57-trs-linux/parsec-service/1.1.0-r0/build/target/release/build/tss-esapi-5b5d9342bd16db73/build-script-build`
(exit status: 101)
|   --- stderr
|   thread 'main' panicked at 'Unsupported TSS version: 4',
/oe/build/tmp_trs-qemuarm64/work/cortexa57-trs-linux/parsec-service/1.1.0-r0/cargo_home/bitbake/tss-esapi-7.1.0/build.rs:9:22

and also latest meta-clang changes break the build with:

|   thread 'main' panicked at 
'"enum_(unnamed_at_/oe/build/tmp_trs-qemuarm64/work/cortexa57-trs-linux/parsec-service/1_1_0-r0/build/target/aarch64-trs-linux-gnu/release/build/psa-crypto-sys-b4f9ce2b7d8846b2/out/include/mbedtls/cipher_h_205_1)"
 is not a valid Ident', 
/oe/build/tmp_trs-qemuarm64/work/cortexa57-trs-linux/parsec-service/1.1.0-r0/cargo_home/bitbake/proc-macro2-1.0.43/src/fallback.rs:730:9
|   stack backtrace:
|  0: rust_begin_unwind
|  1: core::panicking::panic_fmt
|  2: proc_macro2::fallback::validate_ident
|  3: proc_macro2::fallback::Ident::_new
|  4: proc_macro2::fallback::Ident::new
|  5: proc_macro2::imp::Ident::new
|  6: proc_macro2::Ident::new
|  7: bindgen::ir::context::BindgenContext::rust_ident_raw
|  8: bindgen::ir::context::BindgenContext::rust_ident
|  9: ::codegen
| 10: ::codegen
| 11: ::codegen
| 12: ::codegen::{{closure}}
| 13: ::codegen
| 14: ::codegen
| 15: bindgen::codegen::codegen::{{closure}}
| 16: bindgen::ir::context::BindgenContext::gen
| 17: bindgen::codegen::codegen
| 18: bindgen::Bindings::generate
| 19: bindgen::Builder::generate
| 20: build_script_build::common::generate_mbed_crypto_bindings
| 21: build_script_build::operations::script_operations
| 22: build_script_build::main
| 23: core::ops::function::FnOnce::call_once
|   note: Some details are omitted, run with `RUST_BACKTRACE=full` for a 
verbose backtrace.

In both cases fix is to update to the master branch or 1.2.0-rc1 pre-release.
Porting the individual patches did not work due to complex rust crate depencies.

Added LICENSE file checksum. Using cargo-update-recipe-crates.bbclass from
poky to maintain list of crates in the .inc file, but removed entries
for fuzz/Cargo.lock. Tested on qemu that parsec.service stars correctly
and works with swtpm use cases.

Signed-off-by: Mikko Rapeli 
---
 ...ce_1.1.0.inc => parsec-service-crates.inc} | 239 +-
 ...e_1.1.0.bb => parsec-service_1.2.0-rc1.bb} |  14 +-
 2 files changed, 134 insertions(+), 119 deletions(-)
 rename meta-parsec/recipes-parsec/parsec-service/{parsec-service_1.1.0.inc => 
parsec-service-crates.inc} (50%)
 rename meta-parsec/recipes-parsec/parsec-service/{parsec-service_1.1.0.bb => 
parsec-service_1.2.0-rc1.bb} (91%)

v3: change to gitsm fetcher

v2: removed crates for fuzz/Cargo.lock from SRC_URI
https://lists.yoctoproject.org/g/yocto/message/59518

v1: https://lists.yoctoproject.org/g/yocto/message/59495
diff --git a/meta-parsec/recipes-parsec/parsec-service/parsec-service_1.1.0.inc 
b/meta-parsec/recipes-parsec/parsec-service/parsec-service-crates.inc
similarity index 50%
rename from meta-parsec/recipes-parsec/parsec-service/parsec-service_1.1.0.inc
rename to meta-parsec/recipes-parsec/parsec-service/parsec-service-crates.inc
index c04bcbd..fe80b42 100644
--- a/meta-parsec/recipes-parsec/parsec-service/parsec-service_1.1.0.inc
+++ b/meta-parsec/recipes-parsec/parsec-service/parsec-service-crates.inc
@@ -1,223 +1,232 @@
-# This file is created from parsec repository Cargo.lock using cargo-bitbake 
tool
+# Autogenerated with 'bitbake -c update_crates parsec-service'
 
+# from Cargo.lock
 SRC_URI += " \
 crate://crates.io/ahash/0.7.6 \
-crate://crates.io/aho-corasick/0.7.19 \
+crate://crates.io/aho-corasick/0.7.20 \
 crate://crates.io/ansi_term/0.12.1 \
-crate://crates.io/anyhow/1.0.64 \
+crate://crates.io/anyhow/1.0.69 \
+crate://crates.io/asn1-rs/0.3.1 \
 crate://crates.io/asn1-rs-derive/0.1.0 \
 crate://crates.io/asn1-rs-impl/0.1.0 \
-crate://crates.io/asn1-rs/0.3.1 \
 crate://crates.io/atty/0.2.14 \
 crate://crates.io/autocfg/1.1.0 \
-crate://crates.io/base64/0.13.0 \
+crate://crates.io/base64/0.13.1 \
 crate://crates.io/bincode/1.3.3 \
 crate://crates.io/bindgen/0.57.0 \
-crate://crates.io/bindgen/0.59.2 \
+crate://crates.io/bindgen/0.63.0 \
 crate://crates.io/bitfield/0.13.2 \
 crate://crates.io/bitflags/1.3.2 \
-crate://crates.io/bumpalo/3.11.0 \
-crate://crates.io/bytes/1.2.1 \
-crate://crates.io/cc/1.0.73 \
+crate://crates.io/bumpalo/3.12.0 \
+crate://crates.io/bytes/1.4.0 \
+crate://crates.io/cc/1.0.79 \
 crate://crates.io/cexpr/0.4.0 \
 crate://crates.io/cexpr/0.6.0 \
 crate://crates.