You’ll have to be a little more specific than that Im afraid.
> On 2 May 2022, at 01:55, Christopher Jennings
> wrote:
>
> Help with vulnerabilities
Help with vulnerabilities
Hey there,
I'm sorry for my typo. Yes, I mean 2.3.6.
Sincerely,
Denny
Von: Dr. Volker Thieme [mailto:volker.thieme+deb...@mailbox.org]
Gesendet: Montag, 1. Dezember 2014 21:13
An: Denny Bortfeldt
Cc: debian-security@lists.debian.org
Betreff: Re: OpenVPN DDoS Fix
Hi!
On 01 Dec 2014, at
Hi!
On 01 Dec 2014, at 17:17, Denny Bortfeldt wrote:
> Hello everyone!
>
> Is anyone in touch with the new openvpn update 2.6.3 and know when it will be
> released in debian repo?
Did you mean 2.3.6?
Sincerely,
Volker
—
On Mon, Dec 01, 2014 at 04:17:50PM +, Denny Bortfeldt wrote:
> Hello everyone!
>
> Is anyone in touch with the new openvpn update 2.6.3 and know when it will be
> released in debian repo?
> Read more at https://forums.openvpn.net/topic17625.html
>
The update in on the works.
Since the test
Hello everyone!
Is anyone in touch with the new openvpn update 2.6.3 and know when it will be
released in debian repo?
Read more at https://forums.openvpn.net/topic17625.html
Thanks in advance!
Sincerely,
Denny
On Mon, Sep 22, 2008 at 08:16:01AM +0200, Stefan Fritsch wrote:
> On Monday 22 September 2008, Felipe Figueiredo wrote:
> > > Try modsecurity, it should block invalid URI
> >
> > Speaking of which, shouldn't it be re-included in Debian now that
> > the licensing issue[1] is supposed to be over[2]?
On Monday 22 September 2008, Felipe Figueiredo wrote:
> > Try modsecurity, it should block invalid URI
>
> Speaking of which, shouldn't it be re-included in Debian now that
> the licensing issue[1] is supposed to be over[2]?
There is already an ITP bug, but I don't know the current status.
http:/
On Mon, 2008-09-22 at 09:15 +1000, Stephen Vaughan wrote:
> Try modsecurity, it should block invalid URI
>
Speaking of which, shouldn't it be re-included in Debian now that the
licensing issue[1] is supposed to be over[2]?
1. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=352344
2. http://blo
435 (apache).
If we get a "DDOS" we make a tcpdump and count the IPs (maximum 8 Dial Up
Accounts) to block them on our Firewall.
I don´t find any about this strange request on Google or some security
boards.
Is this a new kind of DDOS or just kiddy stuff? If someone have some
ur Webserverfarm and finally after 5 Minutes the Webserver(s) get
> out of memory:
>
>
>
> Out of Memory: Kill process 12082 (apache) score 199722 and children.
>
> Out of memory: Killed process 19435 (apache).
>
>
>
> If we get a "DDOS" we make a tcpdump
Client make about 80-100 strange Request per Minute and we get a peak
on our Webserverfarm and finally after 5 Minutes the Webserver(s) get out of
memory:
Out of Memory: Kill process 12082 (apache) score 199722 and children.
Out of memory: Killed process 19435 (apache).
If we get a "DDO
Robert,
The only way to truly recover from a break-in, is to fully restore the
system
from a trusted medium. That being said, here's what your script does:
1) Hide it's name in the process table as '/usr/sbin/nscd ' (100
spaces).
2) Bind to UDP port 1337 in order
Robert,
The only way to truly recover from a break-in, is to fully restore the system
from a trusted medium. That being said, here's what your script does:
1) Hide it's name in the process table as '/usr/sbin/nscd ' (100
spaces).
2) Bind to UDP port 1337 in order
ect
me yesterday, but I had put www-data on
cron.deny and thus it prevented the script from
being ran.
I think that a lot of people are probably
falling prey to this DDOS script right now based
upon e-mails I've received from people.
Shouldn't the apache user be automatically
denied from
ect
me yesterday, but I had put www-data on
cron.deny and thus it prevented the script from
being ran.
I think that a lot of people are probably
falling prey to this DDOS script right now based
upon e-mails I've received from people.
Shouldn't the apache user be automatically
denied from
16 matches
Mail list logo
