1 This directory contains some files useful for ad-hoc tests.
2 With these it is possible to run a test of secnet on a Linux host
3 even if that Linux host does not have another working network connection.
5 The keys here are (obviously) public. They were generated like this:
6 ssh-keygen -C inside@example.com -f test-example/inside.key -t rsa1 -b 1024
7 ssh-keygen -C outside@example.com -f test-example/outside.key -t rsa1 -b 1024
8 # edit sites to paste {inside,outside}.key.pub into pubkey lines
9 base64 <inside.key >inside.key.b64
10 base64 <outside.key >outside.key.b64
15 In one window, as root
16 ./secnet -dvnc test-example/inside.conf
18 ./secnet -dvnc test-example/outside.conf
20 ping -I secnet-test-i 172.18.232.2
22 For running under valgrind memcheck, do something like this:
23 valgrind --num-callers=40 --gen-suppressions=yes --db-attach=yes \
24 --leak-check=full --suppressions=test-example/memcheck.suppressions \
25 ./secnet -dvnc test-example/outside.conf
26 NB that --num-callers is needed as secnet's stack can be deep.
28 The config file outside-unshare.conf can be used on Linux in
29 conjunction with test-example/fake-userv and a built checkout of
30 userv-utils.git to run the "outside" copy of secnet in a new "network
35 Everything in this directory is part of secnet. See README (in the
36 directory above) for full list of copyright holders.
38 secnet is free software; you can redistribute it and/or modify it
39 under the terms of the GNU General Public License as published by
40 the Free Software Foundation; either version 3 of the License, or
41 (at your option) any later version.
43 secnet is distributed in the hope that it will be useful, but
44 WITHOUT ANY WARRANTY; without even the implied warranty of
45 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
46 General Public License for more details.
48 You should have received a copy of the GNU General Public License
49 version 3 along with secnet; if not, see
50 https://www.gnu.org/licenses/gpl.html.