From: Dimitri Papadopoulos <3350651+DimitriPapadopoulos@users.noreply.gitlab.com>
Date: Mon, 21 Jun 2021 17:34:55 +0000 (+0200)
Subject: Get rid of trailing spaces
X-Git-Tag: v8.20~129^2
X-Git-Url: https://www.infradead.org/git/?a=commitdiff_plain;h=45f7999da39d9b3ccd8b61ba01ed6da0f8b8ccce;p=users%2Fdwmw2%2Fopenconnect.git

Get rid of trailing spaces

Signed-off-by: Dimitri Papadopoulos <3350651+DimitriPapadopoulos@users.noreply.gitlab.com>
---

diff --git a/fortinet.c b/fortinet.c
index 0b220b7a..08ca63ce 100644
--- a/fortinet.c
+++ b/fortinet.c
@@ -541,7 +541,7 @@ static int fortinet_configure(struct openconnect_info *vpninfo)
 	 * FortiOS 4 was the last version to send the legacy HTTP configuration.
 	 * FortiOS 5 and later send the current XML configuration.
 	 * We clearly do not need to support FortiOS 4 anymore.
-	 * 
+	 *
 	 * Yet we keep this code around in order to get a sanity check about
 	 * whether the SVPNCOOKIE is still valid/alive, until we are sure we've
 	 * worked out the weirdness with reconnects.
diff --git a/openconnect-internal.h b/openconnect-internal.h
index 97f0ba24..ac692f4c 100644
--- a/openconnect-internal.h
+++ b/openconnect-internal.h
@@ -1240,7 +1240,7 @@ int do_gen_hotp_code(struct openconnect_info *vpninfo,
 		     struct oc_auth_form *form,
 		     struct oc_form_opt *opt);
 
-int set_oidc_token(struct openconnect_info *vpninfo, 
+int set_oidc_token(struct openconnect_info *vpninfo,
 		     const char *token_str);
 
 /* stoken.c */
diff --git a/www/contribute.xml b/www/contribute.xml
index 34a8945d..ea83425f 100644
--- a/www/contribute.xml
+++ b/www/contribute.xml
@@ -132,7 +132,7 @@ perhaps even Google Summer of Code projects.</p>
 
 <h2>Other enhancements</h2>
 
-One of the main other improvements that would be welcome, is implementing a full WebView in the graphical clients. Currently for protocols like Juniper, OpenConnect screen-scrapes the HTML pages used for login, and attempts to make sense of them. This is The main thing that would be 
+One of the main other improvements that would be welcome, is implementing a full WebView in the graphical clients. Currently for protocols like Juniper, OpenConnect screen-scrapes the HTML pages used for login, and attempts to make sense of them. This is The main thing that would be
 Other items on the TODO list include:
 
 <ul>
diff --git a/www/licence.xml b/www/licence.xml
index cd3a95ee..1eb1d8c2 100644
--- a/www/licence.xml
+++ b/www/licence.xml
@@ -638,17 +638,17 @@ under Windows, used with permission from
 <table border="1"><tr><td>
 <pre>
 Copyright 2007, 2010 by Nathan C. Myers &lt;ncm@cantrip.org&gt;
-Redistribution and use in source and binary forms, with or without modification, 
+Redistribution and use in source and binary forms, with or without modification,
 are permitted provided that the following conditions are met:
 
     Redistributions of source code must retain the above copyright notice, this
     list of conditions and the following disclaimer.
-    
+
     Redistributions in binary form must reproduce the above copyright notice,
     this list of conditions and the following disclaimer in the documentation
     and/or other materials provided with the distribution.
 
-    The name of the author must not be used to endorse or promote products derived 
+    The name of the author must not be used to endorse or promote products derived
     from this software without specific prior written permission.
 
 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY
@@ -704,7 +704,7 @@ THE POSSIBILITY OF SUCH DAMAGE.
 <table border="1"><tr><td>
   <pre>
 Copyright (C) 2012, 2013 James McLaughlin et al.  All rights reserved.
- 
+
 Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions
 are met:
diff --git a/www/mail.xml b/www/mail.xml
index f2b8cc50..7d40f3c2 100644
--- a/www/mail.xml
+++ b/www/mail.xml
@@ -47,7 +47,7 @@
 	  If you are posting debugging output from openconnect to the mailing list, do <em>not</em> include a line which looks like this:
 	  <br/><tt>Set-Cookie: webvpn=835278264@921600@1221512527@6B9EC24DEB2F59E242F75B424D42F223D0912984;PATH=/</tt><br/>
 	  That HTTP cookie is all that's needed to grant access to the VPN session you just logged in to &#8212;
-	  it's almost as bad as giving your password away. Version 2.26 or later of OpenConnect will 
+	  it's almost as bad as giving your password away. Version 2.26 or later of OpenConnect will
 	  automatically filter this out of the debugging output for you.
 	</p>
 	<p>For Juniper VPN, the equivalent is a <tt>DSID</tt> cookie, which is not yet filtered
diff --git a/www/platforms.xml b/www/platforms.xml
index 2b2d1764..3812c42b 100644
--- a/www/platforms.xml
+++ b/www/platforms.xml
@@ -14,7 +14,7 @@
 <p>OpenConnect is known to work, with both IPv6 and Legacy IP, on Linux
 (<a href="https://github.com/cernekee/ics-openconnect">including
 Android</a>), OpenBSD, FreeBSD (including Debian GNU/kFreeBSD), NetBSD,
-DragonFly BSD, OpenIndiana/OpenSolaris, Solaris 10/11, Windows and 
+DragonFly BSD, OpenIndiana/OpenSolaris, Solaris 10/11, Windows and
 Mac OS X platforms, and should be trivially portable to any other platform
 supporting <a href="https://en.wikipedia.org/wiki/TUN/TAP">TUN/TAP</a> devices
 and on which <a href="https://www.gnutls.org/">GnuTLS</a> or
diff --git a/www/styles/main.css b/www/styles/main.css
index 43ea8bb9..b9465d8b 100644
--- a/www/styles/main.css
+++ b/www/styles/main.css
@@ -1,7 +1,7 @@
 body {
     background: white;
     font-family: 'Raleway', Sans, Arial, Helvetica, Geneva, Swiss, SunSans-Regular;
-    font-size: 12px; 
+    font-size: 12px;
 }
 
 #logo {
@@ -56,9 +56,9 @@ body {
 }
 
 #menu1 .nonsel a:hover span {
-    color: Black;    
-    text-decoration: underline; 
-    background: url(../images/rightsel.png) top right no-repeat transparent;    
+    color: Black;
+    text-decoration: underline;
+    background: url(../images/rightsel.png) top right no-repeat transparent;
 }
 
 #menu1 .sel a {
