summaryrefslogtreecommitdiff
path: root/lib/stdlib/test/shell_docs_SUITE_data/unknown_erlang_binary_to_term_2_func.txt
diff options
context:
space:
mode:
Diffstat (limited to 'lib/stdlib/test/shell_docs_SUITE_data/unknown_erlang_binary_to_term_2_func.txt')
-rw-r--r--lib/stdlib/test/shell_docs_SUITE_data/unknown_erlang_binary_to_term_2_func.txt10
1 files changed, 9 insertions, 1 deletions
diff --git a/lib/stdlib/test/shell_docs_SUITE_data/unknown_erlang_binary_to_term_2_func.txt b/lib/stdlib/test/shell_docs_SUITE_data/unknown_erlang_binary_to_term_2_func.txt
index 026b8d18cb..60e6109348 100644
--- a/lib/stdlib/test/shell_docs_SUITE_data/unknown_erlang_binary_to_term_2_func.txt
+++ b/lib/stdlib/test/shell_docs_SUITE_data/unknown_erlang_binary_to_term_2_func.txt
@@ -16,7 +16,7 @@
source.
When enabled, it prevents decoding data that can be used to
- attack the Erlang system. In the event of receiving unsafe
+ attack the Erlang runtime. In the event of receiving unsafe
data, decoding fails with a badarg error.
This prevents creation of new atoms directly, creation of new
@@ -33,6 +33,14 @@
> binary_to_term(<<131,100,0,5,"hello">>, [safe]).
hello
+ Warning:
+ The safe option ensures the data is safely processed by
+ the Erlang runtime but it does not guarantee the data is
+ safe to your application. You must always validate data
+ from untrusted sources. If the binary is stored or
+ transits through untrusted sources, you should also
+ consider cryptographically signing it.
+
used:
Changes the return value to {Term, Used} where Used is the
number of bytes actually read from Binary.