Difference between revisions of "OpenVPN/Documentation for testers"

From Secure Computing Wiki
Jump to: navigation, search
m (Debugging)
Line 44: Line 44:
 
= Debugging =
 
= Debugging =
  
If OpenVPN crashes on you, can help developers figure out the problem by giving them a backtrace of the crash. If you're running released (stable) version of OpenVPN, you should install the ''openvpn debug'' and ''gdb'' packages and then run openvpn via gdb. On "testing" turn on debugging before compilation. In either case you can get a backtrace of the crash like this:
+
If OpenVPN crashes, you can help developers figure out the problem by giving them a backtrace of the crash. If you're running released (stable) version of OpenVPN, you should install the ''openvpn debug'' and ''gdb'' packages and then run openvpn via gdb. On "testing" turn on debugging before compilation. In either case you can get a backtrace of the crash like this:
  
 
  gdb /usr/sbin/openvpn
 
  gdb /usr/sbin/openvpn

Revision as of 11:57, 25 February 2010

Instructions for testers wanting to test

Building OpenVPN testing from git

Fetching the sources

  • If you have not cloned the git repository:
git clone git://openvpn.git.sourceforge.net/gitroot/openvpn/openvpn-testing.git
cd openvpn-testing
git checkout -b allmerged origin/allmerged
  • If you already have git repository clone:
cd openvpn-testing
git checkout allmerged
git pull --rebase origin
  • Prepare for building:
autoreconf -vi

Building OpenVPN testing from snapshots

  • Unpack it
gzip -dc openvpn-YYYYWW.tar.gz | tar xvf -
cd openvpn-devel/

Configure and compile

When testing this version of OpenVPN, we would appreciate if all deprecated features would be disabled by default. We want to know how OpenVPN behaves for you without these features.

When doing the compile-time configuration of OpenVPN, please make sure the following arguments are included:

  • --disable-depr-random-resolv

Example:

./configure --disable-depr-random-resolv
make [-j <num CPU cores + 1>]

When testing this version, please give us a report to **TBD**. This report should also include the output of:

openvpn --version

in addition to the ./configure line use used for the compilation and all the configuration files you used. We would like to have both success and fail reports.

Debugging

If OpenVPN crashes, you can help developers figure out the problem by giving them a backtrace of the crash. If you're running released (stable) version of OpenVPN, you should install the openvpn debug and gdb packages and then run openvpn via gdb. On "testing" turn on debugging before compilation. In either case you can get a backtrace of the crash like this:

gdb /usr/sbin/openvpn
[gdb info message...blablabla...]
(gdb) run --config <your config file> [--other-arguments-you-might-pass]
[wait for the crash]
(gdb) bt
[full backtrace should appear]