From c7917b3c44c56021b71b75c52617b9701bd13387 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Richard=20K=C3=B6rber?= Date: Sun, 14 Jan 2018 14:19:42 +0100 Subject: [PATCH] Add note about usage of serialized resources --- src/site/markdown/usage/session.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/site/markdown/usage/session.md b/src/site/markdown/usage/session.md index a1cb6f4c..0a6ada91 100644 --- a/src/site/markdown/usage/session.md +++ b/src/site/markdown/usage/session.md @@ -45,3 +45,5 @@ All resource objects are serializable, so the current state of the object can be However the `Session` the object is bound with is _not_ serialized! This is because the `Session` object contains a copy of your private key. Not serializing it prevents that you unintentionally reveal your private key in a place with lowered access restrictions. This means that a deserialized object is not bound to a `Session` yet. It is required to rebind it to a `Session`, by invoking its `rebind()` method. + +Serialization is only meant for short term storage at runtime, not for long term persistence. Do not share serialized data between different versions of _acme4j_.