Hi Bhavya,
This has been discussed within the SRU Team, and we have decided that the impact
of this bug is not worth the risk in perusing a fix at this time.
The addition of a whitespace at the end of the command name has very low real
world impact, as it doesn't outright cause any issues, and any user generated
scripts can be fixed easily, in your case, by removal of explicit checks for
the substring, and to make it a little more flexible so it accepts the space.
This doesn't have anything to do with your SRU template and proposed debdiff,
they are perfectly fine and the backport of the patch is correct.
This all comes down to risk tolerance, and openssh is a special package because
it is installed on every single server install, and most desktop installs. If
a regression were to occur that prevents someone from remotely accessing their
systems, that could be quite bad.
This is not a permanent no, we can revisit in the future if you can demonstrate
sufficient real world impact.
If you have any questions, please let me know.
Thanks,
Matthew
** Changed in: openssh (Ubuntu Noble)
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2147690
Title:
SSH_ORIGINAL_COMMAND env variable has an extra white space at the end
of its value
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2147690/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
