Comments on: Automating WordPress uploads using SSH

By: Jonathan Dingman

Jonathan Dingman — Thu, 13 Aug 2009 21:31:10 +0000

I made the update to the codex so it doesn’t show PRIVKEY anymore, but that it reflects the correct value of PRIKEY. I made the update because I saw your article and realized you were correct, that the codex had the wrong value.

Thanks for the heads up.

It’s tough to write a tutorial that fits every circumstance, so it’s great that people, like yourself, like spin-off tutorials so that other people can benefit from other people’s experiences.

By: weave

weave — Sun, 12 Jul 2009 03:08:06 +0000

Just read the Codex page has been corrected. Nice.

By: weave

weave — Thu, 28 May 2009 22:37:52 +0000

Woah, thanks. That’s much better! Had no idea that that was doable! Then in that case the host in FTP_HOST has to be localhost too.

I did have to change the from to localhost.localdomain due to this syslog error.

May 28 21:53:56 catzilla sshd[1316]: Authentication tried for weave with correct key but not from a permitted host (host=localhost.localdomain, ip=127.0.0.1).

Thanks!

By: Pat Hennessy

Pat Hennessy — Thu, 28 May 2009 21:07:09 +0000

You could also put from=”localhost”,no-port-forwarding,no-pty in your authorized keys file. It should go before ssh-rsa. That will ensure the private key can only be used locally. Although, chmod’ing the private key file open and shut as you need it couldn’t hurt either.