[Freegis-list] Re: Encrpting Shapefiles

[Frank Warmerdam]

Bernhard Reiter wrote:
> On Fri, Aug 27, 2004 at 06:34:04AM +0800, Dan Jacobson wrote:
> 
>>Satyajit> I want to encrypt the shapefiles so that the set of data can be seen only through
>>Satyajit> my application.
>>
>>Sounds like a direction opposite from the goals of this list.
> 
> 
> Why? :)
> I mean if you have private geodata (like the locations 
> of your relatives) I would perferably encrypt it 
> and of course I would use Free Software to do it. 

Bernhard,

Encryption for privacy purposes is not anti-freedom, but it sounds like
the fellow was talking about locking data so it was only accessable through
his application.  Presumably this is, in essence, an attempt to limit the
users access to data with further policy enforced by the application.

This is a model I have seen from a number of companies (and governments!)
and is I think usually quite opposite from the desire for various freedoms
with software and data.

I was reading the following essay by a fellow from Sun today (linked also from
Slashdot):

   http://www.sys-con.com/java/46131.cfm

One of the things I thought was interesting in this was the concept that
there were freedoms important to users as opposed to developers:

Simon Phipps says:
   What freedoms do deployers need? They're actually rather traditional:
     * Function that meets actual business needs
     * Freedom to change supplier, so that prices can always be negotiated
     * Freedom to choose new software solutions as business needs evolve
     * Control of the data, by implication control of the format it's stored in
     * Protection from liabilities associated with the development of the software

I find the first "freedom" quite dubious. The freedom to magically have whatever
I want or need just appear for me?   But I thought that the following freedoms
are meaningful from a user/deployer point of view and describe kind sof openness
organizations need to keep in when selecting solutions.

The earlier question about encrypting data would appear to be an effort to
interfere with the "control of the data" freedom.  But I think the freedom
to change supplier is a fundamental one to the free software movement.  To
not be locked into any vendor due to IP or other constraints.  The freedom
to choos new software solutions basically comes down to ensuring that
various kinds of lock-in are avoided ... standards can play an important
role in this.

Anyways, I guess my overall point is that beyond the core freedoms esposed
by the free software movement there are a variety of other things that
users (and concerned software developers) should be considering to ensure
that users of all kinds can maneuver as they need to.

Enough rambling for today.

Best regards,
-- 
---------------------------------------+--------------------------------------
I set the clouds in motion - turn up   | Frank Warmerdam, warmerdam at pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush    | Geospatial Programmer for Rent