Various style, typo and whitespace corrections

This commit is contained in:
Adrian-Ken Rueegsegger 2012-01-06 17:37:59 +01:00 committed by Tobias Brunner
parent 9d17c1a679
commit 5ed3e3a7e6
4 changed files with 10 additions and 11 deletions

View File

@ -5,8 +5,8 @@
Git repository Git repository
--------------------- ---------------------
For interested developers, we have a public repository. To check out and For interested developers, we have a public repository. To check out and compile
compile the code, you need the following tools: the code, you need the following tools:
- Git - Git
- a recent GNU C compiler (>= 3.x) - a recent GNU C compiler (>= 3.x)
@ -43,7 +43,7 @@ Then you're in, start the build as usual:
API documentation API documentation
----------------- -----------------
Charon and libstrongswan contain inline code documentation. These comments can Charon and libstrongswan contain inline code documentation. These comments can
be extracted using doxygen. It is built using 'make apidoc', which creates an be extracted using doxygen. It is built using 'make apidoc', which creates an
'apidoc' folder containing the HTML files. 'apidoc' folder containing the HTML files.

View File

@ -18,7 +18,7 @@ Contents
-------- --------
The strongSwan 4.x branch introduces a new build environment featuring The strongSwan 4.x branch introduces a new build environment featuring
GNU autotools. This should simplify the build process and package GNU autotools. This should simplify the build process and package
maintenance. maintenance.
First check for the availability of required packages on your system First check for the availability of required packages on your system
(section 2.). You may want to include support for additional features, which (section 2.). You may want to include support for additional features, which
@ -42,9 +42,9 @@ Contents
To check if your kernel fullfills the requirements, see section 4. To check if your kernel fullfills the requirements, see section 4.
Next add your connections to "/etc/ipsec.conf" and your secrets to Next add your connections to "/etc/ipsec.conf" and your secrets to
"/etc/ipsec.secrets". Connections that are to be negotiated by the new "/etc/ipsec.secrets". Connections that are to be negotiated by the new
IKEv2 charon keying daemon should be designated by "keyexchange=ikev2" and IKEv2 charon keying daemon should be designated by "keyexchange=ikev2" and
those by the IKEv1 pluto keying daemon either by "keyexchange=ikev1" or those by the IKEv1 pluto keying daemon either by "keyexchange=ikev1" or
the default "keyexchange=ike". the default "keyexchange=ike".
@ -118,7 +118,7 @@ Contents
--------------------------------- ---------------------------------
If you want to securely store your X.509 certificates and private RSA keys If you want to securely store your X.509 certificates and private RSA keys
on a smart card or a USB crypto token then you will need a PKCS #11 library on a smart card or a USB crypto token then you will need a PKCS #11 library
for the smart card of your choice. The OpenSC PKCS#11 library (use for the smart card of your choice. The OpenSC PKCS#11 library (use
versions >= 0.9.4) available from http://www.opensc.org/ supports quite a versions >= 0.9.4) available from http://www.opensc.org/ supports quite a
selection of cards and tokens (e.g. Aladdin eToken Pro32k, Schlumberger selection of cards and tokens (e.g. Aladdin eToken Pro32k, Schlumberger

2
NEWS
View File

@ -27,7 +27,7 @@ strongswan-4.6.1
- Therefore our approach of computing integrity checksums for plugins had to be - Therefore our approach of computing integrity checksums for plugins had to be
changed radically by moving the hash generation from the compilation to the changed radically by moving the hash generation from the compilation to the
post-installation phase. post-installation phase.
strongswan-4.6.0 strongswan-4.6.0
---------------- ----------------

View File

@ -74,8 +74,7 @@ struct diffie_hellman_t {
/** /**
* Returns the shared secret of this diffie hellman exchange. * Returns the shared secret of this diffie hellman exchange.
* *
* Space for returned secret is allocated and must be * Space for returned secret is allocated and must be freed by the caller.
* freed by the caller.
* *
* @param secret shared secret will be written into this chunk * @param secret shared secret will be written into this chunk
* @return SUCCESS, FAILED if not both DH values are set * @return SUCCESS, FAILED if not both DH values are set
@ -108,7 +107,7 @@ struct diffie_hellman_t {
diffie_hellman_group_t (*get_dh_group) (diffie_hellman_t *this); diffie_hellman_group_t (*get_dh_group) (diffie_hellman_t *this);
/** /**
* Destroys an diffie_hellman_t object. * Destroys a diffie_hellman_t object.
*/ */
void (*destroy) (diffie_hellman_t *this); void (*destroy) (diffie_hellman_t *this);
}; };