Re: [GRASS-dev] Implement a REST API for GRASS

2017-05-26 Thread Sören Gebbert
ag von Maris >> Nartiss [maris@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

Re: [GRASS-dev] Implement a REST API for GRASS

2017-05-25 Thread Maris Nartiss
opers 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

Re: [GRASS-dev] Implement a REST API for GRASS

2017-05-25 Thread Sören Gebbert
-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: Re: [GRASS-dev] Implement a REST API for GRASS > > I assume that both are equally dangerous. My

Re: [GRASS-dev] Implement a REST API for GRASS

2017-05-25 Thread Blumentrath, Stefan
: 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

Re: [GRASS-dev] Implement a REST API for GRASS

2017-05-25 Thread Maris Nartiss
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

Re: [GRASS-dev] Implement a REST API for GRASS

2017-05-25 Thread Pietro
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

Re: [GRASS-dev] Implement a REST API for GRASS

2017-05-25 Thread Pietro
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

Re: [GRASS-dev] Implement a REST API for GRASS

2017-05-24 Thread Maris Nartiss
2017-05-24 14:18 GMT+03:00 Pietro : > Dear devs, > > Any ideas that you want to share? > GRASS GIS code has never been developed with security in mind. I would not suggest to run it in a non-trustable environment. Māris. > Best regards > > Pietro ___ gr

Re: [GRASS-dev] Implement a REST API for GRASS

2017-05-24 Thread Moritz Lennert
On 24/05/17 13:18, Pietro wrote: Dear devs, In the last days I've started thinking to a REST API for GRASS. I think would be nice to offer some of the GRASS functionalities through a web service. I would like to detailed the whole

[GRASS-dev] Implement a REST API for GRASS

2017-05-24 Thread Pietro
Dear devs, In the last days I've started thinking to a REST API for GRASS. I think would be nice to offer some of the GRASS functionalities through a web service. I would like to detailed the whole REST API using the YAML