Package: wnpp
Severity: wishlist
X-Debbugs-Cc: Mazen Neifer <[email protected]>

* Package name : python-lakers-python
Version : 0.5.0
Upstream Contact: Geovane Fedrecheski, Christian Ams�ss <[email protected]>
* URL : https://lakers.readthedocs.io/en/latest/
* License : BSD-3-Clause
Programming Lang: Python package written in Rust
Description : an implementation of the EDHOC protocol (RFC9528) providing key establishment for constrained ("IoT") devices

Lakers is an implementation of EDHOC (RFC9528), which is part of setting
up object security for constrained devices (also called "IoT" devices),
e.g. for CoAP OSCORE (RFC7252, RFC8613).

This package contains Python wrappers for the library.

---

This package is an recommended dependency of the python3-aiocoap
package. While CoAP has security modes that can do without this, they
are all flawed (in general as a matter of personal opinion, and in this implementation of CoAP as a matter of fact).

The underlying Rust library, lakers, is itself so far unpackaged, but it
and all its dependencies should be as smooth sailing packaging-wise as a
Rust crate can be (and I hope that's very smooth). The Rust tree of dependencies thar are unpackaged is, as I understand:

- lakers
- lakers-shared, lakers-crypto-rustcrypto, lakers-ead-authz (all in
this workspace, so this might become one source package I think)
- defmt-or-log
- defmt-or-log-macros
- hax-lib, hax-lib-macros (hax does formal verification, but the crate
is an almost-no-op that merely enables the annotations that the
formal verification needs)

I am part of the upstream team for this package, so if there's anything
we can do to simplify packaging, pl