On Tue, 1 Apr 2014 08:53:38 -0700 (PDT), Melanie Riley wrote:
> export "SPATIALITE_SECURITY=relaxed"
>
> So I did --within the Spatialite GUI, at the spatialite command
> prompt
> window....with no luck. It does not acknowledge
> "export" as any proper syntax. Where can I change this setting?
>
Hi Melanie,
sorry, but the above syntax is merely intended for "sane minded"
systems supporting POSIX standards: e.g. Unix, Linux, MacOsX,
Android, FreeBSD, NetBSD (and many, many others)
if you are using instead some different operating system you'll
be probably required to consult the appropriate platform
documentation supporting your specific o.s./version.
You've missed to specify which platform you are currently using:
anyway my educated guess is that the following references could
eventually help you:
http://technet.microsoft.com/en-us/library/bb490998.aspx
http://en.wikipedia.org/wiki/Environment_variable
> Is there an ok way to populate the style column with this other
> column
> without causing any potential issues?
>
sorry again, but the problem is substantially different.
A) any SQL function allowing to directly exchange an external file
from / to the DB and the local file-system could eventually imply
a serious security risk.
a malicious SQL script (or even more dangerous: a forged trigger)
could easily exploit such a vulnerability so to install a virus
or a trojan. or alternatively the same mechanism could be
successfully deployed so to steal reserved and sensible data.
B) anyway directly importing / exporting external files from
the DB and the local file-system is a very useful option
in many different cases: e.g. this exactly is the case of
XB_LoadXML and XB_StoreXML
in other worlds: if you explicitly invoke these functions
for any good reason this doesn't implies any possible
security risk.
but leaving function like these intentionally available
without any restriction could eventually open seriously
dangerous security pitfalls.
C) accordingly to all this, any SQL function posing even vaguely
potential security issues will always be kept disabled.
unless the user gives an explicit "informed consent" thus
allowing to temporarily relax the standard security rules.
using an external environment variable is the most simple
way to implement all this.
environment variables are rather easy to be handled, are
universally supported on any possible platform I know, and
are definitely well out-of-reach of any possible malicious
attack strategy.
bye Sandro