I am trying to get ssh to work in cron, and it seems like I have tried all the standard tricks with no luck at all. I can run a non-interactive ssh by using>./some_script_with_sshin bash. It's only when I try to use it in cron that it fails.  Any help I could get would be greatly appreciated.Below are some of the data requested in similar questions:My user's crontabPATH = /home/zach/.ssh/:/usr/bin52 * * * * ssh -vvv my_account@my_remote touch temp.tempPrintout from the email cron sent meOpenSSH_7.3p1 Ubuntu-1, OpenSSL 1.0.2g  1 Mar 2016debug1: Reading configuration data /etc/ssh/ssh_configdebug1: /etc/ssh/ssh_config line 19: Applying options for *debug2: resolving my_remote port 22debug2: ssh_connect_direct: needpriv 0debug1: Connecting to my_remote [IP_HERE] port 22.debug1: Connection established.debug1: identity file /home/zach/.ssh/id_rsa type 1debug1: key_load_public: No such file or directorydebug1: identity file /home/zach/.ssh/id_rsa-cert type -1debug1: Enabling compatibility mode for protocol 2.0debug1: Local version string SSH-2.0-OpenSSH_7.3p1 Ubuntu-1debug1: Remote protocol version 2.0, remote software version OpenSSH_6.2debug1: match: OpenSSH_6.2 pat OpenSSH* compat 0x04000000debug2: fd 3 setting O_NONBLOCKdebug1: Authenticating to my_remote:22 as 'my_account'debug3: hostkeys_foreach: reading file /home/zach/.ssh/known_hostsdebug3: record_hostkey: found key type ECDSA in file /home/zach/.ssh/known_hosts:1debug3: load_hostkeys: loaded 1 keys from my_remotedebug3: order_hostkeyalgs: prefer hostkeyalgs: ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521debug3: send packet: type 20debug1: SSH2_MSG_KEXINIT sentdebug3: receive packet: type 20debug1: SSH2_MSG_KEXINIT receiveddebug2: local client KEXINIT proposaldebug2: KEX algorithms: curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha256,diffie-hellman-group14-sha1,ext-info-cdebug2: host key algorithms: ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519-cert-v01@openssh.com,ssh-rsa-cert-v01@openssh.com,ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsadebug2: ciphers ctos: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,aes128-cbc,aes192-cbc,aes256-cbc,3des-cbcdebug2: ciphers stoc: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,aes128-cbc,aes192-cbc,aes256-cbc,3des-cbcdebug2: MACs ctos: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1debug2: MACs stoc: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1debug2: compression ctos: none,zlib@openssh.com,zlibdebug2: compression stoc: none,zlib@openssh.com,zlibdebug2: languages ctos:debug2: languages stoc:debug2: first_kex_follows 0debug2: reserved 0debug2: peer server KEXINIT proposaldebug2: KEX algorithms: ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1debug2: host key algorithms: ssh-rsa,ssh-dss,ecdsa-sha2-nistp256debug2: ciphers ctos: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-gcm@openssh.com,aes256-gcm@openssh.com,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.sedebug2: ciphers stoc: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-gcm@openssh.com,aes256-gcm@openssh.com,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.sedebug2: MACs ctos: hmac-md5-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-ripemd160-etm@openssh.com,hmac-sha1-96-etm@openssh.com,hmac-md5-96-etm@openssh.com,hmac-md5,hmac-sha1,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96debug2: MACs stoc: hmac-md5-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-ripemd160-etm@openssh.com,hmac-sha1-96-etm@openssh.com,hmac-md5-96-etm@openssh.com,hmac-md5,hmac-sha1,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96debug2: compression ctos: none,zlib@openssh.comdebug2: compression stoc: none,zlib@openssh.comdebug2: languages ctos:debug2: languages stoc:debug2: first_kex_follows 0debug2: reserved 0debug1: kex: algorithm: ecdh-sha2-nistp256debug1: kex: host key algorithm: ecdsa-sha2-nistp256debug1: kex: server->client cipher: aes128-ctr MAC: umac-64-etm@openssh.com compression: nonedebug1: kex: client->server cipher: aes128-ctr MAC: umac-64-etm@openssh.com compression: nonedebug3: send packet: type 30debug1: sending SSH2_MSG_KEX_ECDH_INITdebug1: expecting SSH2_MSG_KEX_ECDH_REPLYdebug3: receive packet: type 31debug1: Server host key: ecdsa-sha2-nistp256 SHA256:K8vzLDbyV5JKlcnHsIj6BK/yR4OTJaY4fFuHpsg0FdEdebug3: hostkeys_foreach: reading file /home/zach/.ssh/known_hostsdebug3: record_hostkey: found key type ECDSA in file /home/zach/.ssh/known_hosts:1debug3: load_hostkeys: loaded 1 keys from my_remotedebug3: hostkeys_foreach: reading file /home/zach/.ssh/known_hostsdebug3: record_hostkey: found key type ECDSA in file /home/zach/.ssh/known_hosts:2debug3: load_hostkeys: loaded 1 keys from 128.97.70.146debug1: Host 'my_remote' is known and matches the ECDSA host key.debug1: Found key in /home/zach/.ssh/known_hosts:1debug3: send packet: type 21debug2: set_newkeys: mode 1debug1: rekey after 4294967296 blocksdebug1: SSH2_MSG_NEWKEYS sentdebug1: expecting SSH2_MSG_NEWKEYSdebug3: receive packet: type 21debug2: set_newkeys: mode 0debug1: rekey after 4294967296 blocksdebug1: SSH2_MSG_NEWKEYS receiveddebug2: key: /home/zach/.ssh/id_rsa (0x55f6f6440f50)debug3: send packet: type 5debug3: receive packet: type 6debug2: service_accept: ssh-userauthdebug1: SSH2_MSG_SERVICE_ACCEPT receiveddebug3: send packet: type 50debug3: receive packet: type 51debug1: Authentications that can continue: publickey,gssapi-with-mic,password,keyboard-interactivedebug3: start over, passed a different list publickey,gssapi-with-mic,password,keyboard-interactivedebug3: preferred publickey,keyboard-interactivedebug3: authmethod_lookup publickeydebug3: remaining preferred: keyboard-interactivedebug3: authmethod_is_enabled publickeydebug1: Next authentication method: publickeydebug1: Offering RSA public key: /home/zach/.ssh/id_rsadebug3: send_pubkey_testdebug3: send packet: type 50debug2: we sent a publickey packet, wait for replydebug3: receive packet: type 60debug1: Server accepts key: pkalg ssh-rsa blen 279debug2: input_userauth_pk_ok: fp SHA256:jsePXa9FO8c9f0bVwdgvXMJQ2GyHVqz5spaO13EQ0/Mdebug3: sign_and_send_pubkey: RSA SHA256:jsePXa9FO8c9f0bVwdgvXMJQ2GyHVqz5spaO13EQ0/Mdebug1: read_passphrase: can't open /dev/tty: No such device or addressdebug2: no passphrase given, try next keydebug2: we did not send a packet, disable methoddebug3: authmethod_lookup keyboard-interactivedebug3: remaining preferred:debug3: authmethod_is_enabled keyboard-interactivedebug1: Next authentication method: keyboard-interactivedebug2: userauth_kbdintdebug3: send packet: type 50debug2: we sent a keyboard-interactive packet, wait for replydebug3: receive packet: type 60debug2: input_userauth_info_reqdebug2: input_userauth_info_req: num_prompts 1debug1: read_passphrase: can't open /dev/tty: No such device or addressdebug3: send packet: type 61debug3: receive packet: type 51debug1: Authentications that can continue: publickey,gssapi-with-mic,password,keyboard-interactivedebug2: userauth_kbdintdebug3: send packet: type 50debug2: we sent a keyboard-interactive packet, wait for replydebug3: receive packet: type 60debug2: input_userauth_info_reqdebug2: input_userauth_info_req: num_prompts 1debug1: read_passphrase: can't open /dev/tty: No such device or addressdebug3: send packet: type 61debug3: receive packet: type 51debug1: Authentications that can continue: publickey,gssapi-with-mic,password,keyboard-interactivedebug2: userauth_kbdintdebug3: send packet: type 50debug2: we sent a keyboard-interactive packet, wait for replydebug3: receive packet: type 60debug2: input_userauth_info_reqdebug2: input_userauth_info_req: num_prompts 1debug1: read_passphrase: can't open /dev/tty: No such device or addressdebug3: send packet: type 61debug3: receive packet: type 51debug1: Authentications that can continue: publickey,gssapi-with-mic,password,keyboard-interactivedebug2: we did not send a packet, disable methoddebug1: No more authentication methods to try.Permission denied (publickey,gssapi-with-mic,password,keyboard-interactive).Permissions on local RSA data>ls -l ~/.ssh/total 12-rw------- 1 zach zach 1766 Dec 22 13:47 id_rsa-rw-r--r-- 1 zach zach  419 Dec  4  2015 id_rsa.pub-rw-r--r-- 1 zach zach 1332 Dec 21 13:51 known_hostsPermissions on local home>ls -l ~/..total 20drwx------  2 root root 16384 Jul 17  2015 lost+founddrwx------ 67 zach zach  4096 Dec 22 16:05 zachPermissions on local ~/.ssh folderdrwx------  2 zach zach    4096 Dec 22 15:11 .sshPermissions on remote homedrwx------ 31 my_account       grad      4096 Dec 22 13:57 my_accountPermissions on remote RSA data> ls -l ~/.ssh/total 12-rwx------ 1 my_account grad 419 Dec  4  2015 authorized_keys-rw------- 1 my_account grad  36 Dec 20 22:45 config-rw------- 1 my_account grad 223 Sep 10 14:51 known_hostsPermissions on remote ~/.ssh folder> ls -l ~drwx------  2 my_account grad   4096 Dec 20 22:45 .sshLocal /etc/ssh/ssh_confighost *    passwordauthentication no    stricthostkeychecking no    identityfile ~/.ssh/id_rsa    sendenv lang lc_*    hashknownhosts yesRemote /etc/ssh/ssh_config> cat /etc/ssh/ssh_configHost *    Protocol            2    ServerAliveInterval     120    TCPKeepAlive        no    ConnectTimeout      5    NoHostAuthenticationForLocalhost    yes    PreferredAuthentications    gssapi-with-mic,publickey,keyboard-interactive,password    GSSAPIAuthentication    yes    SendEnv         LOGNAME LANG LC_*    ForwardX11Trusted       yesMy ssh key is not password protected.>env | grep SSHSSH_AGENT_LAUNCHER=gnome-keyringSSH_AUTH_SOCK=/run/user/1000/keyring/ssh (I am user 1000)I have also tried to use the -n, -T, -t, and -t -t options for ssh with no noticeable difference.
SSH with Cron: RSA key not accepted
ubuntu;ssh;cron;key authentication
debug1: Offering RSA public key: /home/zach/.ssh/id_rsadebug3: send_pubkey_testdebug3: send packet: type 50debug2: we sent a publickey packet, wait for replydebug3: receive packet: type 60debug1: Server accepts key: pkalg ssh-rsa blen 279debug2: input_userauth_pk_ok: fp SHA256:jsePXa9FO8c9f0bVwdgvXMJQ2GyHVqz5spaO13EQ0/Mdebug3: sign_and_send_pubkey: RSA SHA256:jsePXa9FO8c9f0bVwdgvXMJQ2GyHVqz5spaO13EQ0/Mdebug1: read_passphrase: can't open /dev/tty: No such device or addressdebug2: no passphrase given, try next keyYour key is passphrase protected, but you probably didn't notice, because you are using gnome-keyring which takes care of that. So what are the possibilities:Use separate key, which is not encrypted for cron jobs, becuase you still don't have a reasonable and secure way how to provide passphrase in cron job. This is preferred.If you don't mind storing passphrase in plaintext, use sshpass:sshpass -p your_passhprase -vvv my_account@my_remote touch temp.tempOther possibility is to try to hijack the connection to your gnome-keyring (using SSH_AUTH_SOCK environment variable). But note that this might not work always (once you log out of your graphical session, the gnome-keyring will not be running anymore and you will see the failures again:SSH_AUTH_SOCK=/run/user/1000/keyring/ssh ssh -vvv my_account@my_remote touch temp.temp