[GRASS-dev] Implement a REST API for GRASS

Sören Gebbert soerengebbert at googlemail.com
Thu May 25 14:18:07 PDT 2017


2017-05-25 10:24 GMT+02:00 Blumentrath, Stefan <Stefan.Blumentrath at nina.no>:
> 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-bounces at lists.osgeo.org] im Auftrag von Maris Nartiss [maris.gis at gmail.com]
> Gesendet: Donnerstag, 25. Mai 2017 09:42
> An: Pietro
> Cc: GRASS developers list
> Betreff: Re: [GRASS-dev] Implement a REST API for GRASS
>
> 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 <peter.zamb at gmail.com>:
>> Dear Māris,
>>
>> On Wed, May 24, 2017 at 8:52 PM, Maris Nartiss <maris.gis at gmail.com> 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 the same modules through a WPS service? Why?
>>
>> Pietro
> _______________________________________________
> grass-dev mailing list
> grass-dev at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
> _______________________________________________
> grass-dev mailing list
> grass-dev at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev


More information about the grass-dev mailing list