It is no about implementation but the concept itself. As soon as there
will be an easy way how to provide GRASS GIS processing as a service,
somebody will run it without understanding all security ramifications
of allowing any input into GRASS. Securing GRASS code would be nice,
but so far we are s
2017-05-25 10:24 GMT+02:00 Blumentrath, Stefan :
> Seen this: https://bitbucket.org/huhabla/open-graas?
Sorry, that shouldn't be public available. Please ignore this implementation.
Cheers
Sören
> Cheers
> Stefan
>
> Von: grass-dev [grass-dev-boun...@list
Seen this: https://bitbucket.org/huhabla/open-graas?
Cheers
Stefan
Von: grass-dev [grass-dev-boun...@lists.osgeo.org] im Auftrag von Maris Nartiss
[maris@gmail.com]
Gesendet: Donnerstag, 25. Mai 2017 09:42
An: Pietro
Cc: GRASS developers list
Betreff:
On Thu, May 25, 2017 at 1:15 AM, Markus Neteler wrote:
> IMHO "Fig. 1: GRASS GIS 7 location structure" in
> https://grass.osgeo.org/grass72/manuals/help_loc_struct.png
> https://grass.osgeo.org/grass72/manuals/helptext.html
>
> (master: doc/help_loc_structure.odg)
>
> often confuses users while
>
Paul Schrum wrote
> Going by
> https://grasswiki.osgeo.org/wiki/Compile_and_Install_Ubuntu#GRASS_GIS and
> focusing on GRASS GIS 7 trunk:
>
> 1. Last week I did
>
> svn co https://svn.osgeo.org/grass/grass/trunk grass7_trunk
>
> On a directory under my ownership.
>
> 2. Today in that same dire
I assume that both are equally dangerous. My opinion is that GRASS GIS
should not be exposed to any non trustable users, as various smaller
and larger bugs are too common. Unless, of course, it runs inside a
throw-away VM.
2017-05-25 10:33 GMT+03:00 Pietro :
> Dear Māris,
>
> On Wed, May 24, 2017
Dear Māris,
On Wed, May 24, 2017 at 8:52 PM, Maris Nartiss wrote:
> GRASS GIS code has never been developed with security in mind. I would
> not suggest to run it in a non-trustable environment.
>
Do you think that expose some GRASS modules through a REST API can be more
dangerous than exposing
Hi Moritz,
On Wed, May 24, 2017 at 3:31 PM, Moritz Lennert <
mlenn...@club.worldonline.be> wrote:
> - first of all: is build a REST API for GRASS a stupid idea? should we
>> use/promote just the WPS?
>>
>
>
> Well, what is your argument agains WPS ? Why do you think a REST API is
> necessary / us
