1. 19 4月, 2011 1 次提交
  2. 13 4月, 2011 1 次提交
  3. 05 4月, 2011 2 次提交
  4. 01 4月, 2011 6 次提交
  5. 25 3月, 2011 1 次提交
  6. 22 2月, 2011 2 次提交
  7. 18 2月, 2011 1 次提交
  8. 17 2月, 2011 5 次提交
  9. 08 2月, 2011 13 次提交
  10. 20 1月, 2011 1 次提交
  11. 23 12月, 2010 1 次提交
  12. 02 12月, 2010 5 次提交
  13. 09 11月, 2010 1 次提交
    • J
      Bluetooth: Fix non-SSP auth request for HIGH security level sockets · bdb7524a
      Johan Hedberg 提交于
      When initiating dedicated bonding a L2CAP raw socket with HIGH security
      level is used. The kernel is supposed to trigger the authentication
      request in this case but this doesn't happen currently for non-SSP
      (pre-2.1) devices. The reason is that the authentication request happens
      in the remote extended features callback which never gets called for
      non-SSP devices. This patch fixes the issue by requesting also
      authentiation in the (normal) remote features callback in the case of
      non-SSP devices.
      
      This rule is applied only for HIGH security level which might at first
      seem unintuitive since on the server socket side MEDIUM is already
      enough for authentication. However, for the clients we really want to
      prefer the server side to decide the authentication requrement in most
      cases, and since most client sockets use MEDIUM it's better to be
      avoided on the kernel side for these sockets. The important socket to
      request it for is the dedicated bonding one and that socket uses HIGH
      security level.
      
      The patch is based on the initial investigation and patch proposal from
      Andrei Emeltchenko <endrei.emeltchenko@nokia.com>.
      Signed-off-by: NJohan Hedberg <johan.hedberg@nokia.com>
      Acked-by: NMarcel Holtmann <marcel@holtmann.org>
      Signed-off-by: NGustavo F. Padovan <padovan@profusion.mobi>
      bdb7524a