At 07/07/2017 at 22:00, Shakespearean monkeys danced on Jerry Geis's
keyboard and said:
Any thoughts on why the e1000e would not talk to the switch ? The switch is
an unmanaged linksys - could not get the model. It auto negotiates to
1G/full.
+1 on the switch not being completely up itself.
Hi,
I'm currently experimenting with the mod_evasive module for Apache, to
protect the server against potential DoS attacks. Here's what I did so far.
# yum install mod_evasive
Don't touch mod_evasive's default configuration, just restart Apache.
# systemctl restart httpd
The package inclu
Am 09.07.2017 um 13:06 schrieb Nicolas Kovacs:
I tried this on two sandbox machine, one on my LAN, one on a public
server, and both times I got the same result.
Any suggestions?
Niki
What does apache log? I guess it logs more than just HTTP status 400.
Alexander
Le 09/07/2017 à 13:17, Alexander Dalloz a écrit :
> What does apache log? I guess it logs more than just HTTP status 400.
Unfortunately the Apache logs don't tell much.
192.168.2.5 - - [09/Jul/2017:13:01:27 +0200] "GET /?91 HTTP/1.0" 400 226
"-" "-"
192.168.2.5 - - [09/Jul/2017:13:01:27 +0200] "G
Le 09/07/2017 à 13:17, Alexander Dalloz a écrit :
> What does apache log? I guess it logs more than just HTTP status 400.
I wonder if something is wrong with the test.pl script. Here's what I have:
#!/usr/bin/perl
# test.pl: small script to test mod_dosevasive's effectiveness
use IO::Socket;
us
Hi,
Some time ago one of my public servers (running Slackware64 14.0) got
attacked and was misused to send phishing emails.
This misadventure made me more concerned about security, so I spent the
last few weeks catching up on security, reading docs about SELinux and
how to use it, etc.
I have a
If your site(s) are simple enough, look into modsecurity for Apache web
servers.
Also, use either iptables or the built-in firewalld stuff on centos7 to
restrict in/outbound ports.
On 07/09/2017 12:01 PM, Nicolas Kovacs wrote:
> Hi,
>
> Some time ago one of my public servers (running Slackware6
This turned out to be a blocking issue with rsyslog. So, the slapd issue
is solved by uncovering the root cause.
On 07/07/2017 07:24 PM, John Jasen wrote:
> Running CentOS7, with openldap-2.4.40-13.el7. The environment consists
> of two ldap providers, in mirror mode, serving over a shared virtua
I have multiple servers running stock CentOS 7 rsyslog 7.4.7-16.el7,
which are configured to log locally and over TCP to a remote logserver,
also running stock CentOS 7 rsyslog. The remote server uses imptcp to
receive, and pretty basic rules to parse and commit to disk.
I have several systems tha
On 07/09/2017 11:01 AM, Nicolas Kovacs wrote:
> Hi,
>
> Some time ago one of my public servers (running Slackware64 14.0) got
> attacked and was misused to send phishing emails.
>
> This misadventure made me more concerned about security, so I spent the
> last few weeks catching up on security, r
What I did on couple of my CentOS boxes is:
- use a bridge which is connected to the specific nic(will always look as up
after boot)
- Run a cron script that checks if the nic state is "NO-CARRIER" or other
weird situations like no IP address and try to run ifdown X-nic and then
ifup X-nic.
Depen
11 matches
Mail list logo
