[mythtv] hello and question
michael at thewatsonfamily.id.au
Thu Dec 20 21:43:53 UTC 2012
On 21/12/2012 3:04 AM, Raymond Wagner wrote:
> On 12/19/2012 21:34, Michael Watson wrote:
>> On 20/12/2012 8:35 AM, Dan Wilga wrote:
>>> On 12/19/12 12:10 PM, Peter Hoopes wrote:
>>>> I'd like to implement a number of MythTV
>>>> Frontends across campus, but I would /really like/ to disable the
>>> Most likely, you'd also want to disable anything that makes permanent
>>> changes to the recordings or settings, like delete, transcode,
>>> commercial flagging, storage group changes, recording rule editing,
>>> etc. It sounds to me like you need a much dumber client than
>>> Mythfrontend. A DNLA-based player would probably be a good choice, or
>>> maybe XBMC with the MythTV plugin.
>> Wouldn't need the MythTV Plugin, just create a video source using
>> myth:// protocol (native to XBMC Eden)
> If you give access to the internal Myth protocol to the end users, all
> of the security issues mentioned come into play. There is no security
> in the internal protocol.
The users dont have access to the Myth Protocol, only XBMC Does!
XBMC access to Myth via the Myth Protocol gives the user a view only
access to the recordings, provides no ability to create/edit recording
schedules, does not provide functionality to start transcoding,
commercial flagging. And XBMC has the ability to prevent users from
entering Music / Pictures / etc and the ability to prevent changing of
video/music sources, and access to options, whereas MythTV Plugin in
XBMC gives access to recording schedules, livetv, transcoding and
Or you could use mythlink.pl and create a video source in XBMC set to
the output directory of mythlink.pl, thus having no direct link to
MythTV from the "Frontend"
More information about the mythtv-dev