Blocking malware sites is blocking Spotify Connect on Naim Streamer?

Posted by: Silence Kills on 18 November 2015

Quite strange, I could not make it to choose my Naim Streamer as a Spotify Connect client for two days now. Local network discovery worked, it showed the Streamer inside the Naim App on an iPad. But when selecting the Naim Streamer it returned to iPad as audio output after a few seconds. Connecting to Spotify Connect on a Mac, running the Spotify Application, worked without a problem.

 

I then took a deep look at my OpenBSD router which blocks "some" sites by using several blocklists. It turned out the the evil list was

http://www.malwaredomainlist.com/hostslist/hosts.txt

from

http://www.malwaredomainlist.com

 

By disabling the blocklist from malwaredomainlist.com, Spotify Connect works on the Naim (FW 4.4) again without any problems.

 

Now the big question: Which of the (suspicious) malware domains from malwaredomainlist does Spotify Connect need to be able to connect to? Quite strange that a list to block malware domains blocks Spotify Connect as well.

 

Must be one of the last ones here since 2015/11/16

http://www.malwaredomainlist.com/update.php

All of them are of type "compromised site leads to Angler EK".

Angler Exploit Kit:

https://blogs.sophos.com/2015/...-angler-exploit-kit/

Posted on: 20 November 2015 by Phil Harris
Originally Posted by Silence Kills:

Quite strange, I could not make it to choose my Naim Streamer as a Spotify Connect client for two days now. Local network discovery worked, it showed the Streamer inside the Naim App on an iPad. But when selecting the Naim Streamer it returned to iPad as audio output after a few seconds. Connecting to Spotify Connect on a Mac, running the Spotify Application, worked without a problem.

 

I then took a deep look at my OpenBSD router which blocks "some" sites by using several blocklists. It turned out the the evil list was

http://www.malwaredomainlist.com/hostslist/hosts.txt

from

http://www.malwaredomainlist.com

 

By disabling the blocklist from malwaredomainlist.com, Spotify Connect works on the Naim (FW 4.4) again without any problems.

 

Now the big question: Which of the (suspicious) malware domains from malwaredomainlist does Spotify Connect need to be able to connect to? Quite strange that a list to block malware domains blocks Spotify Connect as well.

 

Must be one of the last ones here since 2015/11/16

http://www.malwaredomainlist.com/update.php

All of them are of type "compromised site leads to Angler EK".

Angler Exploit Kit:

https://blogs.sophos.com/2015/...-angler-exploit-kit/

 

Hi,

 

Our software guys have taken a quick look at that blocklist and suspect that it's not as accurate as you might wish it to be.

 

The information I have had back is that based on the content of that list it looks like someone has possibly purposely poisoned the content of the list, so a bad domain is pointing to servers that they don't own ... hence the malware list becomes its own enemy as it is blocking genuine domains / sites / services.

 

Cheers

 

Phil

Posted on: 20 November 2015 by Silence Kills

Hello Phil,

 

thanks a lot for your answer and your effort. Many thanks to the software guys, too.

That evening I just made Spotify Connect to work again and wanted to take a deeper look into it at the weekend.