Public bug reported:

Binary package hint: slimserver

By default (/etc/default/slimserver), slimserver is configured for
access only by the local host, not by the network.  I would argue that
essentially everyone who installs the slimserver package wants to allow
network access and that that default should be changed.  It's like
installing Apache with access limited to localhost.  It just ends up
being a hurdle for inexperienced users.

A story: I installed the slimserver package and tested it locally,
didn't notice that it was limited to localhost.  Then I purchased and
set up a Squeezebox hardware device.  Interestingly, even with
slimserver configured for localhost access only, the Squeezebox found
and was able to download the music library from the slimserver, over the
network. (I think this is because only port 9000 was limited to
localhost, and the slimserver does other stuff on port 3483, which was
not limited to localhost.)  However, when one then attempts to play
music from the slimserver, the Squeezebox throws an error: "Problem:
can't connect to server".  This error is not covered anywhere in the
Squeezebox documentation, but I was able to figure out that the server
was only listening to localhost and change it.

I'm a relatively experienced user and it took me 30 minutes or more to
fix this.  One hundred percent of Squeezebox users will have this exact
problem, and when they try to get support for it, they'll probably
mostly get advice about firewalls blocking access and such, which will
have them barking up the wrong tree.  The whole point of this app is to
stream music over the network... the current default configuration has
to be changed by everyone who uses this app.  Either change the default
(preferred) or at least have a high-importance apt question so that the
user can allow network access when the package is installed.

** Affects: slimserver (Ubuntu)
     Importance: Undecided
         Status: New

-- 
slimserver defaults to no external access
https://bugs.launchpad.net/bugs/178588
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to