| Age | Commit message (Collapse) | Author |
|---|
|
+ The restrictions on arbitrary IO when GF is running in restricted mode is now
enforced in the types.
+ This hopefully also solves an intermittent problem when accessing the GF
shell through the web API provided by gf -server. This was visible in the
Simple Translation Tool and probably caused by some low-level bug in the
GHC IO libraries.
|
|
The dependency on PGFEnv has been moved from the list to the exec function of
the commands in the list. This means that the help command no longer needs
to generate a new list of commands and that the state of the shell
(type GF.Command.Interpreter.CommandEnv) no longer needs to contain the list
of commands.
|
|
syntax
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
old concretes if they are for the old abstract; the new priority is implemented in PGF.Data.unionPGF
|
|
|
|
|
|
|
|
|
|
in TreeOperations; using PGF.Expr.match would be better); example given in 'h pt'
|
|
|
|
By setting the environment variable GF_RESTRICTED before starting GF, the shell
will be run in restricted mode. This will prevent the GF shell from starting
arbitrary system commands (most uses of System.Cmd.system are blocked) and
writing arbitrary files (most commands that use writeFile et al are blocked).
Restricted mode is intended minimize the potential security risks involved
in allowing public access to the GF shell over the internet. It should be used
in conjuction with system level protection mechanisms (e.g. file permissions)
to make sure that a publicly acessible GF shell does not give access to parts
of the system that should not be publicly accessible.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
;-separated words
|
|
|
|
|
|
|
|
graphviz and giza alignments
|
|
command in the shell
|
|
|
|
in the abstract syntax
|
|
Still not quite stable.
|
|
|
|
parse forest
|
|
|
|
|
|
|
