You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mynewt.apache.org by ad...@apache.org on 2017/01/26 02:07:37 UTC
[1/4] incubator-mynewt-site git commit: mfg docs - slight rewording /
rearranging
Repository: incubator-mynewt-site
Updated Branches:
refs/heads/develop a10075c4c -> eedec3fd2
mfg docs - slight rewording / rearranging
1. Move create mfg step such that it comes before the boot-build and
create-image steps.
Rationale: The mfg package only needs to be created once, whereas the
boot loader and image need to be rebuilt each time a new mfg image is
built. It makes sense to group the steps that need to be repeated
together.
2. Remove redundant 'newt build rb_boot' line from example
This line was accidentally duplicated.
3. Slight rewording of some text to keep vocabulary consistent (mfg
package versus manufacturing image).
This closes #145.
Project: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/commit/d657ec63
Tree: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/tree/d657ec63
Diff: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/diff/d657ec63
Branch: refs/heads/develop
Commit: d657ec63fbf77a967a0d433c91ff6f0ffe5666d9
Parents: a10075c
Author: Christopher Collins <cc...@apache.org>
Authored: Mon Jan 23 09:15:59 2017 -0800
Committer: aditihilbert <ad...@runtime.io>
Committed: Wed Jan 25 16:23:33 2017 -0800
----------------------------------------------------------------------
docs/newt/command_list/newt_mfg.md | 19 +++++++++----------
1 file changed, 9 insertions(+), 10 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/d657ec63/docs/newt/command_list/newt_mfg.md
----------------------------------------------------------------------
diff --git a/docs/newt/command_list/newt_mfg.md b/docs/newt/command_list/newt_mfg.md
index e7f5258..f7ee02e 100644
--- a/docs/newt/command_list/newt_mfg.md
+++ b/docs/newt/command_list/newt_mfg.md
@@ -60,21 +60,13 @@ targets/rb_boot
build_profile=optimized
```
-Build the bootloader and app images.
-
-```
-$ newt build rb_boot
-$ newt build rb_boot
-$ newt create-image rb_blinky 0.0.1
-```
-
-Create the directory and package to hold the manufacturing images.
+Create the directory and to hold the mfg packages.
```
$ mkdir -p mfgs/rb_blinky_rsa
```
-The `rb_blinky_rsa` package needs a pkg.yml file. In addition it is needs a mfg.yml file where the two constituent targets are defined. An example of each file is shown below.
+The `rb_blinky_rsa` package needs a pkg.yml file. In addition it is needs a mfg.yml file to specify the two constituent targets. An example of each file is shown below.
```
$ more mfgs/rb_blinky_rsa/pkg.yml
@@ -92,6 +84,13 @@ mfg.images:
- 'targets/rb_blinky'
```
+Build the bootloader and app images.
+
+```
+$ newt build rb_boot
+$ newt create-image rb_blinky 0.0.1
+```
+
Run the `newt mfg create` command to collect all the manufacturing snapshot files.
```
[2/4] incubator-mynewt-site git commit: minor edit to newt_mfg.md
Posted by ad...@apache.org.
minor edit to newt_mfg.md
Project: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/commit/82b4936c
Tree: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/tree/82b4936c
Diff: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/diff/82b4936c
Branch: refs/heads/develop
Commit: 82b4936cda8dd64354f3004912165c89a2ad8a37
Parents: d657ec6
Author: aditihilbert <ad...@runtime.io>
Authored: Wed Jan 25 16:29:02 2017 -0800
Committer: aditihilbert <ad...@runtime.io>
Committed: Wed Jan 25 16:29:02 2017 -0800
----------------------------------------------------------------------
docs/newt/command_list/newt_mfg.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/82b4936c/docs/newt/command_list/newt_mfg.md
----------------------------------------------------------------------
diff --git a/docs/newt/command_list/newt_mfg.md b/docs/newt/command_list/newt_mfg.md
index f7ee02e..7e6fe7d 100644
--- a/docs/newt/command_list/newt_mfg.md
+++ b/docs/newt/command_list/newt_mfg.md
@@ -60,7 +60,7 @@ targets/rb_boot
build_profile=optimized
```
-Create the directory and to hold the mfg packages.
+Create the directory to hold the mfg packages.
```
$ mkdir -p mfgs/rb_blinky_rsa
[4/4] incubator-mynewt-site git commit: updated BLE security doc to
remove placeholders about roadmap. The features have been implemented.
Posted by ad...@apache.org.
updated BLE security doc to remove placeholders about roadmap. The features have been implemented.
Project: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/commit/eedec3fd
Tree: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/tree/eedec3fd
Diff: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/diff/eedec3fd
Branch: refs/heads/develop
Commit: eedec3fd266d718e3983fb692867b0101211a840
Parents: e5f6029
Author: aditihilbert <ad...@runtime.io>
Authored: Wed Jan 25 18:07:16 2017 -0800
Committer: aditihilbert <ad...@runtime.io>
Committed: Wed Jan 25 18:07:16 2017 -0800
----------------------------------------------------------------------
docs/network/ble/ble_sec.md | 55 ++++++++++++++++++++++++++--------------
1 file changed, 36 insertions(+), 19 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/eedec3fd/docs/network/ble/ble_sec.md
----------------------------------------------------------------------
diff --git a/docs/network/ble/ble_sec.md b/docs/network/ble/ble_sec.md
index ad6fbc5..c4c815e 100644
--- a/docs/network/ble/ble_sec.md
+++ b/docs/network/ble/ble_sec.md
@@ -1,21 +1,38 @@
## BLE Security
-The Bluetooth Low Energy security model includes five distinct security concepts as listed below. For detailed specifications, see BLUETOOTH SPECIFICATION Version 4.2 [Vol 1, Part A].
-* **Pairing**: The process for creating one or more shared secret keys. In LE a single link key is generated by combining contributions from each device into a link key used during pairing. * **Bonding**: The act of storing the keys created during pairing for use in subsequent connections in order to form a trusted device pair. <font color="#F2853F">*Bonding is currently a roadmap item for Apache Mynewt.* </font>
-* **Device authentication**: Verification that the two devices have the same keys (verify device identity)
-* **Encryption**: Keeps message confidential. Encryption in Bluetooth LE uses AES-CCM cryptography and is performed in the *Controller*.
-* **Message integrity**: Protects against message forgeries.
-Bluetooth LE uses four association models depending on the I/O capabilities of the devices. <font color="#F2853F">*Apache Mynewt has first implemented support for "Just Works" only.*</font>
-* **Just Works**: designed for scenarios where at least one of the devices does not have a display capable of displaying a six digit number nor does it have a keyboard capable of entering six decimal digits.
-* **Numeric Comparison**: designed for scenarios where both devices are capable of displaying a six digit number and both are capable of having the user enter "yes" or "no". A good example of this model is the cell phone / PC scenario.
-* **Out of Band**: designed for scenarios where an Out of Band mechanism is used to both discover the devices as well as to exchange or transfer cryptographic numbers used in the pairing process.
-* **Passkey Entry**: designed for the scenario where one device has input capability but does not have the capability to display six digits and the other device has output capabilities. A good example of this model is the PC and keyboard scenario.
-###Key Generation
-Key generation for all purposes in Bluetooth LE is performed by the *Host* on each LE device independent of any other LE device.
-### Privacy Feature
-Bluetooth LE supports an optional feature during connection mode and connection procedures that reduces the ability to track a LE device over a period of time by changing the Bluetooth device address on a frequent basis. <font color="#F2853F">*Privacy support is currently a roadmap item for Apache Mynewt.*</font>
-There are two variants of the privacy feature.
-* In the first variant, private addresses are resolved and generated by the *Host*.
-* In the second variant, private addresses are resolved and generated by the *Controller* without involving the Host after the Host provides the Controller device identity information. The Host may provide the Controller with a complete resolving list or a subset of the resolving list.
-Device filtering becomes possible in the second variant when address resolution is performed in the Controller because the peer\u2019s device identity address can be resolved prior to checking whether it is in the white list.
-**Note**: When address resolution is performed exclusively in the Host, a device may experience increased power consumption because device filtering must be disabled.For more details on the privacy feature, refer to BLUETOOTH SPECIFICATION Version 4.2 [Vol 3, Part C] (Published 02 December 2014), Page 592.
+The Bluetooth Low Energy security model includes five distinct security concepts as listed below. For detailed specifications, see BLUETOOTH SPECIFICATION Version 4.2 [Vol 1, Part A].
+
+* **Pairing**: The process for creating one or more shared secret keys. In LE a single link key is generated by combining contributions from each device into a link key used during pairing.
+
+* **Bonding**: The act of storing the keys created during pairing for use in subsequent connections in order to form a trusted device pair.
+
+* **Device authentication**: Verification that the two devices have the same keys (verify device identity)
+
+* **Encryption**: Keeps message confidential. Encryption in Bluetooth LE uses AES-CCM cryptography and is performed in the *Controller*.
+
+* **Message integrity**: Protects against message forgeries.
+
+Bluetooth LE uses four association models depending on the I/O capabilities of the devices.
+
+* **Just Works**: designed for scenarios where at least one of the devices does not have a display capable of displaying a six digit number nor does it have a keyboard capable of entering six decimal digits.
+
+* **Numeric Comparison**: designed for scenarios where both devices are capable of displaying a six digit number and both are capable of having the user enter "yes" or "no". A good example of this model is the cell phone / PC scenario.
+
+* **Out of Band**: designed for scenarios where an Out of Band mechanism is used to both discover the devices as well as to exchange or transfer cryptographic numbers used in the pairing process.
+
+* **Passkey Entry**: designed for the scenario where one device has input capability but does not have the capability to display six digits and the other device has output capabilities. A good example of this model is the PC and keyboard scenario.
+
+###Key Generation
+
+Key generation for all purposes in Bluetooth LE is performed by the *Host* on each LE device independent of any other LE device.
+
+### Privacy Feature
+Bluetooth LE supports an optional feature during connection mode and connection procedures that reduces the ability to track a LE device over a period of time by changing the Bluetooth device address on a frequent basis.
+
+There are two variants of the privacy feature.
+
+* In the first variant, private addresses are resolved and generated by the *Host*.
+* In the second variant, private addresses are resolved and generated by the *Controller* without involving the Host after the Host provides the Controller device identity information. The Host may provide the Controller with a complete resolving list or a subset of the resolving list.
+Device filtering becomes possible in the second variant when address resolution is performed in the Controller because the peer\u2019s device identity address can be resolved prior to checking whether it is in the white list.
+
+**Note**: When address resolution is performed exclusively in the Host, a device may experience increased power consumption because device filtering must be disabled.For more details on the privacy feature, refer to BLUETOOTH SPECIFICATION Version 4.2 [Vol 3, Part C] (Published 02 December 2014), Page 592.
[3/4] incubator-mynewt-site git commit: Remove copyright date
Posted by ad...@apache.org.
Remove copyright date
Project: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/commit/e5f6029d
Tree: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/tree/e5f6029d
Diff: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/diff/e5f6029d
Branch: refs/heads/develop
Commit: e5f6029dc75db32f60ed10a2fea591d51639ae3b
Parents: 82b4936
Author: aditihilbert <ad...@runtime.io>
Authored: Wed Jan 25 17:01:20 2017 -0800
Committer: aditihilbert <ad...@runtime.io>
Committed: Wed Jan 25 17:01:20 2017 -0800
----------------------------------------------------------------------
mkdocs.yml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/e5f6029d/mkdocs.yml
----------------------------------------------------------------------
diff --git a/mkdocs.yml b/mkdocs.yml
index b80b434..6764393 100644
--- a/mkdocs.yml
+++ b/mkdocs.yml
@@ -544,6 +544,6 @@ extra:
location: "Las Vegas, NV"
date: '5-8 January, 2017'
-copyright: 'Copyright © 2015 The Apache Software Foundation, Licensed under the Apache License, Version 2.0 Apache and the Apache feather logo are trademarks of The Apache Software Foundation.'
+copyright: 'Apache Mynewt (incubating) is available under Apache License, version 2.0.'
google_analytics: ['UA-72162311-1', 'auto']