SSHShell not blocking

kgn · Post by **kgn** » Wed 08 Oct 2008 08:04

There seems to be a serious problem with the SSHshell component. I note that another user here has what looks like a similar problem.

I want to use the component in blocking mode - but the thing does not block correctly.

If I try something like
cp.connect
cp.writestring('some command')
cp.readstring()

...it does not work. All I EVER get back is nothing at all.

I tried an idea mentioned here in the forum and added a 1 second timer delay between the write and the read. And that kind of works. I do at least get something back, although I am not too sure if the response is fully correct.

From this it seems that the component is not blocking, which is rather important for my application. Putting in a random time delay is not a fix - it is silly. What if there is a slow connection and it takes 2xtimedelay to get a response? No, some random time delay is not an answer.

Is this a bug? Or is it by design? ie do I have to get a response back in some other way?

It also seems that the response returns the correct response, but is then followed by a lot of garbage characters.

I am looking at buying this component. I have tried the competition, and it returns the correct (ie no garbage characters) response.

Any ideas?

Dimon · Post by **Dimon** » Fri 10 Oct 2008 12:14

This problem was discussed in the following topics:
http://devart.com/forums/viewtopic.php?t=12954

We are investigating this problem to improve work of TScSSHShell. As soon as we solve the problem we will let you know.

ib · Post by ib » Mon 13 Oct 2008 15:55

This problem is imho a terminal-settings problem.
Dealing with echo-ing the command(s) , the remote-prompt and the control-characters for some kind of virtual terminal ( line breaks etc ) would hugely enhance the usability of the shell component.

ajoschi · Post by **ajoschi** » Thu 28 Oct 2010 11:15

Hi.

I wonder if there is any progress in this issue?

I am using Version V2.60 of SecureBrigde and it seems to occur there, too.
Is this issue fixed in V3.0?

Best regards,
Ajoschi

Dimon · Post by **Dimon** » Mon 01 Nov 2010 17:07

We still haven't fixed the problem, because different SSH servers and Operating Systems use different ways to know echoing of a command, and thus there is no single solution.