Bug 52455 - kio fish can't connect into a bsd system
Summary: kio fish can't connect into a bsd system
Status: RESOLVED DUPLICATE of bug 60083
Alias: None
Product: kio
Classification: Frameworks and Libraries
Component: fish (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Jörg Walter
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-12-31 14:51 UTC by Iuri Fiedoruk
Modified: 2003-07-09 22:54 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Iuri Fiedoruk 2002-12-31 14:51:18 UTC
Version:            (using KDE KDE 3.0.99)
Installed from:    Compiled From Sources
Compiler:          gcc 3.2 
OS:          Linux

After we changed out server to freebsd 4.3/OpenSSH_3.4p1 FreeBSD-20020702, SSH protocols 1.5/2.0, OpenSSL 0x0090607f, kio fish can't connect on it anymore.
When it should ask for password, it just keeps loading forever.
Comment 1 Jörg Walter 2003-03-21 10:38:37 UTC
Please provide additional details: Can you show a dump of "ssh the-offending-host" including all 
text up to the remote shell prompt? 
Also, are you using privilege separation on the server? It _should_ work with KDE-3.1's version, 
but I have not tested that myself. 
Comment 2 Iuri Fiedoruk 2003-03-21 17:33:01 UTC
There isn't much I can tell you, ssh direct just works, throught kio_fish it dosen't asks for 
password. 
 
A way I found for making it work was sending a gcc key on the server, so instead of asking me 
the password, the server asks me the password of the key. 
 
I don't know what "privilege separation" means, if you ellaborate a bit more, I can give it a try. 
 
Thanks. 
Comment 3 jcook 2003-07-09 18:44:51 UTC
Privilege escalation is the problem. We recently upgraded our dev box to FreeBSD
4.8 using sshd version OpenSSH_3.5p1 FreeBSD-20030201. I changed
UsePrivilegeSeparation to no and restarted sshd and can now use fish to access
the server from kde 3.1.2.
Comment 4 Lauri Watts 2003-07-09 22:54:11 UTC
It's not just privelege separation, we tested with various combinations with it on 
and off and saw inconclusive results. 
 
In any case,  the patch on the dupe does fix it for most people. 

*** This bug has been marked as a duplicate of 60083 ***