102 | | By default Web-GRASS is designed to allow access to trusted users. |
103 | | Each user will be an UNIX user on the server with his own home. |
104 | | The web-grass UI interface will be accessible through an opportune registration/auth/login framework. |
105 | | The communication over the network will be encrypted using HTTPS. |
106 | | The imput parameters will be parsed and sanitized, this will be part of the UI itself, based on the [http://grass.osgeo.org/programming7/gislib_cmdline_parsing.html GRASS command-line parsing] |
| 102 | By default Web-GRASS is designed to allow access to trusted users. [[BR]] |
| 103 | Each user will be an UNIX user on the server with his own home. [[BR]] |
| 104 | The web-grass UI interface will be accessible through an opportune registration/auth/login framework.[[BR]] |
| 105 | The communication over the network will be encrypted using HTTPS.[[BR]] |
| 106 | The imput parameters will be parsed and sanitized, this will be part of the UI itself, based on the [http://grass.osgeo.org/programming7/gislib_cmdline_parsing.html GRASS command-line parsing] [[BR]] |