On Thu, Sep 15, 2011 at 08:53:50PM -0400, John Patterson wrote:
I'd say that encryption is the answer here - hang the security on the key
rather than the code.
I think that this is not the case depicted by Giovanni; if I
understand well he wants to prevent the letitimate user (which
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.,
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
On Thu, Sep 15, 2011 at 8:56 PM, Marco Hugentobler
marco.hugentob...@sourcepole.ch wrote:
Hi Giovanni
The simplest solution might be to encrypt the data and send the key to your
clients.
Simplest, but if you send the key in plaintext then you might as well
send the data in plaintext -
On Thu, Sep 15, 2011 at 11:14 AM, G. Allegri gioha...@gmail.com wrote:
I've been asked to create a custom qgis, to be distributed via CD/DVD along
with some data (vector and raster) that should be only visible and usable
thorugh the customized qgis and not by any other tool.
Has somebody in
That's a great point - I was envisioning a scenario in which end users are
to be (mostly) trusted not to take efforts to re-distribute the data.
John
On Fri, Sep 16, 2011 at 2:42 AM, Niccolo Rigacci nicc...@rigacci.orgwrote:
On Thu, Sep 15, 2011 at 08:53:50PM -0400, John Patterson wrote:
Hi All,
Last night I thought it might be cool to try and implement auto saving for
layers that are in edit mode in QGIS. There was a request [1] opened up a
while ago and while a plugin could have been made to fill the hole I think
that this kind of stuff is nice to have built in.
So I had a go
