On Fri, 3 Dec 2004, Erik Anderson wrote:
On Thu, 2 Dec 2004, James Yonan wrote:
How about a ./configure option such as --disable-password-save (and
corresponding #define flag for Windows build in config-win32.h)?
This flag would then disable the optional file argument to --askpass and
That could be a solution -- if we reverse it! Make the option disabled by
default, so you have to use --enable-password-save on ./configure to get
this feature. This would mean thay binary distributions, and typical builds
by normal users will lack this feature.
Those few people who need to setup an un-attended system with a passphrase
protected key can go through the trouble of building their own openvpn
binary from source.
This will make it alot harder for normal users to circumvent security.
Another way of dealing with it is like we discussed to do it with the GUI,
by having a PUSHable option that would cause the openvpn client to abort
the connection if the passphrase had been read from a file. The very same
option could then also be used by a GUI to control whether to allow a user
to save the passphrase or not.
Umm, what would prevent someone from saying --enable-password-save --askpass
on the command line? At least a disable-password-save cannot be overridden
once it's been said somewhere...
The --enable-password-save option I proposed was of cource a ./configure
option controlling the build, not a cmd-line option to the openvpn binary.
If built without password-save support, --askpass wouldn't work as
If using a pushable option, that should of cource not be accepted as a
cmd-line option on the client overriding the pushed option.
Mathias Sundman (^) ASCII Ribbon Campaign
OpenVPN GUI for Windows X NO HTML/RTF in e-mail
http://www.nilings.se/openvpn / \ NO Word docs in e-mail
Openvpn-users mailing list