Skip to content

Conversation

Lukas-Luger
Copy link

I am working on some glue code to enable the use of the PSA Certified API via a USE_PSA flag.

This PR implements hashing and prng. I used the existing prng include methodology as an example to further separate the hashing functionality into platform-specific files.

So far I have only tested psa hashing and prng as well as the provided software hashing function, but have not been able to test it with sodium for hashing.

fixed naming

initialized psa inside dtls_init(); removed const on prf_labels, bc psa wants it in RAM

testing removing makefile.riot in plattform specific

progress on removing makefile

working dtls_hash.h and .c file (tested with native sha2 and psa)

fixed psa, reverted const

little cleanup

further cleanup

fixed formating
@boaks
Copy link
Contributor

boaks commented Feb 16, 2025

First at all, thanks for your contribution.

For open source projects of the Eclipse Foundation some rules for such contributions need to be obeyed to ensure, that others are able to use it with the Eclipse License (EPL 1.0).

Did you read the CONTRIBUTING guidance?

We will need a Eclipse Contributor Agreement from you in order to process the PR.

@Lukas-Luger
Copy link
Author

Yes, I did read the CONTRIBUTING guidance and agreed to the ECA. Seems like it needed some time for processing the agreement.

@Lukas-Luger
Copy link
Author

Is there anything to do to get this merged?

@boaks
Copy link
Contributor

boaks commented Apr 5, 2025

Hi Lukas,

sorry from my side. I had the reduce my time spent into open source projects to my free time. I currently try to maintain Eclipse/Californium and answer the questions for tinydtls.

We have quite a lot of other PRs open, some for longer. In general I'm not sure, how long it will take.
I could provide my feedback, but I'm not sure, if that helps to merge it faster.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants