PsyPhi

Version 1.42 was automatically downloaded to my computer without any problems or even any explicit indication that the update had occurred. Today, I noticed the news of the release at the bottom of the updater screen ('Update' tab), and verified that I had been updated by clicking the 'About' tab. Since I had heard (via this forum) that the IP Ignore feature was planned for 1.42, I looked for evidence of the change, and discovered the new menu item in the tray pop-up. I had been experiencing blocking when trying to listen to a particular internet radio station (Pure.FM @ IP 95.211.85.75), and reported it as a potential false positive. The reply informed me that the blocking was "not an F/P", since there were known real threats in "this range" (I assume that means the set of IPs with addresses of 95.211.85.*, or perhaps 95.211.*.*). I was told that infections via streaming audio broadcasts were "not very common", and it was reasonably safe to "temporarily disable the IP Protection whilst accessing the stream". However, this didn't seem like a viable workaround in my case, since I wanted to be able to access other websites and email safely while listening to internet radio in the background. I requested the capabilty to exclude specific IP addresses from the blocking, and then learned that such a feature was already in the pipeline for v1.42. I had suggested a mechanism for directly adding items to the ignore list, or alternatively a new button in the blocking alert message. However, the implementation via a new menu item seems even cleaner, and probably much safer because it's less likely to encourage a user to get in the habit of ignoring the IP every time a block occurs. So I tried listening to Pure.FM again, and when the blocking alert came up, I was able to add 95.211.85.75 to the ignore list. The station then played normally (every time, without any repeated action required). A simple test reassured me that blocking other IPs was still enabled, and the new exception was specific to the single IP rather than a range - I could access 95.211.85.75 via my browser, but 95.211.85.74 remained blocked. Very nice! Thanks for adding this useful new feature! a happy customer, PsyPhi

I tried turning off the IP Protection feature, and was then able to access the (previously blocked) stations, but when I turned the IP Protection back on, within a few seconds the blocking alert popped up again and the music stopped playing. I guess I should have expected this

When you say "range", are you referring to other ports of 95.211.85.75 (the internet stations I want to listen to are at 95.211.85.75:80 & 95.211.85.75:8000), or do you mean some collection of "neighboring" IP address (such as all IP addresses of the form 95.211.85.xxx)? Does the IP blocking feature use such range designations because relevant characteristics are likely to be shared among members of the range (say, a bank of servers in the same physical building, or a common ISP)? Or is it simply a convenience to make your IP database a manageable size (a reasonable compromise if it significantly reduces the program's footprint and/or response time)?

Wow, I'm impressed! I suggested the improvement less than 24 hours ago, and already you guys are working on implementing it!! Thanks!!! your facetious fan, PsyPhi

Well, it would be handy if an IP address could be added to this list. Say, for example, Malwarebytes is blocking access to a website that you know is safe (or you are willing to accept the risk in that particular case). If you could specify exceptions to IP blocking, then you wouldn't need to turn off *all* IP checking/blocking (and expose yourself to myriad threats) to access a single website. Of course, this enhancement need not be implemented via manual editing of the Ignore List. A cleaner solution might be to have a button in the IP blocking alert that let you turn off blocking for only the reported IP.

Is it possible to get infected/victimized by malware simply from listening to streaming internet radio? Would it be safe to temporarily disable Malwarebytes IP protection so I can access these stations?

Whenever I attempt to listen to internet radio stations from Pure.FM (using either iTunes or Windows Media Player), Malwarebytes pops up a balloon over the task bar indicating that it has blocked access to IP 95.211.85.75 (and the station doesn't play). I don't know if this is a false positive or a real threat. I can access other stations OK.