Still no activity in the upstream issue, however I think OpenSSH 8.9
offers a mechanism that can help avoiding hitting MaxAuthTries in some
cases: "destination constraints", see documentation for -h in ssh-
add(1). AIUI constraining should limit the number of keys tried against
a given host,
I have again updated the upstream case, but if they are not willing/convinced
this won't happen as Ubuntu delta or we will have too many small scratches by
being slightly different on this.
So anyone affected/requesting this please chime in on the upstream bug.
Dropping server-next as it can't
@RCJ - can you help by testing the PPA that I provided and chime in on
the upstream discussion to get things moving a bit better - just to show
that people would really care about this feature.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: openssh (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872145
Title:
explicit key offered after all agent keys, auth can fail before
explicit
Filed upstream for a discussion at
https://bugzilla.mindrot.org/show_bug.cgi?id=3153 and linked in the bug
here.
** Bug watch added: OpenSSH Portable Bugzilla #3153
https://bugzilla.mindrot.org/show_bug.cgi?id=3153
** Also affects: openssh via
** Also affects: openssh (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=203700
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872145
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872145
Title:
explicit key offered after all agent keys, auth can fail before
explicit key used
To manage notifications about
I have a PPA at:
https://launchpad.net/~paelzer/+archive/ubuntu/bug-872145-ssh-prefer-user-configured-key
I have tested and the "IdentityFile" directive in /etc/ssh/ssh_config
does not count as "user defined". I'd have preferred if that would count
as well, but for now at least preferring the
Without checking deeper I'm unsure if keys listed in e.g.
/etc/ssh/ssh_config are considered as "userprovided" but lets give this
a shot.
Gladly the debug already contains "explicit" if id->userprovided is
true.
I usually get:
debug1: Will attempt key: /home/paelzer/.ssh/id_rsa RSA ... agent
There are plenty of workarounds and the internet is full of this issue.
-
https://serverfault.com/questions/36291/how-to-recover-from-too-many-authentication-failures-for-user-root
- https://www.tecmint.com/fix-ssh-too-many-authentication-failures-error/
-
** Tags added: id-5e5e7f1874c52821423d5bfd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872145
Title:
explicit key offered after all agent keys, auth can fail before
explicit key used
To
** Tags added: server-next
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872145
Title:
explicit key offered after all agent keys, auth can fail before
explicit key used
To manage notifications
It also prefers configured key files over smart cards, causing similar
issues. Luckily there is a work around for that by adding /dev/null as
an identify file in the config, but that's super ugly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Summary changed:
- explicit key offered after all agent keys, auth fails before explicit key used
+ explicit key offered after all agent keys, auth can fail before explicit key
used
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
14 matches
Mail list logo
