News for hackers. Stuff that matters.
Re:OpenSSH 6.5 Released by jaryd on Thursday January 30, 2014 @10:13PM (#7155022)
The following two things are highlights for me:

  * ssh(1): Add a ssh_config(5) "Match" keyword that allows
   conditional configuration to be applied by matching on hostname,
   user and result of arbitrary commands.

 * ssh(1): Add support for client-side hostname canonicalisation
   using a set of DNS suffixes and rules in ssh_config(5). This
   allows unqualified names to be canonicalised to fully-qualified
   domain names to eliminate ambiguity when looking up keys in
   known_hosts or checking host certificate names.
Re:OpenSSH 6.5 Released by stormbrew on Thursday January 30, 2014 @10:41PM (#7155108)
Both great things. I'm pretty excited about elliptic curve keys and the ability to have ProxyCommand-like ProxyUseFDPass return an fd instead of act as an long-lived intermediary, personally.

A lot to like in this.

Re:OpenSSH 6.5 Released by nodata on Friday January 31, 2014 @03:08AM (#7155841)
The Match keyword is great, but the syntax of "and continue reading until the end of the file" is a pain. They should add an EndMatch keyboard to close the block, or force indentation or something.
Re:OpenSSH 6.5 Released by djmdjm on Thursday January 30, 2014 @11:09PM (#7155189)
More details on the hostname canonicalisation here: http://blog.djm.net.au/2014/01/hostname-canonicalisation-in-...
Re:OpenSSH 6.5 Released by newman314 on Friday January 31, 2014 @03:08PM (#7158871)
I would still like to see an easy way to switch between a gateway ssh host and going direct depending on location/IP.

If I'm home, I want to be able to ssh to the gateway machine automatically and when I'm at work, go direct.

Obviously, this can be fixed with a shell script but it's hacky.

Re:OpenSSH 6.5 Released by stormbrew on Friday January 31, 2014 @03:39PM (#7159051)
The Match keyword does allow you to configure based on your local address, so on first glance it would seem like it would allow you to do this, but for some reason ProxyCommand is not on the list of whitelisted keywords acceptable in a Match block. :/ That's really a shame.