[bluez/bluez] e9a8e8: mesh: Correct size of friend cache

[bluez/bluez] e9a8e8: mesh: Correct size of friend cache

[Isak Westin]

  Branch: refs/heads/master
  Home:   https://github.com/bluez/bluez
  Commit: e9a8e884109c1fb3ee075115cb28312dd2716669
      https://github.com/bluez/bluez/commit/e9a8e884109c1fb3ee075115cb28312dd2716669
  Author: Isak Westin <isak.westin@loytec.com>
  Date:   2022-10-06 (Thu, 06 Oct 2022)

  Changed paths:
    M mesh/friend.c

  Log Message:
  -----------
  mesh: Correct size of friend cache

The cache size communicated to the Low Power node should be the same as
the cache size actually used.


  Commit: 7ff3e10d92bac299f541d365057f422d0282e483
      https://github.com/bluez/bluez/commit/7ff3e10d92bac299f541d365057f422d0282e483
  Author: Isak Westin <isak.westin@loytec.com>
  Date:   2022-10-06 (Thu, 06 Oct 2022)

  Changed paths:
    M mesh/net.c

  Log Message:
  -----------
  mesh: Verify padding bits in Friend Poll messages

The padding bits in a Friend Poll message must be zero.
See MshPRFv1.0.1 section 3.6.5.1.


  Commit: 3f3a7b8e192f210b7119b30e8c840e13993134a9
      https://github.com/bluez/bluez/commit/3f3a7b8e192f210b7119b30e8c840e13993134a9
  Author: Isak Westin <isak.westin@loytec.com>
  Date:   2022-10-06 (Thu, 06 Oct 2022)

  Changed paths:
    M mesh/net.c

  Log Message:
  -----------
  mesh: Queue a friend update on IV Update change

A friend update should be queued when we receive a Secure Network beacon
that changes the IV Update state.


  Commit: c89e9c4b22b4f32c5b4dee396caf5fc54b434da2
      https://github.com/bluez/bluez/commit/c89e9c4b22b4f32c5b4dee396caf5fc54b434da2
  Author: Isak Westin <isak.westin@loytec.com>
  Date:   2022-10-06 (Thu, 06 Oct 2022)

  Changed paths:
    M mesh/net.c

  Log Message:
  -----------
  mesh: Always relay messages from Low Power nodes

If we receive a message from one of our Low Power nodes, which is
encrypted using frendship credentials and where the destination is not
us, we must relay that message using master credentials.
See MshPRFv1.0.1 section 3.6.6.2.


  Commit: 95bf980b015ee4cb549568d18dd4db6c3f74aa4a
      https://github.com/bluez/bluez/commit/95bf980b015ee4cb549568d18dd4db6c3f74aa4a
  Author: Isak Westin <isak.westin@loytec.com>
  Date:   2022-10-06 (Thu, 06 Oct 2022)

  Changed paths:
    M mesh/node.c

  Log Message:
  -----------
  mesh: Update Key Refresh flag after provision

The Key Refresh flag in the Secure Network beacon is now correctly
updated based on provisioning data after being successfully provisioned.


  Commit: c1f1a49aeb1518fa8a808e107573399acab2bd86
      https://github.com/bluez/bluez/commit/c1f1a49aeb1518fa8a808e107573399acab2bd86
  Author: Isak Westin <isak.westin@loytec.com>
  Date:   2022-10-06 (Thu, 06 Oct 2022)

  Changed paths:
    M mesh/prov-acceptor.c

  Log Message:
  -----------
  mesh: provisionee: Handle unknown PDUs

If an unknown PDU is received during provisioning, the provisioning
should fail with "Invalid PDU".


  Commit: 77da94eb7a8c8cbeb6db0e0ce31501d08f02ca86
      https://github.com/bluez/bluez/commit/77da94eb7a8c8cbeb6db0e0ce31501d08f02ca86
  Author: Isak Westin <isak.westin@loytec.com>
  Date:   2022-10-06 (Thu, 06 Oct 2022)

  Changed paths:
    M mesh/prov-acceptor.c

  Log Message:
  -----------
  mesh: provisionee: Handle failed provisioning

When a provisioning fails, all additionally received PDU should be
unexpected until link is closed by provisioner. See MshPRFv1.0.1 section
5.4.4.


  Commit: 838ddc931263b5582b6170e09878fc0c4337506b
      https://github.com/bluez/bluez/commit/838ddc931263b5582b6170e09878fc0c4337506b
  Author: Isak Westin <isak.westin@loytec.com>
  Date:   2022-10-06 (Thu, 06 Oct 2022)

  Changed paths:
    M mesh/prov-acceptor.c

  Log Message:
  -----------
  mesh: provisionee: Check prov start parameters

Verify that all parameters in a Provisioning Start PDU are valid, also
compared to the capabilities that has been sent.


Compare: https://github.com/bluez/bluez/compare/e71e1103abc6...838ddc931263