Ticket #527 (assigned defect)
The BlueTooth broadcast ID is set wrong (patch)
| Reported by: | oe@… | Owned by: | marcel@… |
|---|---|---|---|
| Priority: | high | Milestone: | |
| Component: | bluez | Version: | current svn head |
| Severity: | minor | Keywords: | |
| Cc: | buglog@… | Blocked By: | |
| Blocking: | Estimated Completion (week): | ||
| HasPatchForReview: | PatchReviewResult: | ||
| Reproducible: |
Description
The "bluez" packages as provided by OE ships a default hcid.conf for the Neo.
Attached patch against openmoko/trunk/oe adds an updated version of bluez to the
OM SVN repository, overriding the package from the OE snapshot.
The changes:
- BlueTooth? broadcast ID changed to "Neo1973"
- Password changed to "1973"
Attachments
Change History
Changed 6 years ago by oe@…
- Attachment om-fix-bluetooth-ident.patch added
comment:1 Changed 6 years ago by marcel@…
- Status changed from new to assigned
The passkey is disabled anyway, but we will also remove it from the default
configuration.
The default friendly name will be "Neo1973" in the final release. Currently we
are working on getting the next bluez-utils ready and after that rebase the OE
patches.
comment:3 Changed 6 years ago by marcel@…
A default passkey is a security issue and will _NOT_ be used in OpenMoko?.
comment:4 Changed 6 years ago by oe@…
That was a misunderstanding on my part then.
I was under the impression that a "blank" password for BT would be set (which
indeed would be a security issue).
I now understand that per default the BT password is disabled which is of course
the best solution.
comment:5 Changed 6 years ago by stefan@…
As we use OE.dev upstream now and the passkey is disabled by default, all goes
down to the broadcast name, right?

Set BlueTooth? broadcast ID to Neo1973