Rockbox Development > Feature Ideas

Disable Radio?

<< < (5/6) > >>

Llorean:
So any time a config file is loaded (every boot of the player) that contains settings that aren't allowed to change *from the original default* a password is needed?

This would basically mean to use the player if you changed any of these settings from the default, you'd need to put in the password every boot.

ve4cib:
I honestly don't know if that would be the case or not.  As I said, I haven't looked at the code, so I don't know what the architectural changes would have to be to let that kind of password-protected feature lockdown occur.  I was just throwing ideas out there for discussion.

I was working under the assumption that launching a plugin and loading the plugin were two different things.  You load everything at startup, but when you actually go to execute something that's locked-down you're prompted for a password.

If, for example, you choose to lock down Solitaire you you would be prompted for a password the first time you launch Solitaire from the Games menu after booting up.  If you lock down the mpeg plugin you'd be asked for a password the first time you try playing a movie since your last boot.  And so on with every other locked feature.

Llorean:
I was talking about the settings aspect, not the plugins aspect. You are aware that settings are saved in a .cfg file, which is then loaded upon boot, and that other .cfg files can be loaded? Thus if any setting is "protected" any time a .cfg file changed it (such as restoring your settings, every boot) it would request the password.

Not to mention, plugins really are plugins. If someone wanted to they could just download our version of the plugin here and play the unprotected version.

ve4cib:
I'm not entirely sure I follow what you're saying...

Settings are stored in a .cfg.  Fine.  I don't see why that's an issue.  Why would you ever be prompted for a password when loading settings?  It's not the settings that are protected.  It's the actual launcher that would require the password.  Unless the radio or mpeg plugin is actually executed during startup then you shouldn't get a prompt until you actually go to the menu and launch that feature.


--- Quote ---Not to mention, plugins really are plugins. If someone wanted to they could just download our version of the plugin here and play the unprotected version.
--- End quote ---

Plugins are plugins... yes.  Yes they are.  I don't understand your point.

And yes, to get around the password protection on a given feature you could always reinstall the system.  But to get around a compiled-out radio feature you could do the same thing.  So the level of security is the same between the two.

Llorean:
Your original description talks about being able to disable every FEATURE, not just plugins. So I discussed it in relation to all the non-plugin features (settings being the vast majority of them).

I don't see why you're confused by this, unless you really meant "just plugins" and your earlier post was misleading.

Navigation

[0] Message Index

[#] Next page

[*] Previous page