confdroid/confdroid_fail2ban
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

recommit for updates in build 35

Browse Source
This commit is contained in:
Jenkins ConfDroid
2021-09-10 14:08:17 +02:00
parent c4be49d93f
commit 105b665271
3 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
.scannerwork/report-task.txt
View File

@@ -2,5 +2,5 @@ projectKey=cd_fail2ban
serverUrl=http://sonarqube.confdroid.com
serverVersion=7.9.1.27448
dashboardUrl=http://sonarqube.confdroid.com/dashboard?id=cd_fail2ban
ceTaskId=AXvPWHgY1C1yMMr1H4EE
ceTaskUrl=http://sonarqube.confdroid.com/api/ce/task?id=AXvPWHgY1C1yMMr1H4EE
ceTaskId=AXvPm7qA1C1yMMr1H4EP
ceTaskUrl=http://sonarqube.confdroid.com/api/ce/task?id=AXvPm7qA1C1yMMr1H4EP

4
doc/file.README.html
View File

@@ -75,13 +75,13 @@ configuration and management of fail2ban settings and rules.</p>
<h2 id="label-WARNING">WARNING</h2>
<p><code>**__!!! Attention: Never use this puppet module on systems which have
<p><strong><em>Attention: Never use this puppet module on systems which have
been previously configured manually. It is impossible to predict how and
what would have been configured, hence previous configurations outside the
scope of this module may be overwritten! Automated configurations require a
test environment to verify that the module suits the purpose intended by
the user, as well as tune the parameters, before deploying into live
production!!! __**</code></p>
production</em></strong></p>
<h2 id="label-Features">Features</h2>

4
doc/index.html
View File

@@ -75,13 +75,13 @@ configuration and management of fail2ban settings and rules.</p>
<h2 id="label-WARNING">WARNING</h2>
<p><code>**__!!! Attention: Never use this puppet module on systems which have
<p><strong><em>Attention: Never use this puppet module on systems which have
been previously configured manually. It is impossible to predict how and
what would have been configured, hence previous configurations outside the
scope of this module may be overwritten! Automated configurations require a
test environment to verify that the module suits the purpose intended by
the user, as well as tune the parameters, before deploying into live
production!!! __**</code></p>
production</em></strong></p>
<h2 id="label-Features">Features</h2>