On Wed, Nov 09, 2005 at 09:38:06PM +0100, Martin Schulze wrote:
It seems that this bug has been reintroduced with the last security
update for sarge (cpio 2.5-1.3 on i386).
You might have to take that up with the security team.
It has never been fixed for cpio 2.5-1 according to the changelog,
so the bug cannot be reintroduced. Also, looking at the differences
between 1.2 and 1.3 it cannot be reintroduced by the security update.
At least with cpio 2.5-1.2 it definitely works on i386. I just verified it:
client:~# dpkg -i /var/cache/apt/archives/cpio_2.5-1.2_i386.deb
dpkg - warning: downgrading cpio from 2.5-1.3 to 2.5-1.2.
(Reading database ... 34141 files and directories currently installed.)
Preparing to replace cpio 2.5-1.3 (using .../archives/cpio_2.5-1.2_i386.deb)
Unpacking replacement cpio ...
Setting up cpio (2.5-1.2) ...
client:~# dpkg -l cpio
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=b
||/ Name Version
+++-=-==
ii cpio 2.5-1.2
client:~# mt -f tapeserver:/dev/nst0 status
drive type = Generic SCSI-2 tape
drive status = 1073741824
sense key error = 0
residue count = 0
file number = 1
block number = 0
Tape block size 0 bytes. Density code 0x40 (unknown).
Soft error count since last status=0
General status bits on (8101):
EOF ONLINE IM_REP_EN
client:~# dpkg -i /var/cache/apt/archives/cpio_2.5-1.3_i386.deb
(Reading database ... 34141 files and directories currently installed.)
Preparing to replace cpio 2.5-1.2 (using .../archives/cpio_2.5-1.3_i386.deb)
Unpacking replacement cpio ...
Setting up cpio (2.5-1.3) ...
client:~# dpkg -l cpio
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=b
||/ Name Version
+++-=-==
ii cpio 2.5-1.3
client:~# mt -f tapeserver:/dev/nst0 status
tapeserver: Connection refused
mt: tapeserver:/dev/nst0: Illegal seek
Version 2.5-1.3 tries to connect to Port 512 instead of 22 as described
in the original bug reports. Version 2.5-1.2 works fine via ssh and
nothing else has been changed, so I would suggest that it is related to
the security update.
Regards,
Thomas
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
