Bug 502413 - konqueror should re-use sftp connections (prevent ip ban by CSF/LFD)
Summary: konqueror should re-use sftp connections (prevent ip ban by CSF/LFD)
Status: REPORTED
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: 24.04.80
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-04-04 15:29 UTC by Raphael Rosch
Modified: 2025-04-04 15:29 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Raphael Rosch 2025-04-04 15:29:59 UTC
Restoring a session with multiple sftp connections to the same host leads to an IP ban by CSF/LFD. 

This is due to the fact that apparently (probably?) an sftp connection on konqueror attempts a passwordless connection, and *then* it prompts for the password/passkey.. but registering that first one as a failed attempt, and if you have more sftp connections attempted than the server's limit (I think the default is 5) your ip gets banned. konqueror should therefore re-use the first established sftp connection (and only attempt one at a time) instead of trying a new one for each view. 

Another related issue is that this then often causes the kio_sftp socket used by konq to not work anymore, and the workaround I have found is to launch dolphin (which seems unaffected by the frozen kio socket) and attempt the sftp connection there, and then it "magically" works in konqueror. 

Killing the 

> /usr/libexec/kf5/kioslave5 /usr/lib64/qt5/plugins/kf5/kio/sftp.so sftp 

processes does not seem to work either. But I think I had luck once killing the 

> /usr/libexec/kf5/kiod5

process after killing all the sftp kioslave processes. But I'm not sure if it was due to special circumstances or what. In case that is useful information.