Hi all,
Thanks first of all for this great 0.2.6 update of vompserver. I also like all the initiatives to start developing mp3 and/or avi/mpg support.
I decided I am now for so long a "happy user", I should try to contribute something myself. I decided to focus on the long-wished, never realised (AFAIK) parental lock support (or better, child lock support; the parent isn't locked out of anything).
My first action was to install the pin-0.1.7 plugin of VDR, which seems to be an excellent basis to start from.
I am planning a step-by-step approach, each step adding new child lock functionality:
1) First step would be to add a parameter to the vomp-MAC-address.conf file, Childlock = On or Off. When On, the vomp-server plugin:
-checks for the existence of the protection.fsk file (put there by pin-plugin) when browsing through directories or trying to open recordings, and prohibits operation when file is present
-when jumping to a channel (live tv), check whether this channel is blocked by pin-plugin, and act accordingly.
-prohibit to start a timer from a blocked channel (actually, this seems to be a security leak in the pin-plugin version 0.1.7; autoprot functionality does not work for me!), or if it can be started, it generates a blocked recording.
Note that in step one you childlock a media-mvp box or not, and the decision is made at operating system level.
2) Second step would be, instead of blocking the above, asking for the pin-number configured in pin-plugin. Also the auto-timeout to childlock after x minutes of pin-plugin should be active on vompserver-plugin, and the "activate childlock now" functionality.
3) Third step could be, to add extended blocking support as supported by pin-plugin, like blocking broadcast and extended search patterns in blocking.
4) Fourth step could be, to enable adding file locks and/or channel locks and other pin-configuring stuff from the vomp-server plugin.
This way also users without OSD access to vdr-server could use functionality also. This pin-configuring stuff would also have to be protected by same pin-code, of course.
Also, all changes should have no effect to those not having a Childlock entry in their vomp-MAC.conf file or not using pin-plugin at all.
My questions to you:
1) Is pin-0.1.7 plugin actually the best basis to start from, or are there even better alternatives?
2) Can anyone hint me on which steps should be best done in client part, and which in server part?
3) I have some experience developing vdr-related software, but I have no setup on which I can cross-compile the client (dongle) software. Anyone with those capabilities like to join?
4) Other hints, tips, ...
Happy to hear from you!
Thanks first of all for this great 0.2.6 update of vompserver. I also like all the initiatives to start developing mp3 and/or avi/mpg support.
I decided I am now for so long a "happy user", I should try to contribute something myself. I decided to focus on the long-wished, never realised (AFAIK) parental lock support (or better, child lock support; the parent isn't locked out of anything).
My first action was to install the pin-0.1.7 plugin of VDR, which seems to be an excellent basis to start from.
I am planning a step-by-step approach, each step adding new child lock functionality:
1) First step would be to add a parameter to the vomp-MAC-address.conf file, Childlock = On or Off. When On, the vomp-server plugin:
-checks for the existence of the protection.fsk file (put there by pin-plugin) when browsing through directories or trying to open recordings, and prohibits operation when file is present
-when jumping to a channel (live tv), check whether this channel is blocked by pin-plugin, and act accordingly.
-prohibit to start a timer from a blocked channel (actually, this seems to be a security leak in the pin-plugin version 0.1.7; autoprot functionality does not work for me!), or if it can be started, it generates a blocked recording.
Note that in step one you childlock a media-mvp box or not, and the decision is made at operating system level.
2) Second step would be, instead of blocking the above, asking for the pin-number configured in pin-plugin. Also the auto-timeout to childlock after x minutes of pin-plugin should be active on vompserver-plugin, and the "activate childlock now" functionality.
3) Third step could be, to add extended blocking support as supported by pin-plugin, like blocking broadcast and extended search patterns in blocking.
4) Fourth step could be, to enable adding file locks and/or channel locks and other pin-configuring stuff from the vomp-server plugin.
This way also users without OSD access to vdr-server could use functionality also. This pin-configuring stuff would also have to be protected by same pin-code, of course.
Also, all changes should have no effect to those not having a Childlock entry in their vomp-MAC.conf file or not using pin-plugin at all.
My questions to you:
1) Is pin-0.1.7 plugin actually the best basis to start from, or are there even better alternatives?
2) Can anyone hint me on which steps should be best done in client part, and which in server part?
3) I have some experience developing vdr-related software, but I have no setup on which I can cross-compile the client (dongle) software. Anyone with those capabilities like to join?
4) Other hints, tips, ...
Happy to hear from you!