Bugzilla – Bug 9214
Add support for player PIN authentication to SC
Last modified: 2009-09-11 19:51:36 UTC
Many users use ssh when traveling with an SB to connect back to their home SC installation. In many cases this is overkill (and complex) since, IMO, there's no real reason for the streaming audio to go over a tunnel. All that needed to safely expose SC to the internet is a way to authenticate players that try to connect. (SC already has password protection for the web interface.) I'm wondering if the SN player PIN authentication scheme could be ported to SC. There would be an SC option to "Enable player authentication". If this is on, when a player tries to connect, it gets a PIN which must first be entered in SC before it's allowed to connect. Does this sound reasonable? There have been requests to integrate an ssh client into either the player or SBC firmware, but feedback on those hasn't been encouraging...
Interesting idea, Fletch. If a player had been connected locally, then we could verify its UUID, right? Otherwise, what about just enabling password protection on the player itself?
There's probably a lot of ways to do this. I just figured that copying what SN does would require the least amount of new code. To be honest, I'm not sure I understand why SN uses a PIN instead of just entering the UUID on SN. (UUID = MAC Address, right?) Regarding using the password on the player, that would work too. There would probably be requests, though, to have a way to password protect SC and not the player(s) (or vice versa).