Hi! Glad you like it; I did not know anybody had downloaded it :-) I cannot see what is wrong from your screenshot, but I will find a Mac and test it within a few weeks, and then get back to you :-)
Hi again, I have tried Opera now. Unfortunately it seems like the keyboard events are not working as expected. It is weird that Opera is the only browser with this behavior. If you consider fixing this I will be happy to update the distribution, otherwise I will probably fix it in the next version.
Hi, this is the perfect PHP/JS shell i’ve never found on the web. Complete, fun, useflull and based on Mootools (i’ma Mootools addicted :D )
I ‘ve implemented your shell in my free Open Source PHP Framework, and i’ve builded a multi theme plug in
Hi, I am glad you like it. You can post links here or email me: tmi at 5p, then I will share it on this site. I would like to see your plug in and your project :-)
I’m having trouble with vi/vim and ssh though; two important tools…
I have discovered that it doesn’t give me a real terminal:
$ top
TERM environment variable not set.
Fair enough. Worse, though, is that if I try to launch vim (from vim-gtk), the prompt just disappears and I can’t seem to get it back. Refreshing the browser page also doesn’t work. I have to restart apache. Which is only possible if I have a command line to the server. A chicken-and-egg situation.
I also would like to be able to use ssh to get from that server to another. But:
I’m not sure why that is. If I try this from a real terminal, it works fine.
> sudo -H -u www-data sh
server@www-data:~/path> ssh -l pvm otherserver
The authenticity of host 'otherserver (172.22.216.60)' can't be established.
RSA key fingerprint is (hidden).
Are you sure you want to continue connecting (yes/no)?
Hi, you are right ;-) TinyShell is not a real terminal, it does not support (n)curses programs, like top, vi, vim, etc. But you can use the plugin called tiny to edit files. Regarding SSH and top, unfortunately you will have to make a new plugin to support this. But if you have access to do this already, why don’t you use SSH directly instead of TinyShell? TinyShell is more ment to upload to FTP servers, where one does not have shell access. You should be able to call $apache restart though, but it requires that PHP has the right access to perform the command.
Hi, I understand and accept that I can’t use vi or top or whatever. That they won’t work. But TinyShell should survive if I by mistake try to use them anyway. I should be able to get my prompt back somehow. The problem is that I if I by mistake type “vi file” I’m toast. I cannot CTRL-C, or reload the browser or anything. I need to restart the web server (by some other means) to get anything working again. That means I cannot rely on it. If TinyShell access is all I have, “vi file” means I loose connection to the server forever. A truck roll is required.
Here in my debug environment I do have normal terminal access. But once we’ve gone live, I won’t have that. Only HTTP access to serverA. For some reason that I don’t understand it isn’t possible from a TinyShell on serverA to ssh to serverB. Once live I won’t have terminal access to any of them – only TinyShell access. And its a shame I won’t be able to get anywhere from serverA via SSH, don’t you think?
I never realized that PHP would actually wait forever for the command to execute and then also cause the web server to hang. I made a few tests, and it seems that system calls are not affected by the PHP max_execution_time/set_time_limit functions. Actually I also thought that web servers like Apache was configured by default to kill the PHP process after an amount of time, but I see that this is not always the case. But for now I suggest that you open sys.php in the plugin folder and either:
1. Create a black-list of unsupported commands you type by mistake.
2. Alter the shell_exec command, such that output is piped into a file and force a new process by adding an ampersand (&) in the end all commands (where it now already redirects the error stream to standard out). Then cat or tail this file for output after each system call. Problem is that you need to kill all the open process at some time if the do not terminate, but you will probably figure out a way to do this, or maybe do it when you have physical access to the server.
3. Modify the sys plugin to use proc_open instead of shell_exec, in order to gain control over the process that is started.
I think I will look at implementing the last solution in the near feature, and if you do, please share. Thanks for bringing up the problem :-)
Regarding SSH, you might want to copy the sys plugin to an ssh plugin and have a look at this: http://www.php.net/manual/en/function.ssh2-exec.php Unfortunately I do not have think most users have a need to create an SSH connection from the web server to another server through TinyShell, or even have enabled the requirements in PHP to do so, so I have not considered making such a plugin. And again, if you feel like doing some development on TinyShell, please tell me ;-)
Hi,
I use TinyShell. Nice software. :-)
It works without problems in Firefox and Safari. But when I use Opera (10.63) on Mac OS X 10.5.8, I cannot login. See following Screenshot.
http://dl.dropbox.com/u/61444/temp/Bild%202.png
Can someone help me please?
Regards
Ralph
Hi! Glad you like it; I did not know anybody had downloaded it :-) I cannot see what is wrong from your screenshot, but I will find a Mac and test it within a few weeks, and then get back to you :-)
Hi again, I have tried Opera now. Unfortunately it seems like the keyboard events are not working as expected. It is weird that Opera is the only browser with this behavior. If you consider fixing this I will be happy to update the distribution, otherwise I will probably fix it in the next version.
Best regards
Hi, this is the perfect PHP/JS shell i’ve never found on the web. Complete, fun, useflull and based on Mootools (i’ma Mootools addicted :D )
I ‘ve implemented your shell in my free Open Source PHP Framework, and i’ve builded a multi theme plug in
how to share it?
Regards
Mirko
Hi, I am glad you like it. You can post links here or email me: tmi at 5p, then I will share it on this site. I would like to see your plug in and your project :-)
sended an e-mail :)
i hope you will find it a nice plugin
Hejsa,
I’ve just given TinyShell a quick spin. Great!
I’m having trouble with vi/vim and ssh though; two important tools…
I have discovered that it doesn’t give me a real terminal:
Fair enough. Worse, though, is that if I try to launch vim (from vim-gtk), the prompt just disappears and I can’t seem to get it back. Refreshing the browser page also doesn’t work. I have to restart apache. Which is only possible if I have a command line to the server. A chicken-and-egg situation.
I also would like to be able to use ssh to get from that server to another. But:
I’m not sure why that is. If I try this from a real terminal, it works fine.
Hi, you are right ;-) TinyShell is not a real terminal, it does not support (n)curses programs, like top, vi, vim, etc. But you can use the plugin called tiny to edit files. Regarding SSH and top, unfortunately you will have to make a new plugin to support this. But if you have access to do this already, why don’t you use SSH directly instead of TinyShell? TinyShell is more ment to upload to FTP servers, where one does not have shell access. You should be able to call $apache restart though, but it requires that PHP has the right access to perform the command.
Hi, I understand and accept that I can’t use vi or top or whatever. That they won’t work. But TinyShell should survive if I by mistake try to use them anyway. I should be able to get my prompt back somehow. The problem is that I if I by mistake type “vi file” I’m toast. I cannot CTRL-C, or reload the browser or anything. I need to restart the web server (by some other means) to get anything working again. That means I cannot rely on it. If TinyShell access is all I have, “vi file” means I loose connection to the server forever. A truck roll is required.
Here in my debug environment I do have normal terminal access. But once we’ve gone live, I won’t have that. Only HTTP access to serverA. For some reason that I don’t understand it isn’t possible from a TinyShell on serverA to ssh to serverB. Once live I won’t have terminal access to any of them – only TinyShell access. And its a shame I won’t be able to get anywhere from serverA via SSH, don’t you think?
I hope I’ve been more clear this time! :-)
I never realized that PHP would actually wait forever for the command to execute and then also cause the web server to hang. I made a few tests, and it seems that system calls are not affected by the PHP max_execution_time/set_time_limit functions. Actually I also thought that web servers like Apache was configured by default to kill the PHP process after an amount of time, but I see that this is not always the case. But for now I suggest that you open sys.php in the plugin folder and either:
1. Create a black-list of unsupported commands you type by mistake.
2. Alter the shell_exec command, such that output is piped into a file and force a new process by adding an ampersand (&) in the end all commands (where it now already redirects the error stream to standard out). Then cat or tail this file for output after each system call. Problem is that you need to kill all the open process at some time if the do not terminate, but you will probably figure out a way to do this, or maybe do it when you have physical access to the server.
3. Modify the sys plugin to use proc_open instead of shell_exec, in order to gain control over the process that is started.
I think I will look at implementing the last solution in the near feature, and if you do, please share. Thanks for bringing up the problem :-)
Regarding SSH, you might want to copy the sys plugin to an ssh plugin and have a look at this: http://www.php.net/manual/en/function.ssh2-exec.php Unfortunately I do not have think most users have a need to create an SSH connection from the web server to another server through TinyShell, or even have enabled the requirements in PHP to do so, so I have not considered making such a plugin. And again, if you feel like doing some development on TinyShell, please tell me ;-)
Pingback: TinyShell, ssh like access to your website | Wildeng TechDad