Hi, if the plugins are considered a security risk (no matter by whom and no matter if this is justified or not) then probably you should block access to all urls holding plugins on the network level. Your proposed approach is "security by obscurity" IMHO. A more bureaucratic approach would be to have the users sign something that they agree not to download any plugins if not explicitly authorized by <someperson>.
my 2 cents Bernhard > Rummer, Patrick (SGD Süd) via QGIS-User <qgis-user@lists.osgeo.org> hat am > 23.03.2023 09:06 CET geschrieben: > > > Hello Richard, > > thank you very much for your answer. I meant plugins, not "extensions", sry. > > Also, i found a way to simply disable the whole plugin menu within the " > QGISCUSTOMIZATION3.ini". > That's the easiest way and none of our users will find it, since it's under > %appdata%. > > Also, i'm not the one who wants to block the plugins ;) but unfortunately i > have to. > > Kind regards, > > Patrick > > > -----Ursprüngliche Nachricht----- > Von: Richard Duivenvoorde <rdmaili...@duif.net> > Gesendet: Donnerstag, 23. März 2023 09:00 > An: Rummer, Patrick (SGD Süd) <patrick.rum...@sgdsued.rlp.de>; > qgis-user@lists.osgeo.org > Betreff: [EXTERN] Re: [Qgis-user] Restrict User's access to extensions > > > Pff, best to use paper maps and a calculator then ;-) > > But seriously: disabling selective extensions (I think you mean the python > 'plugins') is hard and totally remove python makes QGIS a lot less > productive/usable. > > Not sure if you can remove the default qgis plugins repo (or make it > unreachable for your users), but if(!) so, you could try to remove that url, > and create your own repo which ONLY holds plugins you allow (but then you are > responsible to periodically update them). And off course a user can always > download the plugin from plugins.qgis.org as zip and install it (or even copy > it from another computer). > > Or do you mean other extensions? > > Regards, > > Richard Duivenvoorde > > > > On 3/22/23 14:00, Rummer, Patrick (SGD Süd) via QGIS-User wrote: > > Hello there, > > > > i don’t know if this ist he right list, so pardon me if not. > > > > I have the unpleasant task to deploy QGIS to all of our users via matrix42 > > which is a problem in itself. > > > > Anyways, the question of our - let’s call him „CSO“ – is if we can restrict > > the access to extensions. > > > > I know that you can disable it from within the program but anyone could > > simply reactivate it or use zip-files or whatever. > > > > Is it possible to restrict that somehow? > > > > Kind regards, > > > > Patrick > > > > > > _______________________________________________ > > QGIS-User mailing list > > QGIS-User@lists.osgeo.org > > List info: https://lists.osgeo.org/mailman/listinfo/qgis-user > > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user > > _______________________________________________ > QGIS-User mailing list > QGIS-User@lists.osgeo.org > List info: https://lists.osgeo.org/mailman/listinfo/qgis-user > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user _______________________________________________ QGIS-User mailing list QGIS-User@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
