This commit is contained in:
Hannes Mehnert 2016-04-10 13:03:36 +01:00
parent c51700226a
commit e280c416b6

View file

@ -148,7 +148,7 @@ does not need to care about memory management and bounds checks, immediately rem
several classes of security problems (namely spatial and temporal memory several classes of security problems (namely spatial and temporal memory
issues), once the runtime is trusted. issues), once the runtime is trusted.
The OCaml runtime was reviewed by the French [Agence nationale de la sécurité des systèmes dinformation](http://www.ssi.gouv.fr/agence/publication/lafosec-securite-et-langages-fonctionnels/) in 2013, The OCaml runtime was reviewed by the French [Agence nationale de la sécurité des systèmes dinformation](http://www.ssi.gouv.fr/agence/publication/lafosec-securite-et-langages-fonctionnels/) in 2013,
leading to some changes, such as separation of immutable strings (`String`) and mutable byte vectors (`Bytes`). leading to some changes, such as separation of immutable strings (`String`) from mutable byte vectors (`Bytes`).
The attack surface is still big enough: logical issues, resource management, and there is no access The attack surface is still big enough: logical issues, resource management, and there is no access
control. This is fine for this website, publishing of content is "protected" by GitHub's control. This is fine for this website, publishing of content is "protected" by GitHub's