Powered by:

ohost

Bulgarian mirror 10 Gbps

Protocols: HTTP, HTTPS, FTP, RSYNC
Contact Us: support@ohost.bg

PuTTY bug gssapi-kfw-crash

PuTTY bug gssapi-kfw-crash

This is a mirror. Follow this link to find the primary PuTTY web site.

Home | FAQ | Feedback | Licence | Updates | Mirrors | Keys | Links | Team
Download: Stable · Snapshot | Docs | Changes | Wishlist

summary: GSSAPI with MIT Kerberos-for-Windows or third-party DLL crashes
class: bug: This is clearly an actual problem we want fixed.
difficulty: fun: Just needs tuits, and not many of them.
priority: high: This should be fixed in the next release.
absent-in: 0.70
present-in: d515e4f1a34b4122195b113ba42ad1c4d2de9085 0.71
fixed-in: 142427afaedd6bbf5a0f409d993c67b7b4b08b75 (0.72)

Attempting to use GSSAPI authentication with MIT Kerberos-for-Windows, or a third-party GSSAPI Windows DLL, would cause PuTTY to crash early in an SSH connection.

Since GSSAPI authentication and key exchange are enabled by default, the mere presence of MIT Kerberos is usually sufficient to cause affected versions of PuTTY to crash.

This bug can be worked around by disabling both of the "Attempt GSSAPI" options on the Connection / SSH / Auth / GSSAPI tab in the PuTTY configuration.

(Whenever someone has complained to us about a crash at the start of an SSH session with 0.71, it has almost always turned out to be this. You can easily have a GSSAPI provider on your machine without knowing it, for instance if it was installed by your IT department. So if you're seeing a crash, it's worth trying the workaround, even if you're not sure it applies to you.)


If you want to comment on this web site, see the Feedback page.
Audit trail for this bug.
(last revision of this bug record was at 2019-05-26 11:53:53 +0100)
Mirror hosted by: OHOST LLC