<!-- Translators: put here the copyright notice of the translation -->
<!-- Put here the FDL notice.Read the explanation in fdl-notice.docbook
and in the FDL itself on how to use it. -->
<legalnotice>&FDLNotice;</legalnotice>
<!-- Date and version information of the documentation
Don't forget to include this last date and this last revision number, we
need them for translation coordination !
Please respect the format of the date (YYYY-MM-DD) and of the version
(V.MM.LL), it could be used by automation scripts.
Do NOT change these in the translation. -->
<date>2005-07-22</date>
<releaseinfo>0.3</releaseinfo>
<!-- Abstract about this handbook -->
<abstract>
<para>
&kvpnc; is a KDE frontend for various vpn clients.
</para>
</abstract>
<!-- This is a set of Keywords for indexing by search engines.
Please at least include KDE, the KDE package it is in, the name
of your application, and a few relevant keywords. -->
<keywordset>
<keyword>KDE</keyword>
<keyword>kvpnc</keyword>
<keyword>VPN</keyword>
<keyword>vpnc</keyword>
<keyword>freeswan</keyword>
<keyword>racoon</keyword>
<keyword>IPSec</keyword>
<keyword>IPsec</keyword>
<keyword>Cisco</keyword>
<keyword>OpenVPN</keyword>
<keyword>PPTP</keyword>
</keywordset>
</bookinfo>
<!-- The contents of the documentation begin here.Label
each chapter so with the id attribute. This is necessary for two reasons: it
allows you to easily reference the chapter from other chapters of your
document, and if there is no ID, the name of the generated HTML files will vary
from time to time making it hard to manage for maintainers and for the CVS
system. Any chapter labelled (OPTIONAL) may be left out at the author's
discretion. Other chapters should not be left out in order to maintain a
consistent documentation style across all KDE apps. -->
<chapter id="introduction">
<title>Introduction</title>
<!-- The introduction chapter contains a brief introduction for the
application that explains what it does and where to report
problems. Basically a long version of the abstract.Don't include a
revision history. (see installation appendix comment) -->
<para>
KVpnc is a <ulink url="http://www.kde.org/">KDE</ulink> frontend for various vpn clients. It supports Cisco VPN (<ulink url="http://www.unix-ag.uni-kl.de/~massar/vpnc/">vpnc</ulink>), IPSec (<ulink url="http://www.freeswan.org">FreeS/WAN</ulink> (OpenS/WAN), <ulink url="http://ipsec-tools.sourceforge.net/">racoon</ulink>), PPTP (<ulink url="http://sourceforge.net/projects/pptpclient/">pptpclient</ulink>), <ulink url="http://www.openvpn.net">OpenVPN</ulink>, L2TP (FreeS/WAN, <ulink url="http://www.openswan.org/">Openswan</ulink>, <ulink url="http://www.strongswan.org/" >strongSwan</ulink>, <ulink url="http://ipsec-tools.sourceforge.net/">ipsec-tools</ulink>), <ulink url="http://vtun.sourceforge.net/">Vtun</ulink> and <ulink url="http://www.openssh.net/">OpenSSH</ulink>.
</para>
</chapter>
<chapter id="getting-help">
<title>Getting help</title>
<itemizedlist>
<listitem>
<para>General</para>
<para>The project page can be found at: <ulink url="https://www.gna.org/projects/kvpnc/">https://www.gna.org/projects/kvpnc</ulink>.</para>
</listitem>
<listitem>
<para>Contact the kvpnc team:</para>
<itemizedlist>
<listitem>
<para>Bug report - To report bugs or wishes use the bugtracker page at: <ulink url="https://gna.org/bugs/?group=kvpnc">https://gna.org/bugs/?group=kvpnc</ulink></para>
</listitem>
<listitem>
<para>A list of planned features (TODO list) can be found here: <ulink url="http://cvs.gna.org/viewcvs/*checkout*/kvpnc/kvpnc/TODO?rev=HEAD&content-type=text/plain">http://cvs.gna.org/viewcvs/*checkout*/kvpnc/kvpnc/TODO?rev=HEAD&content-type=text/plain</ulink> (in English).
</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>Mailing list</para>
<itemizedlist>
<listitem>
<para>kvpnc-user - this list is for users of KVpnc who want to discuss about KVpnc.</para>
</listitem>
<listitem>
<para>kvpnc-devel - this list is related to development of KVpnc.</para>
</listitem>
<listitem>
<para>kvpnc-cvs - this list shows the commit to the CVS tree (readonly).</para>
</listitem>
</itemizedlist>
</listitem>
</itemizedlist>
</listitem>
</itemizedlist>
</chapter>
<chapter id="using-kvpnc">
<title>Using &kvpnc;</title>
<!-- This chapter should tell the user how to use your app. You should use as
many sections (Chapter, Sect1, Sect3, etc...) as is necessary to fully document
your application. -->
<para>
<!-- Note that all graphics should be in .png format. Use no gifs because of
<para>A connection to a cisco concentrator will be often found at universities. The students can fetch the cisco client for use with it. Normally the administrator provides a configuration file (*.pcf), which also can be included in the client.</para>
<para>The original cisco client has some problems:
<itemizedlist>
<listitem><para>Needs a propriarity kernel module (can be build against own kernel)</para></listitem>
<listitem><para>console only</para></listitem>
</itemizedlist>
</para>
<note>
<para>
You need: Username, password, VPN ID, IP address or hostname of the VPN gateway and preshared secret (PSK) if you dont have a cisco profile file (*.pcf).
</para>
</note>
<para>To setup a connection to the Cisco concentrator you need to do the following steps:
<orderedlist>
<listitem><para>Import the pcf file given from administrator (if available go to step 4)</para></listitem>
<listitem><para>Create a new profile with type cisco</para></listitem>
<listitem><para>Set gateway (hostname or IP address of the cisco concentrator) at general profile settings</para></listitem>
<listitem><para>Set at PSK profile settings (Pre shared key) the group password if you want to store it</para></listitem>
<listitem><para>Set at user settings the user name and password (if you want to store it)</para></listitem>
</orderedlist>
</para>
</sect1>
<sect1 id="Howto-IPSec">
<title>IPSec</title>
<para>
...
</para>
</sect1>
<sect1 id="Howto-OpenVPN">
<title>OpenVPN</title>
<para>
...
</para>
</sect1>
<sect1 id="Howto-PPTP">
<title>PPTP</title>
<para>
PPTP is a old VPN protocol designed by Microsoft. Today its known to be insecure. Reasons are unencrypted control channel and design mistakes.
</para>
</sect1>
</chapter>
<chapter id="kvpnc-features">
<title>&kvpnc; features</title>
<!-- <para> -->
<!-- <sect1> -->
<para>KVpnc provides a lot of features:</para>
<itemizedlist>
<listitem><para>Easy to use KDE gui</para></listitem>
<listitem><para>Docking in kicker</para></listitem>
<listitem><para>Can be used to generate configuration files for the supported vpn clients</para></listitem>
<answer><para>There may be many reaons for the compilation to fail : lack of development tools and/or files, unstable code version ... Please try to search the web for your error and if you don't find an answer, then contact the team.</para></answer>
</qandaentry>
<qandaentry>
<question><para>What I have to do to get IPSec working?</para></question>
<answer>
<para>Please install and configure FreeS/WAN (Linux 2.4.x)/ipsec-tools (Linux 2.6.x) first.</para>
<para>Then do the following steps:</para>
<orderedlist>
<listitem><para>Import certificate (if X.509 is needed and it is PKCS12 which is ended with .p12).</para></listitem>
<listitem><para>Setup a new connection (gateway, ...)</para></listitem>
<listitem><para>Setup authentication (username,password/certificate/pre shared key) of the newly created connection.</para></listitem>
</orderedlist>
</answer>
</qandaentry>
<qandaentry>
<question><para>What I need for PPTP?</para></question>
<answer><para>You need a kernel with MPPE support and the <ulink url="http://sourceforge.net/projects/pptpclient/">pptpclient</ulink>.</para></answer>
</qandaentry>
</qandaset>
</chapter>
<chapter id="credits">
<!-- Include credits for the programmers, documentation writers, and
contributors here. The license for your software should then be included below
the credits with a reference to the appropriate license file included in the KDE
distribution. -->
<title>Credits and License</title>
<para>
&kvpnc;
</para>
<para>
Program copyright 2004-2005 Christoph Thielecke <email>crissi99@gmx.de</email>
</para>
<para>
Contributors:
<itemizedlist>
<listitem><para>KDE developers for great KDE.</para></listitem>
<listitem><para>KDevelop developers for great KDevelop.</para></listitem>
<listitem><para>Maurice Massar <email>vpnc@unix-ag.uni-kl.de</email> for his vpnc.</para></listitem>
<listitem><para>Laurent Montel <email>montel@kde.org</email> for patches.</para></listitem>
<listitem><para>Peter Kussmann <email>peter.kussmann@gmx.de</email> for various test environments and new ideas.</para></listitem>
<listitem><para>D. Klinkenberg <email>d.klinkenberg@gmx.net</email> for intensive testing PPTP functionality, usebility hints, tests and bug hunting.</para></listitem>
<listitem><para>All other people which report bugs.</para></listitem>
</itemizedlist>
</para>
<para>
Packagers:
<itemizedlist>
<listitem><para>Carsten Schöne <email>cs@linux-adminstrator.com</email> for building SuSE packages.</para></listitem>
</itemizedlist>
</para>
<!-- TRANS:CREDIT_FOR_TRANSLATORS -->
<para>
<itemizedlist>
<listitem><para>Christoph Thielecke <email>crissi99@gmx.de</email> - german translation</para></listitem>
<para>Click on "New profile..." from Profile menu.</para>
</listitem>
<listitem>
<para>Select the type of connection, hostname of the vpn server. Also fill in remote network, username, password, pres shared key (PSK) or certificate if nessary.</para>
</listitem>
<listitem>
<para>Click "Ok" for creating the new profile.</para>
</listitem>
</orderedlist>
<!-- </para> -->
<!-- </listitem> -->
<!--Start kvpnc from KDE - Internet - kvpnc. Change in preferences dialog the global settings. Click on "New profile..." to add a new profile. Enter the new Name in the upcoming dialog, fill in the empty fields and save profile by clicking on "Save profile...". After enter your VPN data, click on "connect" to connect to your VPN server. By default, kvpnc minimizes into kicker dock after sucessfull connect.-->
