RequestTTY option is not respected when declared in .ssh/config

Thank you for taking the time to report this bug and helping to make Ubuntu better.

I have been able to reproduce this on 12.10 (openssh-server 1:6.0p1-3ubuntu1). My gut feeling is that there is some kind of catch that we're missing but I have been unable to find anything. So far it does seem like a bug to me.

For a proper fix, the next step is to identify whether this bug is present in the upstream project, introduced in the Debian packaging or introduced in Ubuntu's modifications. If Ubuntu hasn't introduced the problem, we should get a bug filed in the appropriate bug tracker. Are you able to help with this, please?

This should probably be Confirmed rather than Triaged since we don't know what we need to do to fix this yet.

I did the following test, compiling the source code distributed on openssh.org:

openssh-6.0p1 : bug is present
openssh-6.1p1 : bug has been corrected, and contains the following Changelog

   - <email address hidden> 2012/07/06 01:47:38
     [ssh.c]
     move setting of tty_flag to after config parsing so RequestTTY options
     are correctly picked up. bz#1995 patch from przemoc AT gmail.com;
     ok dtucker@

Can the openssh package be upgraded to 6.1p1 on ubuntu 12.10 ?

I backported the official patch, please find it attached.

source:
http://anoncvs.mindrot.org/index.cgi/openssh/ssh.c?r1=1.365;r2=1.366&view=patch

The attachment "request-tty.patch" of this bug report has been identified as being a patch. The ubuntu-reviewers team has been subscribed to the bug report so that they can review the patch. In the event that this is in fact not a patch you can resolve this situation by removing the tag 'patch' from the bug report and editing the attachment so that it is not flagged as a patch. Additionally, if you are member of the ubuntu-reviewers team please also unsubscribe the team from this bug report.

[This is an automated message performed by a Launchpad user owned by Brian Murray. Please contact him regarding any issues with the action taken in this bug report.]