search

eclipse-leshan / leshan

Java Library for LWM2M
https://www.eclipse.org/leshan/
BSD 3-Clause "New" or "Revised" License
653 stars 407 forks source link

🏗 Leshan 2.0 : LWM2M 1.1 🚧 #563

Open sbernard31 opened 6 years ago

sbernard31 commented 6 years ago

Leshan v2.0.0 (master branch) is currently in development and aims to support LWM2M 1.1 (or at least some part of it).

You can have a look to currently supported or in development features or current roadmap.

If you are interested in LWM2M 1.1 support in Leshan, we strongly advice to :

This is the best way to get a final 2.0.0 release which fit your needs.

(If you need stable API and are fine with LWM2M v1.0, you should use Leshan v1.x)

sbernard31 commented 3 years ago

A first try about supporting Send Operation is available at #971.

sbernard31 commented 3 years ago

A new milestone release containing new LWM2M 1.1 features is out : 2.0.0-M3.

:exclamation::skull_and_crossbones::exclamation: Affected by security issue:exclamation::skull_and_crossbones::exclamation:

sbernard31 commented 3 years ago

A new milestone release containing new LWM2M 1.1 features is out : 2.0.0-M4. :tada:

Please do not hesitate to test and give us feedback. :pray:
We are also interested to know which features are missing you the most.
Look at the roadmap, already open issues or LWM2M 1.1 supported features, LWM2M 1.0 supported features or anything we didn't identified.

:exclamation::skull_and_crossbones::exclamation: Affected by security issue:exclamation::skull_and_crossbones::exclamation:

sbernard31 commented 3 years ago

A new milestone release containing new LWM2M 1.1 features is out : 2.0.0-M5. :tada:

We still take feedback about the release or the needed features. :pray: (see comment just above :point_up:)

Next release (M6) will be about cleaning (like removing old UI demo, keeping only one JSON or CBOR lib, more feature in demos, some code cleaning or more little missing feature about LWM2M v1.1 ...)

