How are SFTP fingerprints handled?

May 20, 2008
Syracuse, NY, USA
SFTP fingerprints seem to be remembered between sessions, but only for a while, and not across various versions of TCC. How are they handled?


Staff member
May 14, 2008
TCC shows me this:
v:\> dir s
The server provided the following fingerprint:

Would you like to continue? (Y/N)?

That's correct, but that's not what you originally asked.

The ipworks ssh class passes the fingerprint when the class connects. If you accept it, it gets saved to your .INI file (server + fingerprint). (But it is never deleted.) When you reconnect, TCC looks to see if there's a match in the .INI file; if so it's accepted, if not you get the prompt.
May 20, 2008
Syracuse, NY, USA
I must have been doing two different things when I noticed the same version of TCC asking twice about the fingerprint. Now I see that it's actually in the INI file twice and I'm not asked about it any longer.
v:\> grep 48:99 %_ininame
Apr 20, 2017
We got a (reasonably) neat solution to avoiding an interactive prompt in an unattended BTM file (for instance when run from Task Scheduler):

copy s mydestination
INPUT /c /W0

The Keystack puts the Y response into the buffer just in case the copy command is to a new site, and it pops up the 'fingerprint - do you want to continue' message.
That means that the copy command continues regardless
The Input then flushes the Y out of the buffer (/c) if the prompt did NOT appear, or waits 0 seconds for new input if the 'Y' was used up and there is nothing to clear.

However, it would be nice if TCC was able to detect that it was not running intereactively (ie from a service or scheduled task), and NOT put out a prompt that will never get acknowledged. (We are using TCC20 - this may already be fixed in a newer version, but I have no idea).
Thread starter Similar threads Forum Replies Date
M Support 3
P Support 7
V Support 2
V Support 17
V Support 7