[mythtv] Latest commits have broken UPNP database lookup

[Peter Bennett]

On 11/13/2017 04:55 PM, David Hampton wrote:
> Will it ask before connecting?  How do I keep my test/master frontend
> from finding my 0.28/production backend and attempting to upgrade its
> database?  Run both test frontend and backend in a VM so there's no
> traffic on my home network?  Unplug the ethernet from my workstation
> while testing?:-)   I want to make sure I don't mess up my production
> system.
>
> David
Hi David

If your backend PIN is 0000 and only one backend is running then it will 
connect without even asking.

Run mythtv-setup on your production backend and set a unique pin that is 
not 0000. That is what I do to prevent inadvertent connection to the 
production system. Note the pin does not have to be 4 digits or numeric. 
It can be a whole sentence, but only if it is 0000 will it connect 
automatically.

I recommend also using different database names, user ids and passwords 
for production and development. If everything is mythconverg / mythtv / 
mythtv there may be more risk of inadvertently connecting to the wrong 
place.

A remote frontend or backend will not update the backend database. I 
don't know the details of how it checks, but it does log a message about 
not being authorized to upgrade.

The times when I have inadvertently connected to my production system 
were when I had a production frontend on my development machine, then 
inadvertently started up a development backend. It goes to 
.mythtv/config.xml and connects - PIN numbers or passwords do not 
protect in this case because everything is in the config.xml. Nowadays I 
have a set of scripts that isolate my various versions so that this type 
of thing cannot happen. I avoid having a .mythtv directory at all on my 
user id on the development system.

Let me know if you need more information.

Regards
Peter