Klaus Ramstöck - ECOS Technology
2025-May-07 08:32 UTC
Change in behaviour V9 ./. V10 intended?
V10 brings a change that is slightly annoying to me, I think it is related to this fix mentioned in the change log https://bugzilla.mindrot.org/show_bug.cgi?id=3477 Here is an example of the change in behaviour: # # Older system, using openssh portable V9: # ssh -V OpenSSH_9.8p1, OpenSSL 3.0.15 3 Sep 2024 # ssh user%1234567890 at 127.0.0.1 (user%1234567890 at 127.0.0.1) Password: # no expansion, %% is passed as is # ssh user%%1234567890 at 127.0.0.1 (user%%1234567890 at 127.0.0.1) Password: # # Current system, using V10: # ssh -V OpenSSH_10.0p2, OpenSSL 3.5.0 8 Apr 2025 # ssh user%1234567890 at 127.0.0.1 vdollar_percent_expand: unknown key %1 percent_dollar_expand: failed # % must be escaped as %% # ssh user%%1234567890 at 127.0.0.1 (user%1234567890 at 127.0.0.1) Password: User names follow a <user>%<id> pattern. Is this the intended behaviour? The section form the release notes ssh(1): allow %-token and environment variable expansion in the ssh_config User directive, with the exception of %r and %C which would be self-referential. bz#3477 suggests only the User directive should be affected. Thanks? Klaus Ramst?ck Entwickler ?
Seemingly Similar Threads
- Match/Include by environment variable unexpected behavior
- [Bug 3739] New: Match parsing requires space before '='
- [Bug 3736] New: sshd falls back to password prompt after PAM module returns a PAM_MAXTRIES.
- Entwickler Workshop Virtualisierung
- [Bug 3814] New: incorrect signature when ssh'ing to an AIX server (Big Endian) from amd64 (Little endian)