Menu
▾
▴
phpshell-devel — Discuss the development of PHP Shell
You can subscribe to this list here.
| 2006 |
Jan
(2) |
Feb
(3) |
Mar
|
Apr
(6) |
May
(5) |
Jun
|
Jul
(7) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2007 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
(1) |
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
(16) |
Jun
(11) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2010 |
Jan
(1) |
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(12) |
Jul
(4) |
Aug
(5) |
Sep
|
Oct
(3) |
Nov
|
Dec
(6) |
| 2013 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
|
From: SourceForge.net <no...@so...> - 2006-07-08 00:54:18
|
Feature Requests item #1518713, was opened at 2006-07-07 14:56 Message generated for change (Comment added) made by hoerj You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=800590&aid=1518713&group_id=156638 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Interface Improvements Group: None >Status: Open Priority: 5 Submitted By: Jürgen Hörmann (hoerj) >Assigned to: Nobody/Anonymous (nobody) Summary: Merge all Files into one Initial Comment: Because this program opposes the webserver to a highly increased risk of being hacked i suggest not to leave the script on the server. To make it more usable to upload, use and delete the script it would be good if all files and config could be merged into one solid php file. ---------------------------------------------------------------------- >Comment By: Jürgen Hörmann (hoerj) Date: 2006-07-08 02:54 Message: Logged In: YES user_id=1551592 renaming the file does not help you anything. A very common attack is to use a script that does not check user input properly to include external files. this can easyly be checked if you drop input that contains the resource part of a URI like "http://". But as soon as the script is on the same server this will not help anything anymore. Most scripts will allow to include local files like "../../phpshell/phpshell.php" or .txt, it makes no difference what the fileextension is. If the content is valid php code it will be executed if included. Every attacker will try to get some access to the shell. phpshell is a perfect tool for that and many evil guys can use google to find this script on servers. I do not know how safe the built in authentification is, but .htaccess is of no use if you include the file from any other script. ---------------------------------------------------------------------- Comment By: Martin Geisler (mgeisler) Date: 2006-07-08 02:01 Message: Logged In: YES user_id=1264592 Yeah, I tend to agree with Tobias. Protecting the script with the builtin user management and/or a .htaccess file should be sufficient. If that isn't enough, then rename phpshell.php to phpshell.txt when you want to disable PHP Shell. That *must* be enough -- otherwise you have to ask yourself what kind of attack you anticipate. My point is that if people can still use PHP Shell after you've turned it into a text file, then people could most probably also break your system without PHP Shell being there in the first place. Deleting the phpshell.php file temporary and uploading it when needed could also work. The other support files should be quite harmless. I hope that makes sense -- I'll mark this feature request as "pending", meaning that it will be automatically closed in 14 days unless you repond to it. ---------------------------------------------------------------------- Comment By: Jürgen Hörmann (hoerj) Date: 2006-07-08 01:27 Message: Logged In: YES user_id=1551592 I can not agree. The effort to upload and delete the script is nothing compared to the security risk of this software. You should not deny the probability that there will always be other php scripts that have vulnerabilities. Those scripts might be exploited to include other files on the server. That way you can easyly bypass the .htaccess protection. That this scenario is not only a fiction is shown on your comment list on your "old" webpage. IMHO this script is mainly useful for installation and service tasks, jobs you only do from time to time. So the effort of uploading is negligible to me. The problem with the readability of the code coul be solved by making a development version that consists of multiple files that are only merged for the release version. It would be possible to make a setup routine that merges all files, too. ---------------------------------------------------------------------- Comment By: Tobias Unger (tobiasunger) Date: 2006-07-07 17:01 Message: Logged In: YES user_id=1432671 Hi, of course, software like this is also a safety risk, but I think this idea is very time-consuming. I think it is easyer and nearly as save as your idea to put the software into a directory protected by .htaccess (for a access control). Putting al the software in just one file would make this file less easy to understand. Tobias Unger (tobias-unger.de) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=800590&aid=1518713&group_id=156638 |
|
From: SourceForge.net <no...@so...> - 2006-07-08 00:01:20
|
Feature Requests item #1518713, was opened at 2006-07-07 14:56 Message generated for change (Comment added) made by mgeisler You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=800590&aid=1518713&group_id=156638 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Interface Improvements Group: None >Status: Pending Priority: 5 Submitted By: Jürgen Hörmann (hoerj) >Assigned to: Martin Geisler (mgeisler) Summary: Merge all Files into one Initial Comment: Because this program opposes the webserver to a highly increased risk of being hacked i suggest not to leave the script on the server. To make it more usable to upload, use and delete the script it would be good if all files and config could be merged into one solid php file. ---------------------------------------------------------------------- >Comment By: Martin Geisler (mgeisler) Date: 2006-07-08 02:01 Message: Logged In: YES user_id=1264592 Yeah, I tend to agree with Tobias. Protecting the script with the builtin user management and/or a .htaccess file should be sufficient. If that isn't enough, then rename phpshell.php to phpshell.txt when you want to disable PHP Shell. That *must* be enough -- otherwise you have to ask yourself what kind of attack you anticipate. My point is that if people can still use PHP Shell after you've turned it into a text file, then people could most probably also break your system without PHP Shell being there in the first place. Deleting the phpshell.php file temporary and uploading it when needed could also work. The other support files should be quite harmless. I hope that makes sense -- I'll mark this feature request as "pending", meaning that it will be automatically closed in 14 days unless you repond to it. ---------------------------------------------------------------------- Comment By: Jürgen Hörmann (hoerj) Date: 2006-07-08 01:27 Message: Logged In: YES user_id=1551592 I can not agree. The effort to upload and delete the script is nothing compared to the security risk of this software. You should not deny the probability that there will always be other php scripts that have vulnerabilities. Those scripts might be exploited to include other files on the server. That way you can easyly bypass the .htaccess protection. That this scenario is not only a fiction is shown on your comment list on your "old" webpage. IMHO this script is mainly useful for installation and service tasks, jobs you only do from time to time. So the effort of uploading is negligible to me. The problem with the readability of the code coul be solved by making a development version that consists of multiple files that are only merged for the release version. It would be possible to make a setup routine that merges all files, too. ---------------------------------------------------------------------- Comment By: Tobias Unger (tobiasunger) Date: 2006-07-07 17:01 Message: Logged In: YES user_id=1432671 Hi, of course, software like this is also a safety risk, but I think this idea is very time-consuming. I think it is easyer and nearly as save as your idea to put the software into a directory protected by .htaccess (for a access control). Putting al the software in just one file would make this file less easy to understand. Tobias Unger (tobias-unger.de) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=800590&aid=1518713&group_id=156638 |
|
From: SourceForge.net <no...@so...> - 2006-07-07 23:27:54
|
Feature Requests item #1518713, was opened at 2006-07-07 14:56 Message generated for change (Comment added) made by hoerj You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=800590&aid=1518713&group_id=156638 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Interface Improvements Group: None Status: Open Priority: 5 Submitted By: Jürgen Hörmann (hoerj) Assigned to: Nobody/Anonymous (nobody) Summary: Merge all Files into one Initial Comment: Because this program opposes the webserver to a highly increased risk of being hacked i suggest not to leave the script on the server. To make it more usable to upload, use and delete the script it would be good if all files and config could be merged into one solid php file. ---------------------------------------------------------------------- >Comment By: Jürgen Hörmann (hoerj) Date: 2006-07-08 01:27 Message: Logged In: YES user_id=1551592 I can not agree. The effort to upload and delete the script is nothing compared to the security risk of this software. You should not deny the probability that there will always be other php scripts that have vulnerabilities. Those scripts might be exploited to include other files on the server. That way you can easyly bypass the .htaccess protection. That this scenario is not only a fiction is shown on your comment list on your "old" webpage. IMHO this script is mainly useful for installation and service tasks, jobs you only do from time to time. So the effort of uploading is negligible to me. The problem with the readability of the code coul be solved by making a development version that consists of multiple files that are only merged for the release version. It would be possible to make a setup routine that merges all files, too. ---------------------------------------------------------------------- Comment By: Tobias Unger (tobiasunger) Date: 2006-07-07 17:01 Message: Logged In: YES user_id=1432671 Hi, of course, software like this is also a safety risk, but I think this idea is very time-consuming. I think it is easyer and nearly as save as your idea to put the software into a directory protected by .htaccess (for a access control). Putting al the software in just one file would make this file less easy to understand. Tobias Unger (tobias-unger.de) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=800590&aid=1518713&group_id=156638 |
|
From: SourceForge.net <no...@so...> - 2006-07-07 15:01:52
|
Feature Requests item #1518713, was opened at 2006-07-07 14:56 Message generated for change (Comment added) made by tobiasunger You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=800590&aid=1518713&group_id=156638 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Interface Improvements Group: None Status: Open Priority: 5 Submitted By: Jürgen Hörmann (hoerj) Assigned to: Nobody/Anonymous (nobody) Summary: Merge all Files into one Initial Comment: Because this program opposes the webserver to a highly increased risk of being hacked i suggest not to leave the script on the server. To make it more usable to upload, use and delete the script it would be good if all files and config could be merged into one solid php file. ---------------------------------------------------------------------- Comment By: Tobias Unger (tobiasunger) Date: 2006-07-07 17:01 Message: Logged In: YES user_id=1432671 Hi, of course, software like this is also a safety risk, but I think this idea is very time-consuming. I think it is easyer and nearly as save as your idea to put the software into a directory protected by .htaccess (for a access control). Putting al the software in just one file would make this file less easy to understand. Tobias Unger (tobias-unger.de) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=800590&aid=1518713&group_id=156638 |
|
From: SourceForge.net <no...@so...> - 2006-07-07 12:56:45
|
Feature Requests item #1518713, was opened at 2006-07-07 14:56 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=800590&aid=1518713&group_id=156638 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Interface Improvements Group: None Status: Open Priority: 5 Submitted By: Jürgen Hörmann (hoerj) Assigned to: Nobody/Anonymous (nobody) Summary: Merge all Files into one Initial Comment: Because this program opposes the webserver to a highly increased risk of being hacked i suggest not to leave the script on the server. To make it more usable to upload, use and delete the script it would be good if all files and config could be merged into one solid php file. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=800590&aid=1518713&group_id=156638 |
|
From: SourceForge.net <no...@so...> - 2006-05-15 18:55:11
|
Patches item #1489054, was opened at 2006-05-15 20:55 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=800589&aid=1489054&group_id=156638 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Documentation Group: SVN Status: Open Resolution: None Priority: 5 Submitted By: Martin Geisler (mgeisler) Assigned to: Martin Geisler (mgeisler) Summary: Information about renaming phpshell.php Initial Comment: Some hosting environments use a simple form of "protection" whereby you are denied access to any file called phpshell.php or shell.php. This kind of "protection" only gives a false sense of security since you can rename phpshell.php to, say, happy_sunshine.php and then continue to use it... So SECURITY should be updated with information about this possibility. This is meant both as a reminder to administrators of shared web hosts who might think that blocking access to phpshell.php is enough, and as a tip for people who want to use PHP Shell dispite the wishes of the administrator. In general, SECURITY should contain more information about how one can block applications like PHP Shell. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=800589&aid=1489054&group_id=156638 |
|
From: SourceForge.net <no...@so...> - 2006-05-15 18:44:44
|
Feature Requests item #1489049, was opened at 2006-05-15 20:44 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=800590&aid=1489049&group_id=156638 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: SVN Status: Open Priority: 6 Submitted By: Martin Geisler (mgeisler) Assigned to: Nobody/Anonymous (nobody) Summary: Make authentication optional Initial Comment: It seems that the authentication is causing trouble on some installations, and that the only way to make PHP Shell work is to disable it all together. It would therefore be good if PHP Shell supported this via an option in the configuration file. This option would of course be followed by huge warnings, urging people to actually implement some alternative form of authentication (.htaccess for example). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=800590&aid=1489049&group_id=156638 |
|
From: SourceForge.net <no...@so...> - 2006-05-09 00:45:54
|
Feature Requests item #1398892, was opened at 2006-01-06 23:52 Message generated for change (Comment added) made by mgeisler You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=800590&aid=1398892&group_id=156638 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Interface Improvements >Group: Version 2.1 >Status: Closed Priority: 7 Submitted By: Martin Geisler (mgeisler) >Assigned to: Martin Geisler (mgeisler) Summary: Feedback on Safe Mode Initial Comment: PHP Shell should give specific feedback on the potential problems caused by running it with PHP in Safe Mode. The code already detects Safe Mode and tries to degrade gracefully, but having a clear warning (in big red letters :-) would probably be a good idea. This should of course be configurable. ---------------------------------------------------------------------- >Comment By: Martin Geisler (mgeisler) Date: 2006-05-08 00:53 Message: Logged In: YES user_id=1264592 Fixed in SVN. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=800590&aid=1398892&group_id=156638 |
|
From: SourceForge.net <no...@so...> - 2006-05-08 17:13:21
|
Patches item #1398916, was opened at 2006-01-07 00:42 Message generated for change (Comment added) made by mgeisler You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=800589&aid=1398916&group_id=156638 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Documentation >Group: Version 2.1 >Status: Closed >Resolution: Accepted Priority: 5 Submitted By: Martin Geisler (mgeisler) >Assigned to: Martin Geisler (mgeisler) Summary: List of alternatives Initial Comment: Like any good open-source program PHP Shell shouldn't be afraid of mentioning some of the alternatives out there. An incomplete list would be: * SSH. The Secure Shell is the standard solution to the problem that PHP Shell tries to solve. SSH lets you login to a remote system in a secure way where the traffic and password is encrypted at all times. You can also upload and download files securely and make encrypted TCP tunnels. If your host supports SSH then use it and forget about PHP Shell or any other solution. * Telnet. This is the old way to obtain an interactive login on a remote system. Unfortunately telnet is insecure since the password and subsequent traffic are sent in clear text. SSH was developed precisely to replace telnet. The advantage of telnet over PHP Shell is that it gives you an interactive session. * See more alternatives at the Anyterm homepage: http://anyterm.org/compared.html ---------------------------------------------------------------------- >Comment By: Martin Geisler (mgeisler) Date: 2006-05-08 00:14 Message: Logged In: YES user_id=1264592 This is now in SVN and will be part of version 2.2. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=800589&aid=1398916&group_id=156638 |
|
From: SourceForge.net <no...@so...> - 2006-05-08 17:13:17
|
Bugs item #1479459, was opened at 2006-04-30 21:41 Message generated for change (Comment added) made by mgeisler You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=800587&aid=1479459&group_id=156638 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. >Category: Built-in commands Group: Version 2.1 Status: Open >Resolution: Remind Priority: 6 Submitted By: Martin Geisler (mgeisler) >Assigned to: Martin Geisler (mgeisler) Summary: Directory names with spaces Initial Comment: You currently cannot switch to a directory with spaces in its name. Spaces in normal file names are no problem, they are handled just like any other shell. The problem is that PHP Shell doesn't decode the string before passing it to the PHP chdir() function. So any quoting or escaping done by the user is left as-is in the call to chdir(). ---------------------------------------------------------------------- >Comment By: Martin Geisler (mgeisler) Date: 2006-05-08 00:28 Message: Logged In: YES user_id=1264592 Actually one can switch to directories with spaces in the name, one simply don't quote the spaces in any special way. PHP Shell deals with the 'cd' command as an internal command and naïvely does a chdir() call with the path found after the 'cd' command. PHP Shell should probably remove quotes like other shells or this should be documented. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=800587&aid=1479459&group_id=156638 |
|
From: SourceForge.net <no...@so...> - 2006-04-30 19:48:52
|
Feature Requests item #1479461, was opened at 2006-04-30 21:48 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=800590&aid=1479461&group_id=156638 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Interface Improvements Group: None Status: Open Priority: 4 Submitted By: Martin Geisler (mgeisler) Assigned to: Nobody/Anonymous (nobody) Summary: Advanced history Initial Comment: The history of commands could be made more advanced: duplicates could be ignored, it could be saved between sessions (in a cookie or on the server). Of course one should also be able to clear it on demand. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=800590&aid=1479461&group_id=156638 |
|
From: SourceForge.net <no...@so...> - 2006-04-30 19:41:20
|
Bugs item #1479459, was opened at 2006-04-30 21:41 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=800587&aid=1479459&group_id=156638 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: Version 2.1 Status: Open Resolution: None Priority: 6 Submitted By: Martin Geisler (mgeisler) Assigned to: Nobody/Anonymous (nobody) Summary: Directory names with spaces Initial Comment: You currently cannot switch to a directory with spaces in its name. Spaces in normal file names are no problem, they are handled just like any other shell. The problem is that PHP Shell doesn't decode the string before passing it to the PHP chdir() function. So any quoting or escaping done by the user is left as-is in the call to chdir(). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=800587&aid=1479459&group_id=156638 |
|
From: SourceForge.net <no...@so...> - 2006-04-30 19:15:53
|
Feature Requests item #1479450, was opened at 2006-04-30 21:15 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=800590&aid=1479450&group_id=156638 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Interface Improvements Group: None Status: Open Priority: 5 Submitted By: Martin Geisler (mgeisler) Assigned to: Nobody/Anonymous (nobody) Summary: Add clear button Initial Comment: The button should clear the screen. Having 'clear' as a new built-in command for this would also be nice. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=800590&aid=1479450&group_id=156638 |
|
From: SourceForge.net <no...@so...> - 2006-04-30 19:09:38
|
Feature Requests item #1479447, was opened at 2006-04-30 21:09 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=800590&aid=1479447&group_id=156638 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Internal Commands Group: None Status: Open Priority: 2 Submitted By: Martin Geisler (mgeisler) Assigned to: Nobody/Anonymous (nobody) Summary: Built-in compression (tar, zip, gzip) Initial Comment: For very restricted UNIX hosts or Windows hosts it would be useful if PHP Shell could unpack compressed files itself without relying on external tools. This could be done with the PHP extensions if they are available, or with a pure PHP implementation as a fallback. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=800590&aid=1479447&group_id=156638 |
|
From: SourceForge.net <no...@so...> - 2006-04-30 19:06:09
|
Feature Requests item #1479446, was opened at 2006-04-30 21:06 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=800590&aid=1479446&group_id=156638 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Priority: 4 Submitted By: Martin Geisler (mgeisler) Assigned to: Nobody/Anonymous (nobody) Summary: Option to force SSL (HTTPS) Initial Comment: It should be quite simple and somewhat useful to have an option which would make PHP Shell refuse to run over a normal HTTP link. People who install PHP Shell on a server with SSL enabled would want to make sure that they always use the HTTPS URL. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=800590&aid=1479446&group_id=156638 |
|
From: SourceForge.net <no...@so...> - 2006-04-30 19:01:28
|
Feature Requests item #1479445, was opened at 2006-04-30 21:01 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=800590&aid=1479445&group_id=156638 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Interface Improvements Group: None Status: Open Priority: 3 Submitted By: Martin Geisler (mgeisler) Assigned to: Nobody/Anonymous (nobody) Summary: Customize prompt Initial Comment: It would be neat if one could customize the prompt, just as in a normal shell. This could be as simple as being able to substitute the default prompt for another, or it could be a fancy system with prompt expansion as in Zsh where as %m expands to the hostname, a %D expands to the current date, etc. Also inspired by Zsh, one could try and make a *right* prompt. This would be just like a normal prompt, but aligned to the right. This is quite useful in a normal terminal, but maybe not so for a web-terminal (since the information could just as easily be placed somewhere else, i.e., below the terminal window. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=800590&aid=1479445&group_id=156638 |
|
From: SourceForge.net <no...@so...> - 2006-02-04 15:17:36
|
Patches item #1424084, was opened at 2006-02-04 16:13 Message generated for change (Comment added) made by mgeisler You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=800589&aid=1424084&group_id=156638 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: Version 2.1 Status: Open >Resolution: Accepted Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Editor feature Initial Comment: This Patch addes an editor feature to PHP-Shell 2.1 . You just have to unzip the file and then copy phpshell.php to your PHP-Shell Directory! Then you can start the editor using "editor FILENAME" . Please do not forget this Patch is only testet with PHP-Shell Version 2.1 and may cause problems with other versions!!! License: GPL If you have any questions related to this Patch please feel free to contact me: ma...@to... (Emails should be either German or English)! ---------------------------------------------------------------------- >Comment By: Martin Geisler (mgeisler) Date: 2006-02-04 16:17 Message: Logged In: YES user_id=1264592 Thanks for submitting this -- as we've already spoken about in private mails then I'm sure we can use such a feature in the next version. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=800589&aid=1424084&group_id=156638 |
|
From: SourceForge.net <no...@so...> - 2006-02-04 15:13:49
|
Patches item #1424084, was opened at 2006-02-04 07:13 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=800589&aid=1424084&group_id=156638 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: Version 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Editor feature Initial Comment: This Patch addes an editor feature to PHP-Shell 2.1 . You just have to unzip the file and then copy phpshell.php to your PHP-Shell Directory! Then you can start the editor using "editor FILENAME" . Please do not forget this Patch is only testet with PHP-Shell Version 2.1 and may cause problems with other versions!!! License: GPL If you have any questions related to this Patch please feel free to contact me: ma...@to... (Emails should be either German or English)! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=800589&aid=1424084&group_id=156638 |
|
From: Tobias U. <ma...@to...> - 2006-02-04 13:36:27
|
Hi Martin Geisler, I have got published the "Editor-Update" on my Website: http://www.tobias-unger.de/download . So everybody is able to try and test it until you publish a new Version of PHP-Shell including this feature! Direct Download Link: http://tobias-unger.de/download/phpshell.zip License: GPL Tobias -- Tobias Unger ma...@to... www.tobias-unger.de |
|
From: Martin G. <mge...@mg...> - 2006-01-12 23:21:13
|
Martin Geisler <mge...@mg...> writes: > What still needs to be done: > > * Import into CVS: I think I will import all the versions I have ever > released of PHP Shell, all the way back to 1.5. This will give us > the entire project history, albeit with much abbreviated histories. > > We will hopefully soon be able to switch to Subversion, I've asked > to be part of the upcoming beta on SF. And I've just gotten a negative response -- the beta is apparently already running. Too bad for us, but on the other hand it's good to hear that they're working on it! =2D-=20 Martin Geisler GnuPG Key: 0x7E45DD38 PHP Exif Library | PHP Weather | PHP Shell http://pel.sf.net/ | http://phpweather.net/ | http://mgeisler.net/ Read/write Exif data | Show current weather | A shell in a browser |
|
From: Martin G. <mge...@mg...> - 2006-01-12 21:48:44
|
Hello, The process of moving things over from mgeisler.net to SourceForge is being completed step by step. Most of the infrastructure for PHP Shell has now been setup: * Mailinglists: phpshell-devel and phpshell-commits. They are also carried by Gmane, please see: http://dir.gmane.org/gmane.comp.php.phpshell.devel http://dir.gmane.org/gmane.comp.php.phpshell.cvs (Please ignore the renaming of phpshell-commits to phpshell.cvs, it is the official Gmane policy to mangle names like that in the name of consistancy.) * Trackers: Bugs, Patches, and Feature Requests. I removed the Support Request tracker in the hope that people will write to the mailinglists instead. All trackers actually feed the phpshell-devel list to make it easier to monitor things. What still needs to be done: * Import into CVS: I think I will import all the versions I have ever released of PHP Shell, all the way back to 1.5. This will give us the entire project history, albeit with much abbreviated histories. We will hopefully soon be able to switch to Subversion, I've asked to be part of the upcoming beta on SF. * File releases: the old files should of course be moved to SF. * Homepage: A simple project page should be setup. I imagine copying the page from another project of mine (http://pel.sf.net/) which has a simple layout and nice integration with the SF news system. * Screenshots: A couple of nice screenshots should be posted on SF. Suggestions? Ideas? Things I've forgotten? Please get in contact! =2D-=20 Martin Geisler GnuPG Key: 0x7E45DD38 PHP Exif Library | PHP Weather | PHP Shell http://pel.sf.net/ | http://phpweather.net/ | http://mgeisler.net/ Read/write Exif data | Show current weather | A shell in a browser |
