[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#404134: marked as done (ssh-copy-id gets confused by current directory changes in shell startup scripts)

Your message dated Thu, 9 Dec 2010 15:05:10 +0000
with message-id <20101209150509.GA31150@riva.ucam.org>
and subject line Re: Bug#404134: openssh-server: sshd uses from home directory when copying identity.pub
has caused the Debian Bug report #404134,
regarding ssh-copy-id gets confused by current directory changes in shell startup scripts
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
404134: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=404134
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: openssh-server
Version: 1:4.3p2-7
Severity: normal

When doing ssh-copy-id the ssh server copies the .ssh/authorized_keys file to the wrong location, if the dir is changed in the .bashrc-file. E.g. if I do an "cd /tmp" in my .bashrc-file, it creates a directory /tmp/.ssh on the remote system and the identity is copied to /tmp/.ssh/authorized_keys.

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-2-k7
Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) (ignored: LC_ALL set to de_DE)

Versions of packages openssh-server depends on:
ii  adduser                      3.99        Add and remove users and groups
ii  debconf [debconf-2.0]        1.5.8       Debian configuration management sy
ii  dpkg                         1.13.22     package maintenance system for Deb
ii  libc6                        2.3.6.ds1-4 GNU C Library: Shared libraries
ii  libcomerr2                   1.39-1      common error description library
ii  libkrb53                     1.4.4-3     MIT Kerberos runtime libraries
ii  libpam-modules               0.79-3.2    Pluggable Authentication Modules f
ii  libpam-runtime               0.79-3.2    Runtime support for the PAM librar
ii  libpam0g                     0.79-3.2    Pluggable Authentication Modules l
ii  libselinux1                  1.32-2      SELinux shared libraries
ii  libssl0.9.8                  0.9.8c-3    SSL shared libraries
ii  libwrap0                     7.6.dbs-11  Wietse Venema's TCP wrappers libra
ii  openssh-client               1:4.3p2-7   Secure shell client, an rlogin/rsh
ii  zlib1g                       1:1.2.3-13  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/disable_cr_auth: false
  ssh/encrypted_host_key_but_no_keygen:

--- End Message ---
--- Begin Message --- 
Source: openssh
Source-Version: 1:5.6p1-1

On Thu, Dec 21, 2006 at 11:38:42PM +0100, Michael Naugk wrote:
> Package: openssh-server
> Version: 1:4.3p2-7
> Severity: normal
> 
> When doing ssh-copy-id the ssh server copies the .ssh/authorized_keys
> file to the wrong location, if the dir is changed in the .bashrc-file.
> E.g. if I do an "cd /tmp" in my .bashrc-file, it creates a directory
> /tmp/.ssh on the remote system and the identity is copied to
> /tmp/.ssh/authorized_keys.

This was fixed in OpenSSH 5.6p1:

20100618
 - (djm) [contrib/ssh-copy-id] Update key file explicitly under ~
   rather than assuming that $CWD == $HOME. bz#1500, patch from
   timothy AT gelter.com

You can find packages of this in experimental (which only need to be
installed on the client in order to fix this bug).

Thanks,

-- 
Colin Watson                                       [cjwatson@debian.org]

--- End Message ---
Reply to: