Thanks for the brainstorming. I will bring the various usefull considerations to my collegues. I'll let you know about the policies that will be chosen, and consequently the road to achieve them.
giovanni 2011/9/16 Martin Dobias <wonder...@gmail.com> > On Fri, Sep 16, 2011 at 2:53 AM, John Patterson <j...@henrygis.com> wrote: > > I'd say that encryption is the answer here - hang the security on the key > > rather than the code. If the requirement is explicitly "should be only > > visible and usable through the customized qgis and not by any other > tool.", > > then use GPG[1] or something[2] and add a "File > Load Encrypted Dataset" > > dialog or some such. I would imagine this to be a reasonable solution. > > Even when the data is encrypted on disk, they are freely accessible > within QGIS. The user has many opportunities how to access raw data: > - save the layer to another format > - copy all features to another layer > - save the data in python console > - save the data in a plugin > > Martin >
_______________________________________________ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
