From 2600680ec2fd3cc27d7222154a637995fd90330f Mon Sep 17 00:00:00 2001 From: Gert Doering Date: Sat, 11 Jan 2014 12:50:36 +0100 Subject: [PATCH] Document issue with --chroot, /dev/urandom and PolarSSL. See trac#218 Signed-off-by: Gert Doering Acked-by: Steffan Karger Message-Id: <1389441036-12538-1-git-send-email-gert@greenie.muc.de> URL: http://article.gmane.org/gmane.network.openvpn.devel/8213 (cherry picked from commit b238a1f2d4b2cdcfc844689b33fd3ac43ed31c1c) --- doc/openvpn.8 | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/doc/openvpn.8 b/doc/openvpn.8 index 17ea2205a..e7cff7713 100644 --- a/doc/openvpn.8 +++ b/doc/openvpn.8 @@ -2082,6 +2082,16 @@ 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, +.B \-\-chroot +will only work if a /dev/urandom device node is available +inside the chroot directory +.B dir. +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 -- 2.47.2