Re: Regression caused by "Bluetooth: Map sec_level to link keyrequirements"

[Johan Hedberg]

Hi,

On Thu, Jun 09, 2011, Waldemar.Rymarkiewicz@xxxxxxxxx wrote:
> >I re-pair'ed using a manually entered a 16 digit pin, but now 
> >DUN setup doesn't succeed at all.
> 
> Did you try to remove all stored link keys and start again?
> If you already have a pincode which is insecure you have to remove it manually.
> 
> Try 'hciconfig hciX noauth noencrypt ' before.
> 
> Check syslog and switch debug on in the kernel first.

So I just realized that the BITE tests were only done for mgmtops.c and
not hciops.c. One critical difference is that conn->key_type will not be
set (or actually set to 0xff) for connections which happen after the
initial pairing has occurred. We're right now testing a one-line patch
which might fix the issue. Luiz will send it soon if it turns out to
work fine.

Johan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/