Thanks for the tip, I wasn't expecting that feature to be part of ssh-keygen.
When SSH clients first connect they ask the server for a pseudo terminal (PTY), to enable terminal colors, clearing the screen etc. In this case the SSH server declines that request because it simply wants to send back…
Thanks for the link! I added it to the article.
Glad you liked it! I definitely echo the sentiment of wanting to use these sorts of power-user-only tools. But I think Moxie's recent post, They Live[1], does an excellent job of explaining why we shouldn't accept that…
Good point about the <token>@<host> format, I like it much better too. You're right about tying tokens to host names, that would work. But you'd have to justify whether the extra complexity of multiple web servers…
Thank you! I was looking for that option while writing the section on throwaway keys. I'll have to test it out.
Thanks for the tip, I wasn't expecting that feature to be part of ssh-keygen.
When SSH clients first connect they ask the server for a pseudo terminal (PTY), to enable terminal colors, clearing the screen etc. In this case the SSH server declines that request because it simply wants to send back…
Thanks for the link! I added it to the article.
Glad you liked it! I definitely echo the sentiment of wanting to use these sorts of power-user-only tools. But I think Moxie's recent post, They Live[1], does an excellent job of explaining why we shouldn't accept that…
Good point about the <token>@<host> format, I like it much better too. You're right about tying tokens to host names, that would work. But you'd have to justify whether the extra complexity of multiple web servers…
Thank you! I was looking for that option while writing the section on throwaway keys. I'll have to test it out.