On Thu, 5 Feb 2015 07:50:29 -0600, Dana Mitchell wrote: >>> >>Use .ssh. That's what it's for. > >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. > I thought "sftp" has no ASCII mode. Kirk?
>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. > That shouldn't be. Is it possible that your target user ID is defined in RACF with a default OMVS segment with HOME="/tmp"? This could cause other problems; can you get it changed? Dovetailed's suggestion of doing everything with sftp is clever (but I don't trust the ASCII command.) I think it would be simpler to make a one-time ssh connection and use the ssh-keygen command. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
