Rob Sanders

Our libcli based application (running on Linux) is set as the 'shell' of our users, so it starts running as they log in, whether from Console or ssh.

Our app is basically doing this. It is assigned as the user shell so it is invoked on login. Additionally we’re explicitly forking so the ‘parent’ thread intercepts single characters...

I do local testing with LD=LIBRARY_PATH=. ./clitest

Libcli was written assuming telnet style I/O, which I believe is different than if you were simply reading stdin or a socket (and may vary OS to OS to boot)....

Unable to reproduce on a CentOS 7.5 box. Started clitest, then did 'telnet localhost 8000', was prompted for user/password. Using credentials listed in readme was able to log in.

Concur on Jere's suggestion, if only to ensure anyone using the existing code will continue to work. Will merge to the staging-1.10.8 branch (with Jere's suggestions), with slight change: #define...

Yep, going to do that as I start making direct changes to the branch. I've been working on a change to the OPTIONAL_FLAG so it directly supports validators/completors. We have...

Hi @illukin , Pagination support is still a long way off, but tab completors for options and arguments are already in place. Look at the clitest.c code for some example....

Yes. Been making some improvements on our side for processing sigints as well as sniffing the responses to our commands before doing cli_prints() back to the users. For example, if...

Those changes are outside of libcli code.