| commit | 0dcb0de1c9776010fbf56d598232b8fb88892082 | [log] [tgz] |
|---|---|---|
| author | Christopher Collins <ccollins@apache.org> | Tue Jul 23 16:32:12 2019 -0700 |
| committer | ccollins476ad <ccollins476ad@gmail.com> | Wed Jul 24 09:51:09 2019 -0700 |
| tree | 24b09ab84505fc1c3382f7cf1e9a435ca9a20f5b | |
| parent | a6d89abeb97759484d823ddd23640e1afe14b8c8 [diff] |
Remove security requirements from CoAP commands
This commit removes a feature that has been unused for years.
Initially, the idea was that each CoAP resource would be defined with
one of the following security levels:
* public (no security)
* unauthenticated (encryption)
* secure (encryption and authentication)
A session (connection) would be secured in a transport-specific way, but
the main transport under consideration was Bluetooth. In Bluetooth,
characteristics are assigned security levels resembling the three above.
To implement this defunct security mechanism in CoAP-over-Bluetooth, we
would need three different characteristics, one corresponding to each
security level. When sending a CoAP request, the newtmgr client would
choose the correct characteristic based on the secure state of the
connection.
This security policy has not been supported in Mynewt for a few years.
The code implementing it is unused and unmaintained, so I am removing it
now.
Newt Manager (newtmgr) is the application tool that enables a user to communicate with and manage remote devices running the Mynewt OS. It uses a connection profile to establish a connection with a device and sends command requests to the device. The newtmgr tool documentation can be found under /docs which are published at http://mynewt.apache.org/latest/os/modules/devmgmt/newtmgr.html
Build the newtmgr tool as follows:
apache-mynewt-newtmgr-1.3.0 directory to $GOPATH/src/mynewt.apache.org/newtmgrcd $GOPATH/src/mynewt.apache.org/newtmgr/newtmgrgo build