The suggestion is very simple. Basically the user would need to provide a password when installing an extension/plugin.
The exact strength of the system could be configured. The admin of the OS could decide, if extensions need OS level admin privilege to install system wide. If they need just a local PM only password, or nothing for local installation. The system could be some hybrid of these three.
This seams to me very reasonable. It shouldn't be an add-on that does something like that, and PM could be configured to suit the needs of the users.
Password for installing extentions
Forum rules
Please keep everything here strictly on-topic.
This board is meant for Pale Moon source code development related subjects only like code snippets, patches, specific bugs, git, the repositories, etc.
This is not for tech support! Please do not post tech support questions in the "Development" board!
Please make sure not to use this board for support questions. Please post issues with specific websites, extensions, etc. in the relevant boards for those topics.
Please keep things on-topic as this forum will be used for reference for Pale Moon development. Expect topics that aren't relevant as such to be moved or deleted.
Please keep everything here strictly on-topic.
This board is meant for Pale Moon source code development related subjects only like code snippets, patches, specific bugs, git, the repositories, etc.
This is not for tech support! Please do not post tech support questions in the "Development" board!
Please make sure not to use this board for support questions. Please post issues with specific websites, extensions, etc. in the relevant boards for those topics.
Please keep things on-topic as this forum will be used for reference for Pale Moon development. Expect topics that aren't relevant as such to be moved or deleted.
-
squarefractal
Re: Password for installing extentions
You can do this by locking down the write permission for profiles.ini and the extensions directory in your profile folder, and then tossing in the .xpi in this directory whenever you need to install an extension.
-
New Tobin Paradigm
Re: Password for installing extentions
This will break extension updates.. It is NOT recommended.
-
Moonchild
- Pale Moon guru
- Posts: 35636
- Joined: 2011-08-28, 17:27
- Location: Motala, SE
Re: Password for installing extentions
You can lock this down with a corporate setup (e.g. mozilla.cfg) and setting the correct extension installation scope flags. Please do a web search for this, there's plenty of documentation out there. it won't add a password, but will prevent undesirable installation of extensions without proper system-wide account rights if done properly.
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
-
Omitooshi
Re: Password for installing extentions
^
I was more general in my post.
I still think that installing, basically little programs with out a password is a bit anomalous. It wouldn't improve security? And since it's configurable, it wont piss some users.
I was thinking, to force the user to choose in a easy to configure way. Not messing with config files. This should be for the average user, not just an admin. The recommended option would be i guess to have a local password for local installations. If he chooses no password, then he takes responsibility if bad things happen as a result.
I was more general in my post.
I still think that installing, basically little programs with out a password is a bit anomalous. It wouldn't improve security? And since it's configurable, it wont piss some users.
I was thinking, to force the user to choose in a easy to configure way. Not messing with config files. This should be for the average user, not just an admin. The recommended option would be i guess to have a local password for local installations. If he chooses no password, then he takes responsibility if bad things happen as a result.
-
LimboSlam
- Board Warrior
- Posts: 1029
- Joined: 2014-06-09, 04:43
- Location: USA
Re: Password for installing extentions
This does not sound easy at all and no user should be forced to use extra security. Also, wouldn't this effect installations of pictures, videos/audio and other stuff?Omitooshi wrote:......to force the user....... local installations........
With Pale Moon by my side, surfing the web is quite enjoyable and takes my headaches away! 
God is not punishing you, He is preparing you. Trust His plan, not your pain. #TrentShelton #RehabTime
God is not punishing you, He is preparing you. Trust His plan, not your pain. #TrentShelton #RehabTime
-
Omitooshi
Re: Password for installing extentions
^
I meant, to force them to choose between a password or no password. During installation i guess.
Not force them to use a password.
pictures/videos/audio/stuff? You mean themes? Well, i don't know about that. I think it could be. I had in mind executables.
an added feature, could be, that the installation privileges could expire after say 15 minutes. This way a user that tests lots of stuff, doesn't need to pass the password every single time.
an other one, could be that automatic updates are allowed only for explicitly allowed sites. The white list would be subject to the password.
You see, flexible stuff.
In general, i'm thinking of something easy to use by simple users, and flexible too. The current no password required installation should remain as an option also. The user takes responsibility for his own actions.
I meant, to force them to choose between a password or no password. During installation i guess.
Not force them to use a password.
pictures/videos/audio/stuff? You mean themes? Well, i don't know about that. I think it could be. I had in mind executables.
an added feature, could be, that the installation privileges could expire after say 15 minutes. This way a user that tests lots of stuff, doesn't need to pass the password every single time.
an other one, could be that automatic updates are allowed only for explicitly allowed sites. The white list would be subject to the password.
You see, flexible stuff.
In general, i'm thinking of something easy to use by simple users, and flexible too. The current no password required installation should remain as an option also. The user takes responsibility for his own actions.
-
ketmar
- Lunatic
- Posts: 369
- Joined: 2015-07-28, 11:10
- Location: Earth
Re: Password for installing extentions
there is already an option which is easy for "simple users": prompt window with time-locked "install" button. if user doesn't want to pay attention to that window, no passwords will help.