Downloadempty - run applications under pseudo-terminal (PTY) sessions to dialogue with interactive programs. Replace TCL/Expect with a simple tool and use your favorite shell (sh, bash, csh, tcsh, ksh, zsh, etc)
License
BSD LicenseFollow empty
Other Useful Business Software
Define and Deliver Comprehensive Cybersecurity Services. Security threats continue to grow, and your clients are most likely at risk. Small- to medium-sized businesses (SMBs) are targeted by 64% of all cyberattacks, and 62% of them admit lacking in-house expertise to deal with security issues. Now technology solution providers (TSPs) are a prime target. Enter ConnectWise Cybersecurity Management (formerly ConnectWise Fortify) — the advanced cybersecurity solution you need to deliver the managed detection and response protection your clients require. Whether you’re talking to prospects or clients, we provide you with the right insights and data to support your cybersecurity conversation. From client-facing reports to technical guidance, we reduce the noise by guiding you through what’s really needed to demonstrate the value of enhanced strategy.
Rate This Project
Login To Rate This Project
User Reviews
-
Using empty to run ssh it echoes strings sent to remote back, example with empty -s ... this happens only when connecting as root user. and after successfully logged in. I did a brief ps for ssh processes and noticed that when connecting as root sshd dosen't open a [priv] instace of sshd for root user instead if runs directly under the main one and opens another one that has pty attached? it's output sent to remote host bounced back as input from remote host in addition to any output from remote host, instead of the normal behavior would be just output from remote host and only when connecting as root empty forks and runs ssh under a pty then uses two fifos to communicate with ssh process the in fifo sees anything I send out the out fifo in addition to the output from the commands i sent via the out fifo I think it's something to do of how sshd behaves when a root user connects something with the sockets or ptys don't know in addition of how empty captures the remote output :/
-
Thanks for good program!
-
This is just what many people need for their developments on a variety of blog about psedo terminal. I still don't know if this will help me with my problem however I found the man page clear and the examples even better to help me on my way. "Empty" is a little poor with error messages. If an "empty" command fails for some reason it just stops with no informative message of why the command failed.