[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: libssh and screen prompts

Ok, I understand a little better. Libssh provide API's for this
(basicaly channel_read and channel_write). You will have to do the
matching by your own program using libssh's APIs (it's too specific for
libssh itself).


Barbara Knysz a écrit :
> This doesn't necessarily have to be about authentication. Basically I
> use the appearance of certain prompts to know if the previous command
> sent did what was expected. So I believe from your response below, the
> libssh will not provide that information?
> Thanks
> On Tue, Dec 8, 2009 at 9:45 AM, Aris Adamantiadis <aris@xxxxxxxxxxxx
> <mailto:aris@xxxxxxxxxxxx>> wrote:
>     Hello,
>     It depends what you're talking about.
>     If you need to authenticate to the server using SSH authentication
>     (password, keyboard-interactive, publickey, ...), this is integrated in
>     libssh and fully documented.
>     If your server automatically does a "fake" authentication, only to let
>     you enter your credentials to an other program running over the SSH
>     protocol (like some telnet-over-SSH appliances you can find in some
>     embedded devices), then the answer is no. Libssh does not inspect what's
>     travelling in the channels (and never will, because the standard tells
>     it's up to the application).
>     I hope I answered your question.
>     Regards,
>     Aris
>     Barbara Knysz a écrit :
>     > I have created a test program that sends a command, and then recieves
>     > the output.
>     > However, I also need to examine the screen prompt to identify
>     aspects of
>     > work flow, such as then dynamic discovery of the the necessity of an
>     > 'enable' password..
>     >
>     > Does libssh handle this?
>     > Thanks

libssh and screen promptsBarbara Knysz <bknysz@xxxxxxxxx>
Re: libssh and screen promptsAris Adamantiadis <aris@xxxxxxxxxxxx>
Archive administrator: postmaster@lists.cynapses.org