CHANGELOG.md (27ef8bc836da6d760bc5222c9f84020afdc31ed8) CHANGELOG.md (2b0d89b5b8203bb0b74b8df7621078e37ca2861f)
1# Change Log
2All notable changes to this project will be documented in this file.
3
4The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/)
5and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.html).
6
7## [Unreleased]
8
9### Added
1# Change Log
2All notable changes to this project will be documented in this file.
3
4The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/)
5and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.html).
6
7## [Unreleased]
8
9### Added
10- SM: support pairing using Out-of-Band (OOB) data with LE Secure Connections
11
12### Changed
13
14### Fixed
15
16## Changes March 2018
17
18### Added
10- GAP: allow to limit number of connections in LE Peripheral role with gap_set_max_number_peripheral_connections
11- ATT Server: support for delayed ATT read response, see example/att_delayed_read_response.c
12- ATT Server: allow to specify security requirements seperately for read/writes. .h files need to be regenerated
13
19- GAP: allow to limit number of connections in LE Peripheral role with gap_set_max_number_peripheral_connections
20- ATT Server: support for delayed ATT read response, see example/att_delayed_read_response.c
21- ATT Server: allow to specify security requirements seperately for read/writes. .h files need to be regenerated
22
14### Changed
15
16### Fixed
17- RFCOMM: fix infinite loop on L2CAP connection error (regression from 4c3eeed1)
18- HSP HS: accept incomming SCO connection
19- SM: fix iteration over LE Device DB entries for bonding and address resolving
20- SM: store pairing information only if both devices have requested bonding
21
22## Changes February 2018
23

--- 74 unchanged lines hidden --- 		23### Fixed
24- RFCOMM: fix infinite loop on L2CAP connection error (regression from 4c3eeed1)
25- HSP HS: accept incomming SCO connection
26- SM: fix iteration over LE Device DB entries for bonding and address resolving
27- SM: store pairing information only if both devices have requested bonding
28
29## Changes February 2018
30

--- 74 unchanged lines hidden ---