** Changed in: openssh
Status: Unknown => New
--
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/1938144
Title:
monitor_read: unpermitted request 48 on server while
That PR is still pending review, no movements there unfortunately.
--
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/1938144
Title:
monitor_read: unpermitted request 48 on
The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.
** Changed in: openssh (Ubuntu Hirsute)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh
Thanks, Niklas!
Utkarsh, Paride: Since this seems to be a low priority issue, I am
waiting to see if we get a couple more eyes into
https://github.com/openssh-gsskex/openssh-gsskex/pull/21 before adding
this one in our delta (this could even go into Debian first and then we
can start preparing
Wt, thanks for confirming Niklas. Athos, would you mind prepping
an MP for this, et al? TIA, good sir! \o/
--
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/1938144
** Also affects: openssh (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: openssh (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: openssh (Ubuntu Focal)
Status: New => Triaged
** Changed in: openssh (Ubuntu Hirsute)
Status:
Thanks for building the packages for focal.
I can confirm that this fixes the problem for me!
--
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/1938144
Title:
monitor_read:
Hi Niklas,
I just pushed the focal patched package to that same PPA. Note that they
are only available for x86_64 and i386. Let me know if you need it for
any other platforms.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Thanks for the PPA! I currently don't have an impish system at hand,
would it be possible to build it for focal as well?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
Dmitry Belyavskiy proposed a patch for this issue at
https://github.com/openssh-gsskex/openssh-gsskex/pull/21.
I created a PPA with the proposed fix at https://launchpad.net/~athos-
ribeiro/+archive/ubuntu/openssh-gssapi-fix/+packages and I can confirm
it does fix the reproducer proposed in this
** Also affects: openssh via
https://github.com/openssh-gsskex/openssh-gsskex/issues/20
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.
The issue is reproducible in the latest published versions of openssh
carrying the patches in https://github.com/openssh-gsskex/openssh-gsskex
for Ubuntu (impish), Debian (unstable), and Fedora (rawhide).
I filed a bug report in https://github.com/openssh-gsskex/openssh-
gsskex/issues/20 to make
Hi Niklas,
Thanks for putting in the effort into finding a reproducer for the
reported issue.
I could indeed reproduce the issue you have been experiencing. I am
attaching a couple scripts to aid others to reproduce the bug (this
includes a README file with further instructions).
Interestingly,
Ok, I managed to reproduces this in a clean "ubuntu:latest" docker
container. Steps to reproduce are below. During testing, I noticed that
I aliased "ssh" to "ssh -K -X", and that "-K" (or equivalently "-o
GSSAPIAuthentication=yes") is crucial. This changes the problematic SSH
client command to
Thanks Sergio for trying to reproduce this! I'm a bit puzzled, why the
bug did not trigger in your case. I'll try to reproduce this in a clean
VM as well now. One important thing might be that I tried to login as
"root", for which I did not have a Kerberos-Ticket, so a "permission
denied" would be
So, I give this a try and attempted to reproduce the issue.
I set up a VM acting as the KDC, and configured sshd in it with the
following options:
GSSAPIAuthentication yes
GSSAPICleanupCredentials yes
GSSAPIKeyExchange yes
I then configured an LXD container to act as the krb5 client. I created
Hello Niklas!
You're welcome again. Thanks for adding more information... Good to know
we can put Ansible apart from this.
Anyway, we would need more information about the Kerberos configuration
you mentioned before as you noticed it is involved because we don't have
the complete picture to
Hello Athos,
thanks for looking into this!
This is reproducible without Ansible, that was just use-case that
brought up the issue. I've further narrowed it down to the following
setup:
Server:
/usr/sbin/sshd -d -p -f /dev/null -o GSSAPIKeyExchange=yes -o
GSSAPIAuthentication=yes
Client:
Hello Niklas,
Thank you for taking the time to file a bug report.
While the symptoms experienced here seem similar to the ones reported in
https://bugzilla.redhat.com/show_bug.cgi?id=1162620, the patch that
fixed the latter is present in the version of the package for which you
reported the
19 matches
Mail list logo
