Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update to use Californium 2.0.0-M17 #749

Merged

Conversation

rikard-sics
Copy link
Contributor

The OSCORE-related code has been updated to use Californium 2.0.0-M17. For now the OSCORE context database is still handled as a singleton. This will be updated in a coming PR.

Signed-off-by: Rikard Höglund <rikard.hoglund@ri.se>
Signed-off-by: Rikard Höglund <rikard.hoglund@ri.se>
The OSCORE-related code now also uses Californium 2.0.0-M17.
For now the OSCORE context database is still handled as a singleton.

Signed-off-by: Rikard Höglund <rikard.hoglund@ri.se>
@rikard-sics
Copy link
Contributor Author

Now the code has been updated to use Californium 2.0.0-M17. This will give access to more recent OSCORE features like OSCORE-related information (like sender/recipient ID) about incoming/outgoing CoAP messages.

In the recent versions of Californium the OSCORE context database is no longer a singleton. As we discussed before it is better if it is not a singleton in Leshan. For now I kept the OSCORE context database as as singleton and plan a separate PR to change this. I need to consider how I can make the context database accessible to all the places where it is needed.

@sbernard31 sbernard31 merged commit 170f35d into eclipse-leshan:oscore Oct 8, 2019
@sbernard31
Copy link
Contributor

It sounds good. Integrated in oscore branch.

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