Bug#208890: ssh: scp -p makes wrong dates
Package: ssh
Version: 1:3.6.1p2-3
Severity: normal
When I use scp -p with some files, I end up with Dec 31 1969 as their
dates on the remote system. It may be relevant that the source system
is using vfat to hold them. The source system has no problem telling
their proper date.
Both systems running Debian; I'm filing this report from the "remote"
system. I experience the problem regardless of the system I run scp
from.
Could be classified as minor, but it does complicate figuring out
which files need to be updated.
Here's one file on the source system:
-rwxr--r-- 1 ross family 1953154 2003-09-04 22:18 orgs.gno
and then on the target system after scp -p:
-rwxr--r-- 1 ross ross 1953154 Dec 31 1969 orgs.gno
The file is not executable, by the way; that's a VFAT artifact. It's
a FAT32 file system.
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux iron 2.4.20 #1 SMP Thu Jun 26 15:57:25 PDT 2003 i686
Locale: LANG=C, LC_CTYPE=C
Versions of packages ssh depends on:
ii adduser 3.50 Add and remove users and groups
ii debconf 1.3.8 Debian configuration management sy
ii libc6 2.3.2-2 GNU C Library: Shared libraries an
ii libpam-modules 0.76-13 Pluggable Authentication Modules f
ii libpam0g 0.76-13 Pluggable Authentication Modules l
ii libssl0.9.7 0.9.7b-2 SSL shared libraries
ii libwrap0 7.6-ipv6.1-3 Wietse Venema's TCP wrappers libra
ii zlib1g 1:1.1.4-14 compression library - runtime
-- debconf information:
* ssh/privsep_tell:
ssh/insecure_rshd:
ssh/privsep_ask: true
ssh/ssh2_keys_merged:
ssh/user_environment_tell:
* ssh/forward_warning:
ssh/insecure_telnetd:
ssh/new_config: true
* ssh/use_old_init_script: true
* ssh/protocol2_only: true
ssh/encrypted_host_key_but_no_keygen:
* ssh/run_sshd: true
* ssh/SUID_client: true
Reply to: