On Wed, 4 Feb 2015 15:03:17 -0700, Paul Gilmartin <paulgboul...@aim.com> wrote: >> >Use .ssh. That's what it's for. >
Gil, If by that you mean, utilizing these steps from a 2009 Dovetailed presentation: (zoshost's sftp client still connected to remote host) sftp> pwd Remote working directory: /home/kirk/ sftp> mkdir .ssh (if necessary) sftp> chmod 700 .ssh sftp> cd .ssh sftp> ascii Sets the file transfer type to ASCII. sftp> put id_dsa.pub authorized_keys sftp> chmod 600 authorized_keys sftp> quit I tried that but it didn't work. "pwd" didn't show me as being in /home/<userid>, instead it showed that I was in /tmp. So I created a .ssh directory and authorized_keys file in /tmp anyways but it didn't work when reconnecting to this host. Dana ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
