securing the bluetooth pairing with pin code?

[DariBer]

I have a question regarding securing Bluetooth pairing a device like iPhone with a Squeezelite-ESP32 . When pairing an iPhone or what ever using bluetooth, do you know if I can secure that process with maybe a 4 digit code? Cause now anyone who’s near (like on the street, neighbours in the house) can connect to it and start to play music, as it doesn’t need any code. So is there a chance to set a pin code and only the one who know that code can pair and start use the device for streaming?

[sle118]

This has been on my to-do list for a while. Il move that to a new issue to keep it on the radar.

[DariBer]

It would be really nice to have that security option, so if you implement it, thanx in advance :-)

[segdy]

Yes, please!!

[sle118]

I've managed to fix this in my local development environment, but this change will be extremely disruptive for our user base. We would need to move away from the current security protocol, back to the legacy "pin code" approach. Since we don't collect usage information, I can only imagine that the change might disrupt the daily use of the majority of our users. Unfortunately, it is not possible to make this an option either. Either we roll back to legacy pin code and cause some pain to existing users, or I need to find another "clever" way around this which will never really be complete. I might try to poll our user base to see what they think in the logitech forums and decide the path forward from there.

[sle118]

I have been extremely busy in recent months, with work often overlapping with spare time so unfortunately there wasn't much left to address this.

@emlynmac I was planning on implementing a "pair mode" as an option that allows pairing for a limited time, with clients being stored in a white list of mac addresses. But this is no small feature. I'm sure I can handle the bulk of this through command line (long ago I built a mechanism to surface these automatically in the UI). So what is needed is enabled pairing command (timed out Airways), then another command to remove some white listed devices.

I just don't know when I manage to get to this.

[emlynmac]

Is there a doc or something for where parts of the code are? I'd love to get more into this

[emlynmac]

@sle118 could we also make this a build option so those who want can use a different version?

[sle118]

see #217 (comment)

I will see if I can manage to do something in the current version, but I simply don't have any bandwidth right now.

[emlynmac]

@sle118 I read that, hence the offer to take that on further. You had written previously that you had it working locally, so that would be a point for me to start looking at.

[seancmalloy]

Any update on implementing secure bluetooth connection with pin? I have multiple networked speakers with squeezelite-esp32 in my condo and it's extremely annoying when someone connects it them but I want to keep the bluetooth option.

[sle118]

As stated in #342, the current version will be limited to bug fixes as the bulk of my spare time is dedicated to the refactoring of the system. Implementing changes in the current version had become very annoying as we have to fight for every byte on the flash storage, so it is unlikely that I will implement this feature in the old version.

It is still not clear to me if I'll be able to provide a version that fits in 4Mb of flash, but so far it seems that a limited version might be possible for devices with smaller flash chips.