[SOLVED] Repeated Security Risk Messages in Logs

For discussion of topics specific to MythTV on OSX
Post Reply
leejk
Junior
Posts: 65
Joined: Wed Mar 18, 2015 1:51 am

[SOLVED] Repeated Security Risk Messages in Logs

Post by leejk » Wed Mar 18, 2015 1:58 am

Hello,

I've been trying to find a solution for this for a while now, but have come up empty handed. I am running Myth 0.27.4 on Yosemite. Functionally everything is good, but I keep getting the following message in the backend logs:

Code: Select all

2015-03-17 21:44:50.335266 C [333/11783] SSDP ssdp.cpp:339 (ProcessData) - SSDP Request from WAN IP address (0.0.0.0). Possible SSDP Reflection attempt. Ignoring as security risk.
This entry is getting generated about every second in the logs, and it is literally littering the log files, making trying to find valid information pretty hard. I have tried disabling IPv6 as someone in this post suggested: https://code.mythtv.org/trac/ticket/12305
That did not help. Can someone suggest any thing else to try, and maybe explain what causes Myth to output this message?

thx
Last edited by leejk on Thu Mar 19, 2015 2:39 am, edited 2 times in total.

User avatar
stuartm
Developer
Posts: 129
Joined: Wed Feb 05, 2014 5:17 pm
Great Britain

Re: Repeated Security Risk Messages in Logs

Post by stuartm » Wed Mar 18, 2015 12:24 pm

Please upgrade, this was fixed weeks ago.

leejk
Junior
Posts: 65
Joined: Wed Mar 18, 2015 1:51 am

Re: Repeated Security Risk Messages in Logs

Post by leejk » Wed Mar 18, 2015 10:22 pm

stuartm wrote:Please upgrade, this was fixed weeks ago.
I'd like to, but I'm using the macports version and not sure I can overwrite it with another build. Which version do most Mac users install?

thx

tvdave
Junior
Posts: 57
Joined: Sun Jun 29, 2014 10:11 am
Australia

Re: Repeated Security Risk Messages in Logs

Post by tvdave » Wed Mar 18, 2015 10:29 pm

I understand that if you are using Macports you need to remain with it.

User avatar
pvr4me
Senior
Posts: 723
Joined: Fri Feb 07, 2014 7:25 pm
Location: near Toronto, Canada
Contact:
Canada

Re: Repeated Security Risk Messages in Logs

Post by pvr4me » Thu Mar 19, 2015 2:37 am

leejk wrote:
stuartm wrote:Please upgrade, this was fixed weeks ago.
I'd like to, but I'm using the macports version and not sure I can overwrite it with another build. Which version do most Mac users install?
Sorry, I need to cut a new installer with a more recent version of 0.27.4-fixes. Time has been very short recently but I will get to this soon. The new version will install over top of the existing version with no upgrade or migration required.

Craig
The MacPorts guy.

User avatar
pvr4me
Senior
Posts: 723
Joined: Fri Feb 07, 2014 7:25 pm
Location: near Toronto, Canada
Contact:
Canada

Re: Repeated Security Risk Messages in Logs

Post by pvr4me » Thu Mar 19, 2015 2:40 am

tvdave wrote:I understand that if you are using Macports you need to remain with it.
Just to be clear, it is not like there is any lock in or anything. Your recordings are in whatever folder you directed Myth to put them in. You can backup your database and restore it somewhere else with no MacPorts-related issues. (Ie, just the normal stuff if you migrate to a new backend, etc.)

Craig
The MacPorts guy.

leejk
Junior
Posts: 65
Joined: Wed Mar 18, 2015 1:51 am

Re: Repeated Security Risk Messages in Logs

Post by leejk » Thu Mar 19, 2015 10:05 pm

pvr4me wrote:
leejk wrote:
stuartm wrote:Please upgrade, this was fixed weeks ago.
I'd like to, but I'm using the macports version and not sure I can overwrite it with another build. Which version do most Mac users install?
Sorry, I need to cut a new installer with a more recent version of 0.27.4-fixes. Time has been very short recently but I will get to this soon. The new version will install over top of the existing version with no upgrade or migration required.

Craig
No problem, I understand. I was just hoping to find a workaround in the meantime.

rgds

leejk
Junior
Posts: 65
Joined: Wed Mar 18, 2015 1:51 am

Re: Repeated Security Risk Messages in Logs

Post by leejk » Sat Mar 28, 2015 1:17 pm

This problem was fixed by the latest MacPorts release... thanks Craig!

Post Reply