Then for M7, we will probably try begin to work on one of the bigger task: refactoring code to allow to add more transport Layer (#1025).

:warning: People who are using x509 and/or RPK with Leshan v2.0.0-M1 or v2.0.0-M4 MUST upgrade to 2.0.0-M5 version for security reason. :warning:

:exclamation::skull_and_crossbones::exclamation: Affected by security issue:exclamation::skull_and_crossbones::exclamation:

sbernard31 commented 3 years ago

I forgot to mention that M6 should also be the first release which will be built with java 8 ( see https://github.com/eclipse/leshan/issues/924) (until now that was java7)

zakharenkodmytro commented 3 years ago

Great, thanks

sbernard31 commented 2 years ago

A new milestone release about LWM2M 1.1 support is out : 2.0.0-M6. :tada:

About M7, next tasks should be about :

Adding more transport Layer (#1025) will probably be delaied to M8.

:exclamation::skull_and_crossbones::exclamation: Affected by security issue:exclamation::skull_and_crossbones::exclamation:

sbernard31 commented 2 years ago

:warning: 2.0.0-M2 to 2.0.0-M6 are affected by security issue because of com.upokecenter.cbor dependency. (See GHSA-fj2w-wfgv-mwq6) This concerns you if you are using CBOR or SenML-CBOR decoding. There is no milestones release planned at short term, waiting you should force the com.upokecenter.cbor version to 4.5.2.

sbernard31 commented 2 years ago

A new milestone release about LWM2M 1.1 support is out : 2.0.0-M7. :tada:

This 2.0.0-M7 contains com.upokecenter.cbor v4.5.2 which fix the security issue above :point_up:.

About M8, next tasks should be about :

About OSCORE, there is testable demos in oscore branch.

:exclamation::skull_and_crossbones::exclamation: Affected by security issue:exclamation::skull_and_crossbones::exclamation:

sbernard31 commented 2 years ago

A new milestone release about LWM2M 1.1 support is out : 2.0.0-M8. :tada:

Main focus for M9 : Adding more transport Layer (https://github.com/eclipse/leshan/issues/1025)

:exclamation::skull_and_crossbones::exclamation: Affected by security issue:exclamation::skull_and_crossbones::exclamation:

boaks commented 2 years ago

Maybe I missed it, but for now, there is now schedule day for a 2.0.0 release? I ask, because depending on the timeline, a cleaned up Californium 4.0.0 may be better for long term.

sbernard31 commented 2 years ago

Correct, there is no release day scheduled.

I think mandatory feature for 2.0.0 is at least #1025 and I guess this will be a long task to do. I also hope we will have a usable OSCORE feature but depends a lot of @rikard-sics and how much he can move forward on this at californium side (https://github.com/eclipse/leshan/issues/1231). (at worst this will be an experimental only feature) Maybe an experimental support of coap over TCP based on californium. And probably more little API improvement or refactoring. So lot of work to do and so probably no 2.0.0 soon.

If one or more major release of californium is released during the development phase of Leshan 2.0.0 we will integrate it as soon as possible.

If needed, I can let you know when will be soon of a 2.0.0 release.

sbernard31 commented 2 years ago

A new milestone release about LWM2M 1.1 support is out : 2.0.0-M9. :tada:

:warning: People who are using DTLS with Leshan v2.0.0-M1 to v2.0.0-M8 MUST upgrade to 2.0.0-M9 version for security reason. :warning:

See : https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-39368

Main focus for M10 : Adding Transport Layer Abstraction (https://github.com/eclipse/leshan/issues/1025)

:exclamation::skull_and_crossbones::exclamation: Affected by security issue:exclamation::skull_and_crossbones::exclamation:

sbernard31 commented 1 year ago

A new milestone release about LWM2M 1.1 support is out : 2.0.0-M10. :tada:

This should be the last milestone release before massive changes about Transport Layer Abstraction. Lot of the new API is already in master.

If you are using Leshan 2.0.0-Mx or if you are curious about those changes, :loudspeaker: we strongly encourage you to take a look at https://github.com/eclipse/leshan/issues/1025#issuecomment-1373824399 :loudspeaker:

:exclamation::skull_and_crossbones::exclamation: Affected by security issue:exclamation::skull_and_crossbones::exclamation:

sbernard31 commented 1 year ago

A new milestone release about LWM2M 1.1 support is out : 2.0.0-M11.

:loudspeaker: : This is first Milestone Release containing new Transport Layer Abstraction (GH-1025). This is massive changes and maybe not yet fully mature. So please read :warning: release warning before to use it.

:exclamation::skull_and_crossbones::exclamation: Affected by security issue:exclamation::skull_and_crossbones::exclamation:

sbernard31 commented 1 year ago

A new milestone release about LWM2M 1.1 support is out : 2.0.0-M12.

:loudspeaker: : This is second Milestone Release containing new Transport Layer Abstraction (GH-1025). This is massive changes and maybe not yet fully mature. So please read :warning: release warning before to use it.

:exclamation::skull_and_crossbones::exclamation: Affected by security issue:exclamation::skull_and_crossbones::exclamation:

sbernard31 commented 1 year ago

A new milestone release is out : 2.0.0-M13.

:loudspeaker: : This mainly a security fix of 2.0.0-M12, please read release description :warning:

sbernard31 commented 11 months ago

A new milestone release is out : 2.0.0-M14.

:loudspeaker: : Thx to new Transport Layer Abstraction (GH-1025), this release contains a new experimental CoAP provider based on java-coap. Please do not hesitate to try it and give us feedback.

sbernard31 commented 4 months ago

A new milestone release is out : 2.0.0-M15.

📢 : Thx to new Transport Layer Abstraction (GH-1025), this release contains a very experimental CoAP over TCP (and TLS) provider based on java-coap. Please do not hesitate to try it and give us feedback.

Next milestone (M16) should contain :

sbernard31 commented 3 months ago

A new milestone release is out : 2.0.0-M16.

:loudspeaker: : As plan this release is mainly about new maven module refactoring, so a lot of classes was moved and new maven module was created/renamed but behavior should not have changed. See Module Name and API Break.

This is strongly recommended to migrate to this version before to migrate to future 2.0.0-M17.