Bug#334590: openssh-server: sshd segmentation fault (1:4.2p1-5 amd64)
Package: openssh-server Version: 1:4.2p1-5 Severity: critical Justification: breaks the whole system This might have already been reported, but openssh-server 1:4.2p1-5 segfaults on amd64 architectures [...] Oct 18 13:22:34 localhost kernel: sshd[11242]: segfault at 00038eb15e4c rip 2af55817 rsp 7fee2418 error 4 Oct 18 13:22:38 localhost kernel: sshd[11244]: segfault at 0003597d5e4c rip 2af55817 rsp 7f9a1158 error 4 Oct 18 13:22:43 localhost kernel: sshd[11245]: segfault at 1a015e4c rip 2af55817 rsp 7f8aca88 error 4 Oct 18 13:24:30 localhost kernel: sshd[11247]: segfault at 0001cd495e4c rip 2af55817 rsp 7ff72688 error 4 Oct 18 13:24:40 localhost kernel: sshd[11248]: segfault at 7bdd5e4c rip 2af55817 rsp 7fbfc6d8 error 4 Oct 18 13:25:41 localhost kernel: sshd[11250]: segfault at 669d5e4c rip 2af55817 rsp 7f985a18 error 4 [...] It renders remote servers impossible to access after an upgrade of thesystem. Best, Valerio Aimale -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12-1-amd64-k8-smp Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages openssh-server depends on: ii adduser 3.67.2 Add and remove users and groups ii debconf [debconf-2.0] 1.4.58 Debian configuration management sy ii dpkg 1.13.11package maintenance system for Deb ii libc6 2.3.5-7GNU C Library: Shared libraries an ii libcomerr21.38-2 common error description library ii libkrb53 1.3.6-5MIT Kerberos runtime libraries ii libpam-modules0.79-3 Pluggable Authentication Modules f ii libpam-runtime0.79-3 Runtime support for the PAM librar ii libpam0g 0.79-3 Pluggable Authentication Modules l ii libselinux1 1.26-1 SELinux shared libraries ii libssl0.9.7 0.9.7g-5 SSL shared libraries ii libwrap0 7.6.dbs-8 Wietse Venema's TCP wrappers libra ii openssh-client1:4.2p1-4 Secure shell client, an rlogin/rsh ii zlib1g1:1.2.3-6 compression library - runtime openssh-server recommends no packages. -- debconf information: ssh/insecure_rshd: ssh/insecure_telnetd: ssh/new_config: true * ssh/use_old_init_script: true ssh/encrypted_host_key_but_no_keygen: * ssh/disable_cr_auth: false -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#324886: 3.0.3-0 works fine
Andrew, I've tested the preliminary 3.0.3-0 and it works fine with one-lease-per-client set to on. Leases are obtained correctly and no more infinite loops. Thank you for your help Valerio > On Wed, Aug 24, 2005 at 07:26:34PM -0600, Valerio Aimale wrote: > > > > andrew, > > > > thank you for your reply, I will check 3.0.2 out and will report you my > > findings. > > > > There is a preliminary package of dhcp3-3.0.3 available at > http://people.debian.org/~apollock/dhcp3 > > Please test it (or build it on amd64 and test it) and copy the bug with your > findings. > > regards > > Andrew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#324886: dhcp3-server: server goes in infitine loop if one-lease-per-client is set
Package: dhcp3-server
Version: 3.0.2-3
Severity: grave
Justification: renders package unusable
Hello,
since when I upgraded to the most recent version of the package, I've noticed
that if one-lease-per-client is set to on and a client releases the old IP
and re-request new one (after a reboot for example), the dhcp server goes
into an inifite loop and writes the same information to the
dhcpd.leases file until it fills up the disk
dhcpd.leases file:
===
lease 192.168.2.210 {
starts 3 2005/08/24 16:19:15;
ends 3 2005/08/24 16:44:14;
tstp 3 2005/08/31 16:19:15;
binding state free;
hardware ethernet 00:e0:81:2e:9e:7a;
client-hostname "node1";
}
lease 192.168.2.210 {
starts 3 2005/08/24 16:19:15;
ends 3 2005/08/24 16:44:14;
tstp 3 2005/08/31 16:19:15;
binding state free;
hardware ethernet 00:e0:81:2e:9e:7a;
client-hostname "node1";
}
lease 192.168.2.210 {
starts 3 2005/08/24 16:19:15;
ends 3 2005/08/24 16:44:14;
tstp 3 2005/08/31 16:19:15;
binding state free;
hardware ethernet 00:e0:81:2e:9e:7a;
client-hostname "node1";
}
lease 192.168.2.210 {
starts 3 2005/08/24 16:19:15;
ends 3 2005/08/24 16:44:14;
tstp 3 2005/08/31 16:19:15;
binding state free;
hardware ethernet 00:e0:81:2e:9e:7a;
client-hostname "node1";
}
[...]
=
This renders the server unusable where one-lease-per-client is needed
my config
===
# option definitions common to all supported networks...
option domain-name "cluster";
option domain-name-servers 192.168.2.1, 192.168.1.2, 206.83.0.42;
default-lease-time 604800;
max-lease-time 604800;
authoritative;
log-facility local7;
do-forward-updates on;
ignore client-updates;
ddns-updates on;
ddns-update-style interim;
subnet 192.168.2.0 netmask 255.255.255.0 {
range 192.168.2.10 192.168.2.253;
option routers 192.168.2.1;
option domain-name "cluster";
option broadcast-address 192.168.2.255;
option domain-name-servers 192.168.2.1, 192.168.1.2, 206.83.0.42;
option netbios-name-servers 192.168.1.2;
option ntp-servers 192.168.2.1;
ddns-update-style interim;
update-static-leases true;
one-lease-per-client on;
}
=
I think the same bug was present in one of the 3.0 release candidates,
it might be the same surfacing again.
Same behavior is present on i386 architectures.
Thanks
Valerio Aimale
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.11-9-amd64-k8-smp
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Versions of packages dhcp3-server depends on:
ii debconf 1.4.56 Debian configuration management sy
ii debianutils 2.14.1 Miscellaneous utilities specific t
ii dhcp3-common 3.0.2-3Common files used by all the dhcp3
ii libc6 2.3.5-3GNU C Library: Shared libraries an
dhcp3-server recommends no packages.
-- debconf information:
* dhcp3-server/new_auth_behavior:
* dhcp3-server/interfaces: eth1
* dhcp3-server/config_warn:
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
