Hello,
apache 1.3.26
after last upgrades I have lots of:
# lsof | grep DEL
apache-ss 28184root memDEL0,4 229382
/SYSV
...
It is normal ? I dont think so... but how to solve this problem ?
I am not exactly understand what is going on with "DEL" "flag".
Co
Hello,
apache 1.3.26
after last upgrades I have lots of:
# lsof | grep DEL
apache-ss 28184root memDEL0,4 229382 /SYSV
...
It is normal ? I dont think so... but how to solve this problem ?
I am not exactly understand what is going on with "DEL" "flag".
Cou
In article <[EMAIL PROTECTED]> you wrote:
> -rwsr-xr-x1 root root22460 Oct 1 2001 /usr/bin/crontab
>
> yes, because only in this condition normal user can set crontab rules.
this deends on the cron used. The cron in qustion needs to restrict the
access to the spool directory bec
In article <[EMAIL PROTECTED]> you wrote:
> -rwsr-xr-x1 root root22460 Oct 1 2001 /usr/bin/crontab
>
> yes, because only in this condition normal user can set crontab rules.
this deends on the cron used. The cron in qustion needs to restrict the
access to the spool directory bec
Hello,
> Everybody knows that files with a suid bit set can be dangerous.
yes :) sgids too :)
> Well, i was asking myself today why exactly linux uses the suid bit files?!
because binaries are executed with almost the same rights as the
user-owner-of-file [effective UID]
> Could someone please
On Fri, Apr 16, 2004 at 11:02:56PM +0100, Mario Ohnewald wrote:
> Everybody knows that files with a suid bit set can be dangerous.
Everybody knows that almost everything is dangerous.
> Well, i was asking myself today why exactly linux uses the suid bit files?!
> Could someone please explain t
Hello!
Everybody knows that files with a suid bit set can be dangerous.
Well, i was asking myself today why exactly linux uses the suid bit files?!
Could someone please explain that to me?
Example:
~$ ls -lah /var/spool/cron/crontabs/user
-rw---1 root user 408 Apr 16
Ok, th
Hello,
> Everybody knows that files with a suid bit set can be dangerous.
yes :) sgids too :)
> Well, i was asking myself today why exactly linux uses the suid bit files?!
because binaries are executed with almost the same rights as the
user-owner-of-file [effective UID]
> Could someone please
On Fri, Apr 16, 2004 at 11:02:56PM +0100, Mario Ohnewald wrote:
> Everybody knows that files with a suid bit set can be dangerous.
Everybody knows that almost everything is dangerous.
> Well, i was asking myself today why exactly linux uses the suid bit files?!
> Could someone please explain t
Hello!
Everybody knows that files with a suid bit set can be dangerous.
Well, i was asking myself today why exactly linux uses the suid bit files?!
Could someone please explain that to me?
Example:
~$ ls -lah /var/spool/cron/crontabs/user
-rw---1 root user 408 Apr 16
Ok, th
For convenience, below is the original issue as it was posted on
BugTraq...
From: "Nikita V. Youshchenko" <[EMAIL PROTECTED]>
To: bugtraq@securityfocus.com
Subject: Possible DoS on Linux kernel 2.4 and 2.6 using sigqueue
overflow.
Date: Mon, 12 Apr 2004 06:06:04 -0400
User-Agent: KMail/1.5.4
He
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
All,
I am bringing this issue before you for discussion and guidance. There
is a security issue described in the mentioned bug:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=243954
Please review the bug and contribute if you have any suggestions
For convenience, below is the original issue as it was posted on
BugTraq...
From: "Nikita V. Youshchenko" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Possible DoS on Linux kernel 2.4 and 2.6 using sigqueue
overflow.
Date: Mon, 12 Apr 2004 06:06:04 -0400
User-Agent: KMail/1.5.4
Hello.
We
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
All,
I am bringing this issue before you for discussion and guidance. There
is a security issue described in the mentioned bug:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=243954
Please review the bug and contribute if you have any suggestions
Robert Velter a dit :
> Hello all,
>
> there seems to be a new apache vulnerability. Following error messages
> occure many times in my error.log:
>
[...]
> System is woody with all security updates applied.
> Any hints or tips how to track down the attack?
>
A good start might be :
LogLevel debu
Hello all,
there seems to be a new apache vulnerability. Following error messages
occure many times in my error.log:
...
[Fri Apr 16 13:16:33 2004] [error] [client 212.118.85.143] request
failed: URI too long
[Fri Apr 16 13:52:39 2004] [notice] child pid 31788 exit signal
Segmentation fault (11)
Robert Velter a dit :
> Hello all,
>
> there seems to be a new apache vulnerability. Following error messages
> occure many times in my error.log:
>
[...]
> System is woody with all security updates applied.
> Any hints or tips how to track down the attack?
>
A good start might be :
LogLevel debu
Hello all,
there seems to be a new apache vulnerability. Following error messages
occure many times in my error.log:
...
[Fri Apr 16 13:16:33 2004] [error] [client 212.118.85.143] request
failed: URI too long
[Fri Apr 16 13:52:39 2004] [notice] child pid 31788 exit signal
Segmentation fault (11)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday 16 April 2004 08.20, David R wrote:
> 1) At first, didn't realize I needed to uncomment the word prompt in
> lilo.conf (though I figured this one out before posting to the
> group).
You can just hold down the shift or control key when booti
On Wed, Apr 14, 2004 at 05:20:49PM +0200, Martin Schulze wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> - --
> Debian Security Advisory DSA 481-1 [EMAIL PROTECTED]
> http://www.debian.org/sec
Thanks for the many replies. Just for the record, I thought I'd type out
what I had to go through to get everything to work:
1) At first, didn't realize I needed to uncomment the word prompt in
lilo.conf (though I figured this one out before posting to the group).
2) The reason I received the erro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday 16 April 2004 08.20, David R wrote:
> 1) At first, didn't realize I needed to uncomment the word prompt in
> lilo.conf (though I figured this one out before posting to the
> group).
You can just hold down the shift or control key when booti
22 matches
Mail list logo
