Re: [Paparazzi-devel] paparazzi secure datalink compile errors.

[Gautier Hattenberger]

Hi,

I have only tested on real board so far, with ChibiOS. Once I got the RNG driver working, I found an error about Mutex. I can see that the gec transport is using a Mutex, but this is probably related to your implementation of ChibiOS in Paparazzi, Michal, because with the current uart driver, this is making a conflict. Actually, I think it should be removed for the current master branch (note that it doesn't affect nps and stm32 arch).

My latest problem when leaving the lab was that once the connection is established with rustlink, the MCU stops soon after because of stack overflow. Michal, do you have an idea about the actual memory usage of this algo ? Sometimes, it works a little before crashing, so the encryption part should be fine.

Gautier

Le 14/01/2021 à 17:43, Michal Podhradsky a écrit :

Hi Gautier, Chris,

thanks for working on it. I will peek at the rustlink implementation. Do you have a configuration I should try (preferably with NPS target)?

Regards

Michal

On Thu, Jan 14, 2021 at 6:23 AM Gautier Hattenberger <gautier.hattenberger@gmail.com> wrote:

Ok, the first issue was a bug in my rng driver. But now I have some issues threads and mutex

Le 14/01/2021 à 00:59, Michal Podhradsky a écrit :

Hi Gautier,

make sure to delete Cargo.lock and do cargo clean before cargo build

Rusthacl clones hacl-c and compiles it: https://github.com/podhrmic/rusthacl/blob/master/build.rs#L9

Are you able to compile the key-generator from the command line?

Michal

On Wed, Jan 13, 2021 at 2:23 PM Gautier Hattenberger <gautier.hattenberger@gmail.com> wrote:

Hello Michal,

Thanks for your help.

It seems that the rustlink tool don't compile and install hacl-c automatically. Maybe the build.rs script is not called. Any idea ?

Gautier

Le 13/01/2021 à 22:00, Michal Podhradsky a écrit :

Hi Chris, Gautier,

the key generator was depending on a repo that no longer exists. I fixed it in this PR: https://github.com/paparazzi/paparazzi/pull/2645

I haven't used paparazzi in a while, and all the secure telemetry modules seem to be missing something (or they haven't been updated to compile), so if you are able to test it end to end, that would be great.

Regards

Michal

On Wed, Jan 13, 2021 at 9:32 AM Chris <hendrixgr@gmail.com> wrote:

After reading a little about rust i think the warnings are fixed if we
replace

Err(why) => panic!("couldn't write to {}: {}", display, why.description()),

with

Err(why) => panic!("couldn't create {}: {}", display, why.to_string()),

and comment out line 33 "use std::error::Error;"

I haven't tried it yet but the description method will be hard
deprecated and must be replaced in order "why" to return a string.

Chris


_______________________________________________
Paparazzi-devel mailing list
Paparazzi-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel

_______________________________________________
Paparazzi-devel mailing list
Paparazzi-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel

_______________________________________________
Paparazzi-devel mailing list
Paparazzi-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel

_______________________________________________
Paparazzi-devel mailing list
Paparazzi-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel

_______________________________________________
Paparazzi-devel mailing list
Paparazzi-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel

_______________________________________________
Paparazzi-devel mailing list
Paparazzi-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel