Skip to content

O
OpnSense
Commit 8a0e3bc7 authored by Franco Fichtner's avatar Franco Fichtner
Browse files
Options

wizard: remove html from description strings

parent 440e6b5b
Hide whitespace changes
Inline Side-by-side
Showing with 14 additions and 14 deletions
src/wizard/openvpn.xml
View file @ 8a0e3bc7
......@@ -42,7 +42,7 @@
<type>select</type>
<displayname>Type of Server</displayname>
<name>authtype</name>
<description>&lt;br/&gt;&lt;b&gt;NOTE:&lt;/b&gt; If you are unsure, leave this set to "Local User Access."</description>
<description>If you are unsure, leave this set to "Local User Access."</description>
<bindstofield>ovpnserver->step1->type</bindstofield>
<options>
<option>
......@@ -145,7 +145,7 @@
<value>ssl</value>
</option>
</options>
<description>&lt;br/&gt;The protocol used by your LDAP server. It can either be standard TCP or SSL encrypted.</description>
<description>The protocol used by your LDAP server. It can either be standard TCP or SSL encrypted.</description>
</field>
<field>
<name>scope</name>
......@@ -176,7 +176,7 @@
<type>input</type>
<size>40</size>
<bindstofield>ovpnserver->step2->authscope</bindstofield>
<description>Semicolon separated. This will be prepended to the search base DN above or you can specify full container path.&lt;br/&gt;EXAMPLE: CN=Users;DC=example&lt;br/&gt;EXAMPLE: CN=Users,DC=example,DC=com;OU=OtherUsers,DC=example,DC=com</description>
<description>Semicolon separated. This will be prepended to the search base DN above or you can specify full container path, e.g. CN=Users;DC=example or CN=Users,DC=example,DC=com;OU=OtherUsers,DC=example,DC=com</description>
</field>
<field>
<name>userdn</name>
......@@ -348,7 +348,7 @@
<field>
<name>keylength</name>
<displayname>Key length</displayname>
<description>&lt;br/&gt;Size of the key which will be generated. The larger the key, the more security is offers, but larger keys are generally slower to use.</description>
<description>Size of the key which will be generated. The larger the key, the more security is offers, but larger keys are generally slower to use.</description>
<type>select</type>
<value>2048</value>
<bindstofield>ovpnserver->step6->keylength</bindstofield>
......@@ -473,7 +473,7 @@
<field>
<name>keylength</name>
<displayname>Key length</displayname>
<description>&lt;br/&gt;Size of the key which will be generated. The larger the key, the more security is offers, but larger keys are generally slower to use.</description>
<description>Size of the key which will be generated. The larger the key, the more security is offers, but larger keys are generally slower to use.</description>
<type>select</type>
<value>2048</value>
<bindstofield>ovpnserver->step9->keylength</bindstofield>
......@@ -582,7 +582,7 @@
<value>TCP</value>
</option>
</options>
<description>&lt;br/&gt;Protocol to use for OpenVPN connections. If you are unsure, leave this set to UDP.</description>
<description>Protocol to use for OpenVPN connections. If you are unsure, leave this set to UDP.</description>
</field>
<field>
<name>localport</name>
......@@ -648,7 +648,7 @@
<value>4096</value>
</option>
</options>
<description>&lt;br/&gt;Length of Diffie-Hellman (DH) key exchange parameters, used for establishing a secure communications channel. As with other such settings, the larger values are more secure, but may be slower in operation.</description>
<description>Length of Diffie-Hellman (DH) key exchange parameters, used for establishing a secure communications channel. As with other such settings, the larger values are more secure, but may be slower in operation.</description>
</field>
<field>
<name>crypto</name>
......@@ -661,7 +661,7 @@
<value>dummy</value>
</option>
</options>
<description>&lt;br/&gt;The method used to encrypt traffic between endpoints. This setting must match on the client and server side, but is otherwise set however you like. Certain algorithms will perform better on different hardware, depending on the availability of supported VPN accelerator chips.</description>
<description>The method used to encrypt traffic between endpoints. This setting must match on the client and server side, but is otherwise set however you like. Certain algorithms will perform better on different hardware, depending on the availability of supported VPN accelerator chips.</description>
</field>
<field>
<name>digest</name>
......@@ -675,7 +675,7 @@
</option>
</options>
<value>SHA1</value>
<description>&lt;br/&gt;The method used to authenticate traffic between endpoints. This setting must match on the client and server side, but is otherwise set however you like.</description>
<description>The method used to authenticate traffic between endpoints. This setting must match on the client and server side, but is otherwise set however you like.</description>
</field>
<field>
<name>engine</name>
......@@ -688,7 +688,7 @@
<value>dummy</value>
</option>
</options>
<description>&lt;br/&gt;The hardware cryptographic accelerator to use for this VPN connection, if any.</description>
<description>The hardware cryptographic accelerator to use for this VPN connection, if any.</description>
</field>
<field>
<type>listtopic</type>
......@@ -728,7 +728,7 @@
<field>
<displayname>Compression</displayname>
<name>compression</name>
<description>&lt;br/&gt;Compress tunnel packets using the LZO algorithm. Adaptive compression will dynamically disable compression for a period of time if OpenVPN detects that the data in the packets is not being compressed efficiently.</description>
<description>Compress tunnel packets using the LZO algorithm. Adaptive compression will dynamically disable compression for a period of time if OpenVPN detects that the data in the packets is not being compressed efficiently.</description>
<bindstofield>ovpnserver->step10->compression</bindstofield>
<type>select</type>
<options>
......@@ -756,7 +756,7 @@
<displayname>Duplicate Connections</displayname>
<name>duplicate_cn</name>
<type>checkbox</type>
<description>Allow multiple concurrent connections from clients using the same Common Name.&lt;br/&gt;NOTE: This is not generally recommended, but may be needed for some scenarios.</description>
<description>Allow multiple concurrent connections from clients using the same Common Name. This is not generally recommended, but may be needed for some scenarios.</description>
<bindstofield>ovpnserver->step10->duplicate_cn</bindstofield>
</field>
<field>
......@@ -833,7 +833,7 @@
<type>checkbox</type>
<displayname>NetBIOS Options</displayname>
<bindstofield>ovpnserver->step10->nbtenable</bindstofield>
<description>Enable NetBIOS over TCP/IP. &lt;br/&gt;If this option is not set, all NetBIOS-over-TCP/IP options (including WINS) will be disabled.</description>
<description>Enable NetBIOS over TCP/IP. If this option is not set, all NetBIOS-over-TCP/IP options (including WINS) will be disabled.</description>
</field>
<field>
<displayname>NetBIOS Node Type</displayname>
......@@ -846,7 +846,7 @@
<value>dummy</value>
</option>
</options>
<description>&lt;br/&gt;Possible options: b-node (broadcasts), p-node (point-to-point name queries to a WINS server), m-node (broadcast then query name server), and h-node (query name server, then broadcast).</description>
<description>Possible options: b-node (broadcasts), p-node (point-to-point name queries to a WINS server), m-node (broadcast then query name server), and h-node (query name server, then broadcast).</description>
</field>
<field>
<displayname>NetBIOS Scope ID</displayname>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment

Technounit-GROUP 2023