It makes a difference for me, but CanonicalizeHostname has to be in the
right part of the file (not inside an inapplicable Host block; note that
indentation doesn't actually matter). Perhaps I could see your whole
.ssh/config?
--
You received this bug notification because you are a member of
Ah, thanks! I indeed had it after a Host block with indentation /
paragraph, so I was misled in thinking of them as actual paragraphs.
Putting CanonicalizeHostname at the top of the file indeed works.
So it seems this was a deliberate change, or just accidentally happened
to work before. So I
** Description changed:
My ~/.ssh/config has
Host *.canonical.com
- User pitti
+ User pitti
and some convenience aliases as the actual host names change from time
to time:
Host cdimage
- HostName nusakan.canonical.com
+ HostName nusakan.canonical.com
Host
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: openssh (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
CanonicalizeHostname yes does not make any difference. Also, that part
actually seems to work fine (ssh langpack correctly resolves to
macquarie.canonical.com), it's the User from the previous Host * match
which isn't applied.
--
You received this bug notification because you are a member of
Andy pointed out Match; I haven't heard of/used it before, but doing
Match Host *.canonical.com
User pitti
gives exactly the same behaviour.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
I think this was deliberate upstream, probably this:
- ssh(1): Tweak config re-parsing with host canonicalisation - make the
second pass through the config files always run when host name
canonicalisation is enabled (and not whenever the host name changes)
In fact this was not
