Package: rsync
Version: 2.6.4-6
Severity: grave
Tags: security
Justification: user security hole
Integer overflow in the receive_xattr function in the extended
attributes patch (xattr.c) for rsync before 2.6.8 might allow attackers
to execute arbitrary code via crafted extended attributes that tr
Package: openswan
Version: 1:2.4.4-1
Severity: grave
Justification: renders package unusable
the pluto binary will not run, due to a shared library depenency that is
not met:
[EMAIL PROTECTED]:~$ ldd /usr/lib/ipsec/pluto
libldap_r.so.2 => /usr/lib/libldap_r.so.2 (0x0ffa2000)
libp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Steve Langasek wrote:
| On Fri, May 20, 2005 at 08:42:33AM -0500, Jay Kline wrote:
|
|>Steve Langasek wrote:
|>| On Wed, May 18, 2005 at 08:31:51AM -0500, Jay Kline wrote:
|>|
|>|>Steve Langasek wrote:
|>|>| On Wed, May 18, 200
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Steve Langasek wrote:
| On Wed, May 18, 2005 at 08:31:51AM -0500, Jay Kline wrote:
|
|>Steve Langasek wrote:
|>| On Wed, May 18, 2005 at 07:51:05AM -0500, Jay Kline wrote:
|>|
|>|>| Jay, taking care to run rm -f /usr/lib/libldap.s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Steve Langasek wrote:
| On Wed, May 18, 2005 at 07:51:05AM -0500, Jay Kline wrote:
|
|>| Jay, taking care to run rm -f /usr/lib/libldap.so.2.0.15 before
doing so,
|>| would you mind upgrading to the libldap2 from unstable to see if it
fixes
|&
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Steve Langasek wrote:
| On Tue, May 17, 2005 at 11:41:01AM -0700, Ryan Murray wrote:
|
|>On Tue, May 17, 2005 at 12:49:30PM -0500, Jay Kline wrote:
|>
|>>Alexander Sack wrote:
|>>| I did not found any hints on this in the bug rep
rought my attention to this.
If you find the bug number, I would be interested in reading up on it.
Jay
- --
Jay Kline
[EMAIL PROTECTED]
p: 612.337.3517
c: 612.384.1568
- --
"This message (including any attachments) may contain proprietary or
privileged information, the use and disclosure of
sort. However, I am starting to lean towrads
libnss-ldap being the issue. Bug #302296
(http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=302296) does not
describe the error exactly, but much of the behavior is the same. Im
testing today on this..
Jay
- --
Jay Kline
[EMAIL PROTECTED]
p: 612.337.3
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeroen van Wolffelaar wrote:
| You don't happen to have a full disk or ran out of quota, right? I do
| have experiences with failed logins when stuff can't write to disk (temp
| files, log files, ...)
Disks have plenty of space (~80G free) and every use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ryan Murray wrote:
|>| And in /var/log/gdm/:0.log ? (It'll rotate to .1 when restarting)
|>|
|>It seems truncated, but here it is:
|>
|>XFree86 Version 4.3.0.1 (Debian 4.3.0.dfsg.1-12.0.1 20050223080930
|>[EMAIL PROTECTED]
|>elix.org)
|>Release Date: 1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ryan Murray wrote:
| On Thu, May 12, 2005 at 11:02:19AM -0500, Jay Kline wrote:
|
|>-BEGIN PGP SIGNED MESSAGE-
|>Hash: SHA1
|>
|>Ryan Murray wrote:
|>| On Wed, May 11, 2005 at 08:48:20AM -0500, Jay Kline wrote:
|>|
|>|>A
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ryan Murray wrote:
| On Wed, May 11, 2005 at 08:48:20AM -0500, Jay Kline wrote:
|
|>After a recent upgrade of gdm, logins "fail". A user inputs
|>username/password/securID login, it succeeds, goes to a black screen,
|>then back to
Package: gdm
Version: 2.6.0.8-1
Severity: grave
Justification: renders package unusable
After a recent upgrade of gdm, logins "fail". A user inputs
username/password/securID login, it succeeds, goes to a black screen,
then back to login. Here is the output to daemon.log:
gdm[23126]: gdm_slave_
Package: openoffice.org
Version: 1.1.3-7
Severity: grave
Tags: security patch
Justification: user security hole
Recently, SecurityFocus announced a vulnerability in OpenOffice version
1.1.4 and all prior versions. (http://www.securityfocus.com/archive/1/395516)
This allows a mallicous DOC file to
Package: postfix
Version: 2.1.5-4
Followup-For: Bug #291031
I ran into the same problem when upgrading. Perhaps there should be
something to verify that what is in alias_database is capable of having
newaliases run on it before running newaliases. This simple (and
common) mistake in main.cf will
15 matches
Mail list logo