Loading Profile...
Mismatching host keys crashes SftpDrive?
We recently recreated one of our servers previously BSD, now Fedora. The IP and logins are all the same, but the host keys have changed. Now, when trying to connect SftpDrive, it just locks up during the connection process. I'm assuming it's due to invalid host keys, but there's no information. Where are the keys stored for SftpDrive and how would I go about deleting an entry? We tried deleting and re-creating the login account, but that didn't help.
I’m frustrated
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company has a solution in progress.
-
Inappropriate?chrisweiss -
This definitely doesn't happen in the general case, sorry! I'll look into it and see if a bug creeped in somewhere in an odd scenario.
In the meantime you can find the hostkeys in HKEY_CURRENT_USER\Software\SftpDrive
Sorry about this.
-Jeff -
Inappropriate?Okay, looks like we were barking up the wrong tree. Deleted the HOST 000 entry and we're still locking up. Blast. That's the only thing that's changed.
I’m sad
-
Inappropriate?Okay, totally the wrong tree - but we did expose an issue with SftpDrive. Turns out the new machine had an echo statement in .cshrc, so it'd spit out text as soon as you logged in. This confuses SftpDrive something fierce and it locked up.
FWIW, we discovered this is a common problem - Filezilla throws an "Out of memory error", which helped track down the source of the issue.
I’m sorry for the misleading start, glad it works for us, sad that there's still a crash bug.
-
Inappropriate?Glad to see you found the fix
just a general echo statement? I'll do some debugging, should be an easy fix -
Inappropriate?Just wondering if this had been fixed? It looks like 1.7.9 is still the latest version and we ran into this issue again (redoing the developer's image again). These are the two files that are called at login. Removing the echo statements makes things work properly.
# /etc/csh.login
# System wide environment and startup programs, for login setup
#echo running .login.personal
if ($?PATH) then
if ( "${path}" !~ */usr/X11R6/bin* ) then
setenv PATH "${PATH}:/usr/X11R6/bin"
endif
else
if ( $uid == 0 ) then
setenv PATH "/sbin:/usr/sbin:/usr/local/sbin:/bin:/usr/bin:/usr/ local/bin:/usr/X11R6/bin"
else
setenv PATH "/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin"
endif
endif
setenv HOSTNAME `/bin/hostname`
set history=1000
if ( ! -f $HOME/.inputrc ) then
setenv INPUTRC /etc/inputrc
endif
alias md "make debug"
and
# /etc/cshrc
#
# csh configuration for all shell invocations.
# By default, we want this to get set.
# Even for non-interactive, non-login shells.
umask 022
# echo running .cshrc.personal
if ($?prompt) then
if ($?tcsh) then
set promptchars='$#'
set prompt=\[$user'@%m %c]%# '
else
set prompt=\[$user@`hostname -s`\]\$\
endif
endif
if ( $?tcsh ) then
bindkey "^[[3~" delete-char
endif
setenv MAIL "/var/spool/mail/$USER"
limit coredumpsize 0
if ( -d /etc/profile.d ) then
set nonomatch
foreach i ( /etc/profile.d/*.csh )
if ( -r $i ) then
source $i
endif
end
unset i nonomatch
endif
setenv EDITOR vi
setenv PATH ./:${PATH}:/usr/local/eclipse:/sbin
setenv MENGINE_PATH /home/euming/expresso/Proj/MEngine/
I’m concerned
-
Inappropriate?Chris -
The echo is a known issue that we've got on file. I'll try and allocate some time to filter it out internally, but for now, I'd comment it out.
-Jeff
EMPLOYEE
