[Touch-packages] [Bug 1771011] Re: Doesn't accept environment variable with underscore in its name in AuthorizedKeysFile

2018-08-03 Thread  Christian Ehrhardt 
one test needed trigger with new openmpi, done now -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1771011 Title: Doesn't accept environment variable with underscore in

[Touch-packages] [Bug 1771011] Re: Doesn't accept environment variable with underscore in its name in AuthorizedKeysFile

2018-08-03 Thread Launchpad Bug Tracker
This bug was fixed in the package openssh - 1:7.7p1-3 --- openssh (1:7.7p1-3) unstable; urgency=medium [ Colin Watson ] * Adjust git-dpm tagging configuration. * Remove no-longer-used Lintian overrides from openssh-server and ssh. * Add Documentation keys to

[Touch-packages] [Bug 1771011] Re: Doesn't accept environment variable with underscore in its name in AuthorizedKeysFile

2018-08-02 Thread  Christian Ehrhardt 
Released with 1:7.7p1-3 since a while - handing in cosmic-proposed. None of the issues seem related to me, for now I retriggered the tests to run with the new versions and hopefully resolve by itself. -- You received this bug notification because you are a member of Ubuntu Touch seeded

[Touch-packages] [Bug 1771011] Re: Doesn't accept environment variable with underscore in its name in AuthorizedKeysFile

2018-07-16 Thread  Christian Ehrhardt 
This was uploaded to Debian and is in Cosmic-Proposed. The Changelog will auto-close this once migrated. ** Changed in: openssh (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to

[Touch-packages] [Bug 1771011] Re: Doesn't accept environment variable with underscore in its name in AuthorizedKeysFile

2018-06-28 Thread  Christian Ehrhardt 
Since Cosmic is still open and auto-syncing I prepared that as fix [1] for Debian to sync it in. [1]: https://salsa.debian.org/ssh-team/openssh/merge_requests/2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in

[Touch-packages] [Bug 1771011] Re: Doesn't accept environment variable with underscore in its name in AuthorizedKeysFile

2018-06-27 Thread Andreas Hasenack
** Also affects: openssh via https://bugzilla.mindrot.org/show_bug.cgi?id=2851 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu.

[Touch-packages] [Bug 1771011] Re: Doesn't accept environment variable with underscore in its name in AuthorizedKeysFile

2018-06-26 Thread  Christian Ehrhardt 
Will be in 7.7p2 per (next stable release) https://github.com/openssh/openssh-portable/commit/484fc023af92ee30bc99eb9798235a00e8f929cc Upstream Bug: https://bugzilla.mindrot.org/show_bug.cgi?id=2851 Seems to be broken in 7.7 only so no need to SRU. ** Bug watch added: OpenSSH Portable

[Touch-packages] [Bug 1771011] Re: Doesn't accept environment variable with underscore in its name in AuthorizedKeysFile

2018-06-22 Thread  Christian Ehrhardt 
** Tags added: server-next -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1771011 Title: Doesn't accept environment variable with underscore in its name in

[Touch-packages] [Bug 1771011] Re: Doesn't accept environment variable with underscore in its name in AuthorizedKeysFile

2018-06-21 Thread Ubuntu Foundations Team Bug Bot
The attachment "0001-permit-underscore-in-user-environment.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a

[Touch-packages] [Bug 1771011] Re: Doesn't accept environment variable with underscore in its name in AuthorizedKeysFile

2018-06-21 Thread Dan Fuhry
Patch submitted upstream: https://lists.mindrot.org/pipermail/openssh-unix- dev/2018-June/036990.html The patch in my ML post above applies to the OpenBSD version of OpenSSH. I've attached another version that applies to the portable release 7.7p1 here. ** Patch added:

[Touch-packages] [Bug 1771011] Re: Doesn't accept environment variable with underscore in its name in AuthorizedKeysFile

2018-05-25 Thread Andreas Hasenack
** Changed in: openssh (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1771011 Title: Doesn't accept environment variable with

[Touch-packages] [Bug 1771011] Re: Doesn't accept environment variable with underscore in its name in AuthorizedKeysFile

2018-05-16 Thread Joshua Powers
This did not reproduce in xenial or bionic, so that narrows it down to a change between 7.7p1-2 (cosmic) and 7.6p1-4 (bionic) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu.

[Touch-packages] [Bug 1771011] Re: Doesn't accept environment variable with underscore in its name in AuthorizedKeysFile

2018-05-16 Thread Joshua Powers
Confirmed this in a Cosmic container this morning. It appears the version in cosmic has an issue with the underscore. Steps to reproduce: 1. lxc launch ubuntu-daily:c c 2. lxc exec c bash 3. echo "PermitUserEnvironment yes" > /etc/ssh/sshd_config 4. ssh-import-id 5. add environment="FOO_BAR=1"

[Touch-packages] [Bug 1771011] Re: Doesn't accept environment variable with underscore in its name in AuthorizedKeysFile

2018-05-14 Thread Joshua Powers
Hi, thanks for taking the time to file a bug. Based on that last message from SSH it makes me wonder if the syntax you have is correct. 1) Can you confirm PermitUserEnvironment is set to yes in your sshd_config? 2) Can you provide more details of the line in question in your authorized keys