Document issue with --chroot, /dev/urandom and PolarSSL.
PATCH 1/1 Document issue with --chroot, /dev/urandom and PolarSSL.
See trac#218
Signed-off-by Gert Doering <[email protected]...>
--- doc/openvpn.8 | 7 +++++++ 1 file changed, 7 insertions(+)
doc/openvpn.8 +7 -0
@@ -2097,6 +2097,13 @@ In many cases, the parameter can point to an empty directory, however complications can result when scripts or restarts are executed after the chroot operation. + +Note: if OpenVPN is built using the PolarSSL SSL +library, it will only work if a /dev/urandom device +node is available inside the chroot directory. This +is due to the way PolarSSL works (it wants to open +/dev/urandom every time randomness is needed, not just +once at startup) and nothing OpenVPN can influence. .\"********************************************************* .TP .B \-\-setcon context
Signature · 1 line
1.8.3.2
Quoted 15 lines · Gert Doering
See trac#218
Signed-off-by Gert Doering <[email protected]...>--- doc/openvpn.8 | 7 +++++++ 1 file changed, 7 insertions(+)doc/openvpn.8 +0
-0@@ -2097,6 +2097,13 @@ In many cases, the parameter can point to an empty directory, however complications can result when scripts or restarts are executed after the chroot operation.
doc/openvpn.8 In many cases, the · line 2109
Quoted 10 lines
doc/openvpn.8 +7
-0+ +Note: if OpenVPN is built using the PolarSSL SSL +library, it will only work if a /dev/urandom device +node is available inside the chroot directory. This +is due to the way PolarSSL works (it wants to open +/dev/urandom every time randomness is needed, not just +once at startup) and nothing OpenVPN can influence. .\"********************************************************* .TP .B \-\-setcon context
ACK.
Just a tiny nit-pick, "PolarSSL SSL library", isn't it better to say "PolarSSL library"?
Signature · 3 lines
kind regards, David Sommerseth