[jira] [Created] (MYNEWT-758) BLE Host - OOB security for SC

2017-05-17 Thread Christopher Collins (JIRA)
Christopher Collins created MYNEWT-758:
--

 Summary: BLE Host - OOB security for SC
 Key: MYNEWT-758
 URL: https://issues.apache.org/jira/browse/MYNEWT-758
 Project: Mynewt
  Issue Type: Bug
  Components: Nimble
Reporter: Christopher Collins
 Fix For: v1_1_0_rel






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (MYNEWT-750) BLE Host - Ignore pairing attempt from already bonded peer

2017-05-17 Thread Christopher Collins (JIRA)

 [ 
https://issues.apache.org/jira/browse/MYNEWT-750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christopher Collins updated MYNEWT-750:
---
Description: 
If a device is already bonded, the host should not allow the same device to 
pair again.  Currently, the host blindly proceeds with the pairing operation.  
This should not be allowed because the second peer could be an imposter 
masquerading as the original.

I propose the following behavior in such a scenario:
# Host notifies application of the duplicate pairing attempt via the gap event 
callback.  The callback would specify a new event code that specifically 
indicates a duplicate pairing attempt.
# The gap event callback would return an error code indicating which of the 
following behaviors to perform:
## Retry: Return BLE_GAP_REPEAT_PAIRING_RETRY after deleting the conflicting 
bond.  The stack will verify the bond has been deleted and continue the pairing 
procedure.  If the bond is still present, this event will be reported again.
## Ignore: Return BLE_GAP_REPEAT_PAIRING_IGNORE.  The stack will silently 
ignore the pairing request.


  was:
If a device is already bonded, the host should not allow the same device to 
pair again.  Currently, the host blindly proceeds with the pairing operation.  
This should not be allowed because the second peer could be an imposter 
masquerading as the original.

I propose the following behavior in such a scenario:
# Host notifies application of the duplicate pairing attempt via the gap event 
callback.  The callback would specify a new event code that specifically 
indicates a duplicate pairing attempt.
# The gap event callback would return an error code indicating which of the 
following behaviors to perform:
## Reject the pairing request.
## Delete the original bond and proceed with the pairing operation.

Summary: BLE Host - Ignore pairing attempt from already bonded peer  
(was: BLE Host - Reject pairing attempt from already bonded peer)

> BLE Host - Ignore pairing attempt from already bonded peer
> --
>
> Key: MYNEWT-750
> URL: https://issues.apache.org/jira/browse/MYNEWT-750
> Project: Mynewt
>  Issue Type: Bug
>  Components: Nimble
>Reporter: Christopher Collins
>Assignee: Christopher Collins
> Fix For: v1_1_0_rel
>
>
> If a device is already bonded, the host should not allow the same device to 
> pair again.  Currently, the host blindly proceeds with the pairing operation. 
>  This should not be allowed because the second peer could be an imposter 
> masquerading as the original.
> I propose the following behavior in such a scenario:
> # Host notifies application of the duplicate pairing attempt via the gap 
> event callback.  The callback would specify a new event code that 
> specifically indicates a duplicate pairing attempt.
> # The gap event callback would return an error code indicating which of the 
> following behaviors to perform:
> ## Retry: Return BLE_GAP_REPEAT_PAIRING_RETRY after deleting the conflicting 
> bond.  The stack will verify the bond has been deleted and continue the 
> pairing procedure.  If the bond is still present, this event will be reported 
> again.
> ## Ignore: Return BLE_GAP_REPEAT_PAIRING_IGNORE.  The stack will silently 
> ignore the pairing request.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (MYNEWT-748) SensorAPI: Add BME280 support to mynewt along with pressure, temperature and humidity support

2017-05-17 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/MYNEWT-748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16013813#comment-16013813
 ] 

ASF subversion and git services commented on MYNEWT-748:


Commit f2a8e66af0947699269814ff13fa562fc27323d5 in incubator-mynewt-core's 
branch refs/heads/bluetooth5 from [~vrahane]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-core.git;h=f2a8e66 
]

MYNEWT-748 SensorAPI: Add BME280 support

- Make OIC observe rate configurable
- Use the OIC observe rate as the LED blink rate in the app


> SensorAPI: Add BME280 support to mynewt along with pressure, temperature and 
> humidity support
> -
>
> Key: MYNEWT-748
> URL: https://issues.apache.org/jira/browse/MYNEWT-748
> Project: Mynewt
>  Issue Type: New Feature
>Reporter: Vipul Rahane
>Assignee: Vipul Rahane
> Fix For: v1_1_0_rel
>
>
> Add SPI driver for BME280 along with pressure, temperature and humidity 
> support in SensorAPI. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (MYNEWT-748) SensorAPI: Add BME280 support to mynewt along with pressure, temperature and humidity support

2017-05-17 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/MYNEWT-748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16013812#comment-16013812
 ] 

ASF subversion and git services commented on MYNEWT-748:


Commit 1dc1635810bd5b0eea1c3faed1675d9139e2a32d in incubator-mynewt-core's 
branch refs/heads/bluetooth5 from [~vrahane]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-core.git;h=1dc1635 
]

MYNEWT-748 SensorAPI: Add BME280 support

SensorAPI support for pressure, temperature and humidity

- Add temperature, pressure, humidity support
- change temperature handling for bno055
- fix bugs with register values


> SensorAPI: Add BME280 support to mynewt along with pressure, temperature and 
> humidity support
> -
>
> Key: MYNEWT-748
> URL: https://issues.apache.org/jira/browse/MYNEWT-748
> Project: Mynewt
>  Issue Type: New Feature
>Reporter: Vipul Rahane
>Assignee: Vipul Rahane
> Fix For: v1_1_0_rel
>
>
> Add SPI driver for BME280 along with pressure, temperature and humidity 
> support in SensorAPI. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (MYNEWT-748) SensorAPI: Add BME280 support to mynewt along with pressure, temperature and humidity support

2017-05-17 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/MYNEWT-748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16013811#comment-16013811
 ] 

ASF subversion and git services commented on MYNEWT-748:


Commit ad7cdf093a9cf325df02b4a27bcf1d70529dce9f in incubator-mynewt-core's 
branch refs/heads/bluetooth5 from [~vrahane]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-core.git;h=ad7cdf0 
]

MYNEWT-748 SensorAPI: Add BME280 support

- SensorAPI pressure, temperature and humidity support
- Compiles


> SensorAPI: Add BME280 support to mynewt along with pressure, temperature and 
> humidity support
> -
>
> Key: MYNEWT-748
> URL: https://issues.apache.org/jira/browse/MYNEWT-748
> Project: Mynewt
>  Issue Type: New Feature
>Reporter: Vipul Rahane
>Assignee: Vipul Rahane
> Fix For: v1_1_0_rel
>
>
> Add SPI driver for BME280 along with pressure, temperature and humidity 
> support in SensorAPI. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)