@@ -67,7 +67,7 @@ body {
     padding-top: 0.2em;
     background: url(../images/leftsel.png) top left no-repeat #e6e6e6;
     margin-top: 0.2em;
-    margin-left: 5px;    
+    margin-left: 5px;
     height: 2em;
     text-decoration: none;
 }
@@ -106,9 +106,9 @@ body {
 }
 
 #menu2 .nonsel a:hover span {
-    color: Black;    
-    text-decoration: underline; 
-    background: url(../images/rightsel2.png) top right no-repeat transparent;    
+    color: Black;
+    text-decoration: underline;
+    background: url(../images/rightsel2.png) top right no-repeat transparent;
 }
 
 #menu2 .sel a {
@@ -116,7 +116,7 @@ body {
     float: left;
     padding: 0.2em 1em 0 1em;
     margin-top: 0.2em;
-    margin-left: 0px;    
+    margin-left: 0px;
     height: 2em;
     text-decoration: none;
 }
@@ -130,13 +130,13 @@ body {
     padding-left: 20px;
     padding-right: 120px;	
     padding-bottom: 20px;	
-    font-size: 14px; 
+    font-size: 14px;
 }
 
 #text {
     margin: 0;
     border-color: #e6e6e6;
-    font-size: 14px; 
+    font-size: 14px;
     background: #ffffff;
 }
 
diff --git a/www/token.xml b/www/token.xml
index d484173a..d3d2fa24 100644
--- a/www/token.xml
+++ b/www/token.xml
@@ -30,7 +30,7 @@ argument, and the precise form it takes is dependent on the type of
 token as described below.</p>
 <p>For the <tt>openconnect</tt> command line program, if the first character of
 the <tt>--token-secret</tt> value is / or @, the argument is interpreted as a
-filename. The secret data will be loaded from <i>(and potentially saved back 
+filename. The secret data will be loaded from <i>(and potentially saved back
 to, in the case of HOTP tokens)</i> the specifed file.</p>
 
 <p>In each case, the automatic token generation will be tried twice before it
@@ -46,7 +46,7 @@ in which it is not appropriate, please <a href="mail.html">let us know</a>.</p>
 <p>If no <tt>--token-secret</tt> argument is provided in SecurID mode, the
 default <tt>.stokenrc</tt> file from the user's home directory will be used.
 For the NetworkManager integration, this is a separate choice for the token
-type — the UI has separate choices for <i>"RSA SecurID - read from ~/.stokenrc"</i> vs. 
+type — the UI has separate choices for <i>"RSA SecurID - read from ~/.stokenrc"</i> vs.
 <i>"RSA SecurID - manually entered"</i>.</p>
 
 <p>If a token is provided — either directly on the command line, as the contents
@@ -126,13 +126,13 @@ They may be specified in one of the following forms:</p>
   <li><b>sha256:0x53656372657453656372657421</b></li>
   <li><b>sha512:0x53656372657453656372657421</b><br/>
   This is the hexadecimal form which <i>(without the leading <tt>0x</tt>)</i> is
-  accepted by default by the 
+  accepted by default by the
   <tt><a href="https://www.nongnu.org/oath-toolkit/oathtool.1.html">oathtool</a></tt>
   program.</li>
   <li><b>base32:KNSWG4TFORJWKY3SMV2CC===</b></li>
   <li><b>sha256:base32:KNSWG4TFORJWKY3SMV2CC===</b></li>
   <li><b>sha512:base32:KNSWG4TFORJWKY3SMV2CC===</b><br/>
-  This is the base32 form which is accepted by the 
+  This is the base32 form which is accepted by the
   <tt><a href="https://www.nongnu.org/oath-toolkit/oathtool.1.html">oathtool</a></tt>
   program with its <tt>-b</tt> option..</li>
   <li><b>&amp;lt;?xml version=...</b><br/>