Bugzilla – Bug 10087
Backup alarm does not work if SC is password-protected
Last modified: 2009-06-17 09:35:45 UTC
Is there no way this can be done in time for 7.3? Without this sufferers either have to have no backup alarm or no security on the server - neither are good situations to be in.
It's QA's call whether it's a serious enough bug for 7.3.
We are now planning to make a 7.3.3 release. Please review your bugs (all marked open against 7.3.3) to see if they can be fixed in the next few weeks, or if they should be retargeted for 7.4 or future. Thanks!
Since there's now a planned 7.3.3 release, bugs which won't make the cut-off are being moved to the next target out. If you feel that this bug needs to be addressed more (or less) urgently than the 7.4 release, please cc chris@slimdevices.com and leave a comment in the bug to that effect so we can review it. Thanks.
I feel that this bug needs to be addressed more urgently than the 7.4 release. It seems to get bumped onto the next release each time even though this can be considered as a security issue. The only workaround for this bug is to run your server without password protection which for some setups is a security risk.
I'm not sure why this keeps getting bumped either. Doesn't even look like it has been looked at yet. For anybody running this on a network it is standard practice to secure something like this with a password. Anybody following good practice is sooner or later going to end up with an alarm failure (as we did). Alarm failures are not a trivial matter. I can't believe this is a difficult bug to fix. It is a well defined issue with complete reproducibility. I would have expected it to be fairly straight forward to track down. yeah I know, I hate it when people say that to me but I thought I would get my own back for a change :)
For some reason Bugzilla did not change the target when I did this yesterday. Or maybe it was me. In either case, I'm trying it again.
Andy will work on getting this fixed for 7.3.3 time frame
It has been looked at.
Fixed in change 26197.
Verified in 7.3.3 - 26303.
This bug has been fixed in the 7.3.3 release version of SqueezeCenter! If you haven't already. please download the new version from http://www.logitechsqueezebox.com/support/download-squeezecenter.html If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.