Hi,
seems racoon doesn't check properly for valid x509 certs (BID 10546).
Are
Suse 9.1 IPsec tools vulnerable? I haven't looked into the relevant
portion of code yet, but it looks like it is. Bugtraq recommends an
upgrade to 0.3.3 .
Cheers,
Dirk Wetter
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
http://promotions.yahoo.com/new_mail
Same problem here. Also using Nvidia MX-440
-----Original Message-----
From: Al Bogner [mailto:suse-linux@ml04q2.pinguin.uni.cc]
Sent: 20 June 2004 05:51 PM
To: suse-security(a)suse.com
Subject: Re: [suse-security] Kernel update hangs system!
Am Freitag, 18. Juni 2004 07:20 schrieb Stefan Proels:
> I have a similar problem on one of my machines running SuSE Linux
> 9.1. The boot process hangs right after fsck has completed and
> reported all 4 drives as clean.
Here too. If anyone is interested in my hardware details, you can
have look at my posting in German, which shows hwinfo and the last
working boot.msg -
http://lists.suse.com/archive/suse-linux/2004-Jun/2602.html
Feedback to SuSE was sent.
Al
--
Check the headers for your unsubscription address
For additional commands, e-mail: suse-security-help(a)suse.com
Security-related bug reports go to security(a)suse.de, not here
I experienced an unpleasant side affect with the latest kernel update for SuSE
9.1. One (older Pentium-S system) hangs early in the boot process after
installing this update. Rolling back to the version supplied on the
installation disks fixed this. The strange thing is, this didn't happen on
any of the newer systems update before or afterwards, just this one.
I can't find a reason why, but on a second try it resulted in the same
behavior. Locked solid, even after waiting for over an hour. Keyboard dead,
only responded to the power button. The last lines in the boot log read
Setting up network interfaces:
lo
Any suggestions on how to find out what goes wrong here? Since I only have
trusted local users, I'm not so worried about the implications of not having
the latest kernel, but sure I would like to know what happened. I'm using the
default kernel on this system.
Regards,
Arjen
Hi,
I have a Samba file server on my network , which is connected directly to the internet.
I use a SuSEfirewall2 firewall. My local network is 192.168.10.0/24
A couple a days ago, immediaty after I restarted the Samba service I've noticed 2 strange
attempted connections in the SYS_RECV state from the ip's 192.168.198.1 and 192.168.248.1
I runed a tcpdump on the interface and this are the results that I receive every time when I try to acces a local workstation from another workstation in the workgroup:
samba: # tcpdump -v host 192.168.198.1
tcpdump: listening on eth0
15:54:35.216239 192.168.198.1.deskshare > samba.local.netbios-ssn: S [tcp sum ok] 747291326:747291326(0) win 64240 <mss 1460,nop,nop,sackOK> (DF) (ttl 128, id 14273, len 48)
15:54:38.127516 192.168.198.1.deskshare > samba.local.netbios-ssn: S [tcp sum ok] 747291326:747291326(0) win 64240 <mss 1460,nop,nop,sackOK> (DF) (ttl 128, id 14284, len 48)
15:54:44.143570 192.168.198.1.deskshare > samba.local.netbios-ssn: S [tcp sum ok] 747291326:747291326(0) win 64240 <mss 1460,nop,nop,sackOK> (DF) (ttl 128, id 14335, len 48)
15:55:31.380908 192.168.10.7.netbios-ssn > 192.168.198.1.h323hostcall: S [tcp sum ok] 257313301:257313301(0) ack 760741268 win 8760 <mss 1460,nop,nop,sackOK> (DF) (ttl 128, id 32304, len 48)
15:55:34.241142 192.168.10.7.netbios-ssn > 192.168.198.1.h323hostcall: . [tcp sum ok] ack 1 win 8760 (DF) (ttl 128, id 43568, len 40)
15:55:34.355161 192.168.10.7.netbios-ssn > 192.168.198.1.h323hostcall: S [tcp sum ok] 257313301:257313301(0) ack 760741268 win 8760 <mss 1460,nop,nop,sackOK> (DF) (ttl 128, id 44080, len 48)
15:55:40.257204 192.168.10.7.netbios-ssn > 192.168.198.1.h323hostcall: . [tcp sum ok] ack 1 win 8760 (DF) (ttl 128, id 44336, len 40)
15:55:40.354232 192.168.10.7.netbios-ssn > 192.168.198.1.h323hostcall: S [tcp sum ok] 257313301:257313301(0) ack 760741268 win 8760 <mss 1460,nop,nop,sackOK> (DF) (ttl 128, id 45104, len 48)
15:54:35.216239 192.168.198.1.deskshare > samba.local.netbios-ssn: S [tcp sum ok] 747291326:747291326(0) win 64240 <mss 1460,nop,nop,sackOK> (DF) (ttl 128, id 14273, len 48)
15:54:38.127516 192.168.198.1.deskshare > samba.local.netbios-ssn: S [tcp sum ok] 747291326:747291326(0) win 64240 <mss 1460,nop,nop,sackOK> (DF) (ttl 128, id 14284, len 48)
15:54:44.143570 192.168.198.1.deskshare > samba.local.netbios-ssn: S [tcp sum ok] 747291326:747291326(0) win 64240 <mss 1460,nop,nop,sackOK> (DF) (ttl 128, id 14335, len 48)
15:55:31.380908 192.168.10.7.netbios-ssn > 192.168.198.1.h323hostcall: S [tcp sum ok] 257313301:257313301(0) ack 760741268 win 8760 <mss 1460,nop,nop,sackOK> (DF) (ttl 128, id 32304, len 48)
15:55:34.241142 192.168.10.7.netbios-ssn > 192.168.198.1.h323hostcall: . [tcp sum ok] ack 1 win 8760 (DF) (ttl 128, id 43568, len 40)
15:55:34.355161 192.168.10.7.netbios-ssn > 192.168.198.1.h323hostcall: S [tcp sum ok] 257313301:257313301(0) ack 760741268 win 8760 <mss 1460,nop,nop,sackOK> (DF) (ttl 128, id 44080, len 48)
15:55:40.257204 192.168.10.7.netbios-ssn > 192.168.198.1.h323hostcall: . [tcp sum ok] ack 1 win 8760 (DF) (ttl 128, id 44336, len 40)
15:55:40.354232 192.168.10.7.netbios-ssn > 192.168.198.1.h323hostcall: S [tcp sum ok] 257313301:257313301(0) ack 760741268 win 8760 <mss 1460,nop,nop,sackOK> (DF) (ttl 128, id 45104, len 48)
15:55:52.352331 192.168.10.7.netbios-ssn > 192.168.198.1.h323hostcall: S [tcp sum ok] 257313301:257313301(0) ack 760741268 win 8760 <mss 1460,nop,nop,sackOK> (DF) (ttl 128, id 46128, len 48)
What is going on?
Thank you
----
Home, no matter how far...
http://www.home.ro
DUDE!!! I didn't say you can unsubscribe ME from this list :-)
I submitted that link so you can see what you needed to do. Replace my
address with your own :P
ROFL!
-------- Original Message --------
Subject: confirm unsubscribe from suse-security(a)suse.com
Date: 19 Jun 2004 01:00:04 -0000
From: suse-security-help(a)suse.com
Reply-To:
suse-security-uc.1087606804.focefhocidlabfmklogj-u235sentinel=comcast.net(a)suse.com
To: u235sentinel(a)comcast.net
Hi! This is the ezmlm program. I'm managing the
suse-security(a)suse.com mailing list.
I'm working for my owner, who can be reached
at suse-security-owner(a)suse.com.
To confirm that you would like
u235sentinel(a)comcast.net
removed from the suse-security mailing list, please send an empty reply
to this address:
suse-security-uc.1087606804.focefhocidlabfmklogj-u235sentinel=comcast.net(a)suse.com
Usually, this happens when you just hit the "reply" button.
If this does not work, simply copy the address and paste it into
the "To:" field of a new message.
I haven't checked whether your address is currently on the mailing list.
To see what address you used to subscribe, look at the messages you are
receiving from the mailing list. Each message has your address hidden
inside its return path; for example, mary(a)xdd.ff.com receives messages
with return path: <suse-security-return-<number>-mary=xdd.ff.com(a)suse.com.
--- Administrative commands for the suse-security list ---
I can handle administrative requests automatically. Please
do not send them to the list address! Instead, send
your message to the correct command address:
For help and a description of available commands, send a message to:
<suse-security-help(a)suse.com>
To subscribe to the list, send a message to:
<suse-security-subscribe(a)suse.com>
To remove your address from the list, just send a message to
the address in the ``List-Unsubscribe'' header of any list
message. If you haven't changed addresses since subscribing,
you can also send a message to:
<suse-security-unsubscribe(a)suse.com>
For addition or removal of addresses, I'll send a confirmation
message to that address. When you receive it, simply reply to it
to complete the transaction.
If you need to get in touch with the human owner of this list,
please send a message to:
<suse-security-owner(a)suse.com>
Please include a FORWARDED list message with ALL HEADERS intact
to make it easier to help you.
--- Enclosed is a copy of the request I received.
Return-Path: <ashchemelinin(a)netscape.net>
Received: (qmail 29443 invoked from network); 19 Jun 2004 01:00:03 -0000
Received: from unknown (HELO hermes.suse.de) (195.135.221.8)
by 0 with SMTP; 19 Jun 2004 01:00:03 -0000
Received: from scanhost.suse.de (scanhost.suse.de [149.44.160.36])
by hermes.suse.de (Postfix) with ESMTP id 94D38727C4
for <suse-security-unsubscribe-u235sentinel=comcast.net(a)lists.suse.com>; Sat, 19 Jun 2004 03:00:03 +0200 (CEST)
Received: from hermes.suse.de ([10.0.0.1])
by scanhost.suse.de (scanhost [149.44.160.36]) (amavisd-new, port 10025)
with ESMTP id 09084-04
for <suse-security-unsubscribe-u235sentinel=comcast.net(a)lists.suse.com>;
Sat, 19 Jun 2004 02:59:49 +0200 (CEST)
Received: from Cantor.suse.de (cantor.suse.de [195.135.220.2])
(using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits))
(No client certificate requested)
by hermes.suse.de (Postfix) with ESMTP id 4FF87726B5
for <suse-security-unsubscribe-u235sentinel=comcast.net(a)suse.com>; Sat, 19 Jun 2004 02:59:47 +0200 (CEST)
Received: from imo-d02.mx.aol.com (imo-d02.mx.aol.com [205.188.157.34])
by Cantor.suse.de (Postfix) with ESMTP id CAABE7469FE
for <suse-security-unsubscribe-u235sentinel=comcast.net(a)suse.com>; Sat, 19 Jun 2004 02:58:01 +0200 (CEST)
Received: from ashchemelinin(a)netscape.net
by imo-d02.mx.aol.com (mail_out_v37_r2.6.) id d.1b5.afbf8ba (16238)
for <suse-security-unsubscribe-u235sentinel=comcast.net(a)suse.com>; Fri, 18 Jun 2004 20:57:57 -0400 (EDT)
Received: from netscape.net (mow-d23.webmail.aol.com [205.188.139.164]) by air-in03.mx.aol.com (v99_r4.8) with ESMTP id MAILININ32-3f6e40d38f9517d; Fri, 18 Jun 2004 20:57:57 -0400
Date: Fri, 18 Jun 2004 20:57:57 -0400
From: ashchemelinin(a)netscape.net (Anatoly Shchemelinin)
To: suse-security-unsubscribe-u235sentinel=comcast.net(a)suse.com
Subject: please unsubscribe my account
MIME-Version: 1.0
Message-ID: <3615B1A6.1B1DA4CF.1D4ED940(a)netscape.net>
X-Mailer: Atlas Mailer 2.0
X-AOL-IP: 67.124.109.240
X-AOL-Language: english
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: by amavisd-new at scanhost.suse.de
X-Spam-Status: No, hits=-3.4 tagged_above=-20.0 required=5.0 tests=BAYES_00,
RCVD_IN_BL_SPAMCOP_NET
X-Spam-Level:
__________________________________________________________________
Introducing the New Netscape Internet Service.
Only $9.95 a month -- Sign up today at http://isp.netscape.com/register
Netscape. Just the Net You Need.
New! Netscape Toolbar for Internet Explorer
Search from anywhere on the Web and block those annoying pop-ups.
Download now at http://channels.netscape.com/ns/search/install.jsp
hi there,
experiencing the kernel freeze on suse 9.0 on a remote system.
as soon as i upgrade to the latest kernel, the kernel will always freeze
when the /dev/hdc drive is attached.
booting fine when /dev/hdc is disconnected.
btw, i also have a very old box pentium1 some megabytes running suse 9.0
with the latest kernel, with a 4.3gig ide drive, that didnt show any
problems.
any news about these lockups with the new kernel? any eta for fixes?
thanks and cheers,
andy
affected system below. parts of dmesg output with the old/working kernel
----------
<4>hda: ST320423A, ATA DISK drive
<4>ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
<4>hdc: Maxtor 32049H2, ATA DISK drive
<4>hdd: TOSHIBA CD-ROM XM-6302B, ATAPI CD/DVD-ROM drive
<4>ide1 at 0x170-0x177,0x376 on irq 15
<4>hda: max request size: 128KiB
<6>hda: 40011300 sectors (20485 MB) w/512KiB Cache, CHS=39693/16/63,
UDMA(33)
<6> hda: hda1 hda2 hda3 hda4
<4>hdc: max request size: 128KiB
<6>hdc: 40021632 sectors (20491 MB) w/2048KiB Cache, CHS=39704/16/63,
UDMA(100)
Disk /dev/hda: 20.4 GB, 20485785600 bytes
255 heads, 63 sectors/track, 2490 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk /dev/hdc: 20.4 GB, 20491075584 bytes
255 heads, 63 sectors/track, 2491 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
/dev/hda2 on / type reiserfs (rw,acl,user_xattr)
/dev/hda3 on /usr type reiserfs (rw,acl,user_xattr)
/dev/hda4 on /var type reiserfs (rw,acl,user_xattr)
/dev/hdc1 on /opt/opt2 type reiserfs (rw)
0000:00:00.0 Host bridge: Intel Corp. 82815 815 Chipset Host Bridge and
Memory Controller Hub (rev 04)
0000:00:01.0 PCI bridge: Intel Corp. 82815 815 Chipset AGP Bridge (rev
04)
0000:00:1e.0 PCI bridge: Intel Corp. 82801BA/CA/DB/EB PCI Bridge (rev
11)
0000:00:1f.0 ISA bridge: Intel Corp. 82801BA ISA Bridge (LPC) (rev 11)
0000:00:1f.1 IDE interface: Intel Corp. 82801BA IDE U100 (rev 11)
0000:00:1f.2 USB Controller: Intel Corp. 82801BA/BAM USB (Hub #1) (rev
11)
0000:00:1f.3 SMBus: Intel Corp. 82801BA/BAM SMBus (rev 11)
0000:00:1f.4 USB Controller: Intel Corp. 82801BA/BAM USB (Hub #2) (rev
11)
0000:01:00.0 VGA compatible controller: ATI Technologies Inc 3D Rage Pro
AGP 1X/2X (rev 5c)
0000:02:0a.0 Ethernet controller: 3Com Corporation 3c905 100BaseTX
[Boomerang]
0000:02:0c.0 Ethernet controller: 3Com Corporation 3c905 100BaseTX
[Boomerang]
0000:02:0d.0 Ethernet controller: 3Com Corporation 3c905B 100BaseTX
[Cyclone] (rev 30)
Detected 601.498 MHz processor.
CPU: After generic identify, caps: 0383fbff 00000000 00000000
00000000
CPU: After vendor identify, caps: 0383fbff 00000000 00000000
00000000
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 128K
CPU: After all inits, caps: 0383fbff 00000000 00000000 00000040
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: Intel Celeron (Coppermine) stepping 03
I am running a SuSE 9.0 and use postfix (procmail) just for relay.
However, if I want to use a simple ipop3d, it just does not recognize USER command:
# telnet localhost 110
Trying ::1...
telnet: connect to address ::1: Connection refused
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
+OK POP3 v2003.83 server ready <510a.40cf1a78@localhost>
USER stefan
-ERR Unknown AUTHORIZATION state command
I guess is somehow related with shadow suite (shadow-4.0.3-191).
ipop3d was installed with SuSE (along with Cyrus witch I deactivated).
SSH is working.
Do you have any idea?
Thanks,
Stefan