Message: previous - next
Month: April 2012

Re: [trinity-devel] ALMOST (not reading .ssh/config) [was Re: [trinity-devel] sftp-kio - still fails in R14 - Any progress? (log captured - may help?)]

From: "Timothy Pearson" <kb9vqf@...>
Date: Mon, 23 Apr 2012 19:00:32 -0500
> On 04/23/2012 03:26 PM, David C. Rankin wrote:
>> On 04/23/2012 02:44 AM, Timothy Pearson wrote:
>>> Fixed (hacked around) in GIT hash e72f492.  Basically select() no
>>> longer
>>> works on newer systems (could be due to a malfunction of some kind, but
>>> it
>>> doesn't really matter), so instead of busywaiting on select(), newer
>>> systems will busywait on read().
>>> Tim
>> WOHOO!!! Will test and report back. Sorry, I've been swamped the past
>> couple of
>> days. I'll definitely try and build/test tonight!
> Tim,
>   I built tdelibs and tdebase and tested sftp. There is GOOD news and BAD
> news.
> The good new - I can connect with sftp!! The bad news - the kio is not
> reading
> host/port information from ~/.ssh/config. This requires that you manually
> specify a port (if not 22) where sftp:// used to read this information
> from the
> HOST/PORT information contained in ~/.ssh/config. Eg:
> Host arete
> Port 6629
> Host fax
> Port 6631
>   I don't know what reads this file, but it is read currently when fish://
> is
> invoked and it was previously read by sftp:// before this bug appeared.
> Any idea
> where this occurs?

I would have expected ssh to read this on its own, but now that you
mention it I do remember a port 22 parameter being passed to ssh when
invoked by the sftp kioslave.  I would look in ksshprocess.cpp and see if
the sftp kioslave was hardcoded to port 22 for some reason.