<div>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.</div><div><br></div>
<div>giovanni</div><div><br><div class="gmail_quote">2011/9/16 Martin Dobias <span dir="ltr"><<a href="mailto:wonder.sk@gmail.com">wonder.sk@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Fri, Sep 16, 2011 at 2:53 AM, John Patterson <<a href="mailto:john@henrygis.com">john@henrygis.com</a>> wrote:<br>
> I'd say that encryption is the answer here - hang the security on the key<br>
> rather than the code. If the requirement is explicitly "should be only<br>
> visible and usable through the customized qgis and not by any other tool.",<br>
> then use GPG[1] or something[2] and add a "File > Load Encrypted Dataset"<br>
> dialog or some such. I would imagine this to be a reasonable solution.<br>
<br>
</div>Even when the data is encrypted on disk, they are freely accessible<br>
within QGIS. The user has many opportunities how to access raw data:<br>
- save the layer to another format<br>
- copy all features to another layer<br>
- save the data in python console<br>
- save the data in a plugin<br>
<font color="#888888"><br>
Martin<br>
</font></blockquote></div><br></div>