shellinabox - Project Hosting on Google Code

Yesterday 32 hours ago issue 40 (Can't get ShellinaBox to run with OpenSSL on Centos 5.4) commented on by zod...@gmail.com - Did configure even find the OpenSSL development files? What does config.h show? How about "shellinaboxd --help", does it show options for disabling SSL? If not, then it isn't even compiled with SSL support. Did configure even find the OpenSSL development files? What does config.h show? How about "shellinaboxd --help", does it show options for disabling SSL? If not, then it isn't even compiled with SSL support. 32 hours ago issue 40 (Can't get ShellinaBox to run with OpenSSL on Centos 5.4) reported by gianniperez - What steps will reproduce the problem? 1. Installed from source using tar ball 2. ./configure - make && make install 3. Ran shellinaboxd and it works but not through HTTPS What is the expected output? What do you see instead? A secured session What version of the product are you using? On what operating system? Latest - CentOS 5.4 (Final) Please provide any additional information below. OpenSSL works fine for Webmin sessions. Not for Shellinabox though. What steps will reproduce the problem? 1. Installed from source using tar ball 2. ./configure - make && make install 3. Ran shellinaboxd and it works but not through HTTPS What is the expected output? What do you see instead? A secured session What version of the product are you using? On what operating system? Latest - CentOS 5.4 (Final) Please provide any additional information below. OpenSSL works fine for Webmin sessions. Not for Shellinabox though. Last 7 days Dec 04, 2009 issue 39 (Clipboard not integrated with client operating system) Status changed by zod...@gmail.com - This is a very tricky problem. For security reasons, JavaScript does not typically have access to the system clipboard. There are various work-arounds (some them are already implemented in ShellInABox), that on some platforms give limited access to the clipboard. But in practice this is a hard problem to solve. And it never quite works seamlessly. I have some ideas that I want to try out at some point. But for now, you will have to live with the internal clipboard (i.e. you can copy and paste within ShellInABox, but not exchange data with any other application). And even going forward, I might not be able to fix this completely. I'll keep this issue open for a while, in case some of my experiments show that I can improve the user experience -- however gradually. Thanks for reporting this issue. Status: Accepted This is a very tricky problem. For security reasons, JavaScript does not typically have access to the system clipboard. There are various work-arounds (some them are already implemented in ShellInABox), that on some platforms give limited access to the clipboard. But in practice this is a hard problem to solve. And it never quite works seamlessly. I have some ideas that I want to try out at some point. But for now, you will have to live with the internal clipboard (i.e. you can copy and paste within ShellInABox, but not exchange data with any other application). And even going forward, I might not be able to fix this completely. I'll keep this issue open for a while, in case some of my experiments show that I can improve the user experience -- however gradually. Thanks for reporting this issue. Status: Accepted Dec 04, 2009 issue 39 (Clipboard not integrated with client operating system) reported by taylor.jones - Love the project! This is a minor gripe that may not have an easy (any?) solution. What steps will reproduce the problem? 1. Copy text from another application 2. Right click in the shellinabox console 3. Paste option is disabled What is the expected output? What do you see instead? Paste option is enabled and allows me to paste the contents of my system clipboard. What version of the product are you using? On what operating system? Server: shellinabox-2.10 on Debian Testing (armel) Client: Firefox 3.5 on Windows XP Please provide any additional information below. If it is not possible to integrate the copy/paste options in the right-click menu with the operating system's clipboard, consider this possible solution: Don't hijack the Common User Access (http://en.wikipedia.org/wiki/Common_User_Access) shortcuts (e.g. Shift+Ins). Instead leave them to the interpretation of the web browser/operating system. Love the project! This is a minor gripe that may not have an easy (any?) solution. What steps will reproduce the problem? 1. Copy text from another application 2. Right click in the shellinabox console 3. Paste option is disabled What is the expected output? What do you see instead? Paste option is enabled and allows me to paste the contents of my system clipboard. What version of the product are you using? On what operating system? Server: shellinabox-2.10 on Debian Testing (armel) Client: Firefox 3.5 on Windows XP Please provide any additional information below. If it is not possible to integrate the copy/paste options in the right-click menu with the operating system's clipboard, consider this possible solution: Don't hijack the Common User Access (http://en.wikipedia.org/wiki/Common_User_Access) shortcuts (e.g. Shift+Ins). Instead leave them to the interpretation of the web browser/operating system. Dec 03, 2009 shellinaboxd_man (shellinaboxd - publish command line shell through AJAX inter...) Wiki page edited by zod...@gmail.com - Revision r199 Edited wiki page through web user interface. Revision r199 Edited wiki page through web user interface. Dec 03, 2009 r198 (Allow retrieval of the user's default login shell from /etc/...) committed by zod...@gmail.com - Allow retrieval of the user's default login shell from /etc/passwd. Allow the code to be built without support for the LOGIN service, as calling /bin/login does not work well on Fedora. Allow retrieval of the user's default login shell from /etc/passwd. Allow the code to be built without support for the LOGIN service, as calling /bin/login does not work well on Fedora. Dec 02, 2009 r197 (Added fallback code that dynamically computes the correct co...) committed by zod...@gmail.com - Added fallback code that dynamically computes the correct commandline arguments for "objcopy" if building for an otherwise unknown target platform. Fixed a lintian "informational" message. Added fallback code that dynamically computes the correct commandline arguments for "objcopy" if building for an otherwise unknown target platform. Fixed a lintian "informational" message. Dec 02, 2009 r196 (Corrected URL in debian/watch file ) committed by zod...@gmail.com - Corrected URL in debian/watch file Corrected URL in debian/watch file Dec 02, 2009 r195 (Fixed lintian errors. ) committed by zod...@gmail.com - Fixed lintian errors. Fixed lintian errors. Dec 01, 2009 r194 (* Added checks that the debian/changelog file is up-to-date ...) committed by zod...@gmail.com - * Added checks that the debian/changelog file is up-to-date * Added debian/watch file * Updated the Standards-Version in debian/control. Still need to review whether we are in full compliance, though. * Added checks that the debian/changelog file is up-to-date * Added debian/watch file * Updated the Standards-Version in debian/control. Still need to review whether we are in full compliance, though. Last 30 days Dec 01, 2009 r193 ( Added some basic sanity checks to the commit script that no...) committed by zod...@gmail.com - Added some basic sanity checks to the commit script that now makes sure we at least attempt to keep copyright dates updated whenever we make changes. Added some basic sanity checks to the commit script that now makes sure we at least attempt to keep copyright dates updated whenever we make changes. Nov 30, 2009 issue 28 (feture request) commented on by renatoat - Agreed. I could put only the part after "ssh" in the command file or, even better, create a wrapper file which calls the command file only IF it is allowed (allowed = isin `ls /home/myuser/myfolder/`). Agreed. I could put only the part after "ssh" in the command file or, even better, create a wrapper file which calls the command file only IF it is allowed (allowed = isin `ls /home/myuser/myfolder/`). Nov 30, 2009 issue 38 (Cannot start shellinabox with ssl enabled) commented on by zod...@gmail.com - Thanks. I added a link to the project's home page. Thanks. I added a link to the project's home page. Nov 30, 2009 issue 28 (feture request) commented on by zod...@gmail.com - I'd be a little worried about somebody putting things like ../ into the URL in order to make ShellInABox read arbitrary files in your file system -- or even worse, if your machine has user-writable directories mounted, it would allow an attacker to run arbitrary code as a privileged user. I'd be a little worried about somebody putting things like ../ into the URL in order to make ShellInABox read arbitrary files in your file system -- or even worse, if your machine has user-writable directories mounted, it would allow an attacker to run arbitrary code as a privileged user. Nov 30, 2009 r192 (Preparations for packaging ShellInABox in a way that makes i...) committed by zod...@gmail.com - Preparations for packaging ShellInABox in a way that makes it easy for Debian package maintainers to pick it up. Preparations for packaging ShellInABox in a way that makes it easy for Debian package maintainers to pick it up. Nov 27, 2009 issue 28 (feture request) commented on by renatoat - Just to get your opinion: I'm using this service description: shellinaboxd -s "/:$(id -u):$(id -g):HOME:"'/bin/bash -c "u=${url}; exec `cat /home/myuser/myfolder/\${u##\\?}.cmd`"' And I access it like http://192.168.0.1:4200/?file and I have the SSH command inside file.cmd, for instance. My doubt is: is there any way a user could inject commands inside the URL, without being explicitely inside my cmd file? I don't see the way, so I'd like to know if you can see any. Thanks. Just to get your opinion: I'm using this service description: shellinaboxd -s "/:$(id -u):$(id -g):HOME:"'/bin/bash -c "u=${url}; exec `cat /home/myuser/myfolder/\${u##\\?}.cmd`"' And I access it like http://192.168.0.1:4200/?file and I have the SSH command inside file.cmd, for instance. My doubt is: is there any way a user could inject commands inside the URL, without being explicitely inside my cmd file? I don't see the way, so I'd like to know if you can see any. Thanks. Nov 27, 2009 issue 38 (Cannot start shellinabox with ssl enabled) commented on by alan.pope - https://edge.launchpad.net/~popey/+archive/shellinabox Now in the ppa. https://edge.launchpad.net/~popey/+archive/shellinabox Now in the ppa. Nov 26, 2009 issue 36 (Add 80/132 column mode) commented on by ste...@mbase.com.au - Thanks. I am testing using ncurses demos and vttest. I will give a summary in the next few days. Thanks. I am testing using ncurses demos and vttest. I will give a summary in the next few days. Nov 26, 2009 issue 38 (Cannot start shellinabox with ssl enabled) commented on by alan.pope - http://mentors.debian.net/ Is apparently the best place to start. File an ITP bug in debian to get your package in there. Once in Debian it will filter to Ubuntu. http://mentors.debian.net/ Is apparently the best place to start. File an ITP bug in debian to get your package in there. Once in Debian it will filter to Ubuntu. Nov 26, 2009 r191 (Lock the Debian compatibility level a 6, so that the package...) committed by zod...@gmail.com - Lock the Debian compatibility level a 6, so that the packages can easily be built on Hardy. Lock the Debian compatibility level a 6, so that the packages can easily be built on Hardy. Nov 26, 2009 issue 38 (Cannot start shellinabox with ssl enabled) commented on by zod...@gmail.com - Yes, that build failure is a little annoying. Something keeps resetting the compatibility level for no good reason. You can safely decrease it back to six. I'll put something into my build scripts to always reset it going forward. As for the PPA on Launchpad, that sounds like a great idea. Let me know, when it is fully populated and I'll link to it from the project's front page. Also, I'd love to find somebody who can sponsor the project so that it becomes an official Debian and/or Ubuntu package. Having it become part of the distribution would be a great way of making sure that users get properly built binary packages. But I am not quite aware of what the steps are to get this done. So, if you have any insight, I'd appreciate your help. Yes, that build failure is a little annoying. Something keeps resetting the compatibility level for no good reason. You can safely decrease it back to six. I'll put something into my build scripts to always reset it going forward. As for the PPA on Launchpad, that sounds like a great idea. Let me know, when it is fully populated and I'll link to it from the project's front page. Also, I'd love to find somebody who can sponsor the project so that it becomes an official Debian and/or Ubuntu package. Having it become part of the distribution would be a great way of making sure that users get properly built binary packages. But I am not quite aware of what the steps are to get this done. So, if you have any insight, I'd appreciate your help. Nov 26, 2009 issue 38 (Cannot start shellinabox with ssl enabled) commented on by alan.pope - Ok, fixed that after speaking to experts in #ubuntu-motu :) Once launchpad has some capacity there should be binaries for hardy, jaunty and karmic. I'll give lucid a bash once that's stable - given it's LTS. Ok, fixed that after speaking to experts in #ubuntu-motu :) Once launchpad has some capacity there should be binaries for hardy, jaunty and karmic. I'll give lucid a bash once that's stable - given it's LTS. Nov 26, 2009 issue 38 (Cannot start shellinabox with ssl enabled) commented on by alan.pope - I've created a ppa on launchpad where I'll put pre-built packages for Ubuntu. Dunno if that's useful to you/anyone. https://edge.launchpad.net/~popey/+archive/shellinabox So far I've added karmic, but the build for hardy fails. See attachment. Will play a bit more.. I've created a ppa on launchpad where I'll put pre-built packages for Ubuntu. Dunno if that's useful to you/anyone. https://edge.launchpad.net/~popey/+archive/shellinabox So far I've added karmic, but the build for hardy fails. See attachment. Will play a bit more.. Nov 26, 2009 issue 38 (Cannot start shellinabox with ssl enabled) Status changed by zod...@gmail.com - I am glad to hear that recompiling fixes the problem for you. This is a general issue with releasing binary packages. It is hard or even impossible to create binary packages that work for everybody. In general, building from source is much safer. I occasionally contemplate not offering any binary packages, but it seems that for some users having to built from source is a major hurdle -- and if the binary package happens to work for them, then they are very well served by it. It's all a big trade- off. For now, I'll close this bug -- even though, I don't have a good solution that would make everybody happy. Status: WontFix I am glad to hear that recompiling fixes the problem for you. This is a general issue with releasing binary packages. It is hard or even impossible to create binary packages that work for everybody. In general, building from source is much safer. I occasionally contemplate not offering any binary packages, but it seems that for some users having to built from source is a major hurdle -- and if the binary package happens to work for them, then they are very well served by it. It's all a big trade- off. For now, I'll close this bug -- even though, I don't have a good solution that would make everybody happy. Status: WontFix Nov 26, 2009 issue 38 (Cannot start shellinabox with ssl enabled) commented on by alan.pope - Yes compiling from source on the hardy box worked fine. Yes compiling from source on the hardy box worked fine. Nov 26, 2009 issue 38 (Cannot start shellinabox with ssl enabled) commented on by zod...@gmail.com - I built the packages on Karmic. It is quite possible that Hardy is too old for the binary packages. Can you try building from source and see if that gives you a package that works for you? The INSTALL.Debian file has detailed instructions on how to build a new package. I built the packages on Karmic. It is quite possible that Hardy is too old for the binary packages. Can you try building from source and see if that gives you a package that works for you? The INSTALL.Debian file has detailed instructions on how to build a new package. Nov 26, 2009 issue 38 (Cannot start shellinabox with ssl enabled) reported by alan.pope - What steps will reproduce the problem? 1. Install the .deb on Ubuntu 8.04.3 Hardy server 2. Attempt to start shellinabox using sudo /etc/init.d/shellinabox start 3. get error message What is the expected output? What do you see instead? alan@bishop:~$ sudo /etc/init.d/shellinabox start * Starting Shell In A Box Daemon shellinabox Check failed at libhttp/ssl.c:685 in sslSetCertificate(): SSL_CTX_set_tlsext_servername_callback(ssl->sslContext, sslSNICallback) ...done. What version of the product are you using? On what operating system? ii shellinabox 2.10-1 publish command line shell through AJAX interface alan@bishop:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 8.04.3 LTS Release: 8.04 Codename: hardy Please provide any additional information below. What steps will reproduce the problem? 1. Install the .deb on Ubuntu 8.04.3 Hardy server 2. Attempt to start shellinabox using sudo /etc/init.d/shellinabox start 3. get error message What is the expected output? What do you see instead? alan@bishop:~$ sudo /etc/init.d/shellinabox start * Starting Shell In A Box Daemon shellinabox Check failed at libhttp/ssl.c:685 in sslSetCertificate(): SSL_CTX_set_tlsext_servername_callback(ssl->sslContext, sslSNICallback) ...done. What version of the product are you using? On what operating system? ii shellinabox 2.10-1 publish command line shell through AJAX interface alan@bishop:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 8.04.3 LTS Release: 8.04 Codename: hardy Please provide any additional information below. Nov 25, 2009 issue 36 (Add 80/132 column mode) Status changed by zod...@gmail.com - Fixed in subversion. Status: Fixed Fixed in subversion. Status: Fixed Nov 25, 2009 r190 (Enable switching between 80 and 132 column mode, if the brow...) committed by zod...@gmail.com - Enable switching between 80 and 132 column mode, if the browser supports CSS transforms. Enable switching between 80 and 132 column mode, if the browser supports CSS transforms. Nov 25, 2009 issue 37 (Possibility to get host, user, port and password by HTTP req...) commented on by renatoat - I didn't realize there were so many issues already open/closed, so I didn't see the other issue. The security "suprises" aren't really a problem, considering this SSH "helper" will be inside my network, in a way only authorized people will access. I understand and am aware of the security gap, if it leaks in some way. Thanks. I didn't realize there were so many issues already open/closed, so I didn't see the other issue. The security "suprises" aren't really a problem, considering this SSH "helper" will be inside my network, in a way only authorized people will access. I understand and am aware of the security gap, if it leaks in some way. Thanks. Nov 25, 2009 issue 28 (feture request) commented on by zod...@gmail.com - Issue 37 has been merged into this issue. Issue 37 has been merged into this issue. Nov 25, 2009 issue 37 (Possibility to get host, user, port and password by HTTP req...) changed by zod...@gmail.com - Take a look at the discussion in http://code.google.com/p/shellinabox/issues/detail?id=28 I believe it describes the exact same feature request. You can already do this with ShellInABox, if you provide a suitable script file and use the ${url} parameter. But you need to be very careful as you are potentially opening yourself up to all sorts of security problems. That's why I don't really want to document this deployment mode in any more detail. If you know how to set it up, and if you are fully aware of the security implications, then go ahead and use ShellInABox in this fashion. In all other cases, you are probably better of using it in the standard deployment mode which has far fewer security "surprises". Status: Duplicate Take a look at the discussion in http://code.google.com/p/shellinabox/issues/detail?id=28 I believe it describes the exact same feature request. You can already do this with ShellInABox, if you provide a suitable script file and use the ${url} parameter. But you need to be very careful as you are potentially opening yourself up to all sorts of security problems. That's why I don't really want to document this deployment mode in any more detail. If you know how to set it up, and if you are fully aware of the security implications, then go ahead and use ShellInABox in this fashion. In all other cases, you are probably better of using it in the standard deployment mode which has far fewer security "surprises". Status: Duplicate Nov 25, 2009 issue 37 (Possibility to get host, user, port and password by HTTP req...) reported by renatoat - What version of the product are you using? On what operating system? 2.10 on Debian Lenny (5.0) Is there any possibility to get the SSH host, user, port and password depending on the HTTP request, instead of one host configuration per service? I'd like to access, for instance, http://localhost:4200/:id or http://localhost:4200/:host/:user/:port or something like that, in a way the shellinabox would parse it and open the specific connection for that config, just waiting for the password (or connecting automatically if there is a public key present). So, in my intranet I would host it and when accessing http://localhost:4200/1 (with the config in some local file) or http://localhost:4200/domain.com/user01/2222 the connection would be also sucessful. Any idea how could I solve this idea, if no code change is needed? Thanks in advance. What version of the product are you using? On what operating system? 2.10 on Debian Lenny (5.0) Is there any possibility to get the SSH host, user, port and password depending on the HTTP request, instead of one host configuration per service? I'd like to access, for instance, http://localhost:4200/:id or http://localhost:4200/:host/:user/:port or something like that, in a way the shellinabox would parse it and open the specific connection for that config, just waiting for the password (or connecting automatically if there is a public key present). So, in my intranet I would host it and when accessing http://localhost:4200/1 (with the config in some local file) or http://localhost:4200/domain.com/user01/2222 the connection would be also sucessful. Any idea how could I solve this idea, if no code change is needed? Thanks in advance. Nov 23, 2009 issue 36 (Add 80/132 column mode) changed by zod...@gmail.com - This is not entirely trivial to do, as most modern browsers don't applications to arbitrarily resize windows anymore. And within standard HTML, there also is no easy way to request a font that is guaranteed to have a particular dimension. But when using a WebKit based browser (e.g. Chrome or Safari), we have access to CSS transforms which allow us to scale arbitrary web content. I believe, on any of those browsers I could "squish" the font when switching from 80 to 132 column mode. It'll require a few more changes throughout the code, but I'll see what I can do when I have a little time to experiment. Summary: Add 80/132 column mode Status: Accepted Labels: Type-Enhancement −Type-Defect This is not entirely trivial to do, as most modern browsers don't applications to arbitrarily resize windows anymore. And within standard HTML, there also is no easy way to request a font that is guaranteed to have a particular dimension. But when using a WebKit based browser (e.g. Chrome or Safari), we have access to CSS transforms which allow us to scale arbitrary web content. I believe, on any of those browsers I could "squish" the font when switching from 80 to 132 column mode. It'll require a few more changes throughout the code, but I'll see what I can do when I have a little time to experiment. Summary: Add 80/132 column mode Status: Accepted Labels: Type-Enhancement −Type-Defect Nov 23, 2009 issue 36 (VT100 line drawing using IBM437 characters) commented on by ste...@mbase.com.au - We have tried the app tonight using the escape sequences. All OK so far. How difficult would it be to add the 132 col support including switching back and forth? We have tried the app tonight using the escape sequences. All OK so far. How difficult would it be to add the 132 col support including switching back and forth? Nov 23, 2009 issue 36 (VT100 line drawing using IBM437 characters) commented on by ste...@mbase.com.au - I have deleted the attachments. Thanks again. I have deleted the attachments. Thanks again. Nov 23, 2009 issue 36 (VT100 line drawing using IBM437 characters) commented on by ste...@mbase.com.au - The echo escape sequence works on my CentOS virtual when I cat the mcc.log. Thank you for the very prompt reply. I will try the app in the office tomorrow. The echo escape sequence works on my CentOS virtual when I cat the mcc.log. Thank you for the very prompt reply. I will try the app in the office tomorrow. Nov 23, 2009 issue 36 (VT100 line drawing using IBM437 characters) changed by zod...@gmail.com - Don't try to play with the page's character encoding. ShellInABox already reports the correct character encoding to the browser and it makes sure to output everything in Unicode. If you manually override the character encoding in the browser, it either doesn't do anything, or really strange things will happen. ShellInABox understands UTF-8, so the best way to output non-ASCII characters is by making your application encode them in UTF-8. But if that is not an option, you can always send the appropriate escape codes to disable UTF-8 mode and to pick the code page that you want. In your case, that would be IBM437. Try running this command prior to running your application: echo -ne '\033%@\033(U' Summary: VT100 line drawing using IBM437 characters Status: WontFix Don't try to play with the page's character encoding. ShellInABox already reports the correct character encoding to the browser and it makes sure to output everything in Unicode. If you manually override the character encoding in the browser, it either doesn't do anything, or really strange things will happen. ShellInABox understands UTF-8, so the best way to output non-ASCII characters is by making your application encode them in UTF-8. But if that is not an option, you can always send the appropriate escape codes to disable UTF-8 mode and to pick the code page that you want. In your case, that would be IBM437. Try running this command prior to running your application: echo -ne '\033%@\033(U' Summary: VT100 line drawing using IBM437 characters Status: WontFix Nov 22, 2009 issue 36 (VT10 line drawing using IBM437 characters) commented on by ste...@mbase.com.au - Of course subject should be VT100 line drawing! Of course subject should be VT100 line drawing! Nov 22, 2009 issue 36 (VT10 line drawing using IBM437 characters) reported by ste...@mbase.com.au - I am struggling to display VT100 line drawing characters in shellinabox. I have tried different character encodings in different browsers running on different OS. The shellinabox daemon is running on CentOS 5.3. What steps will reproduce the problem? 1. I have tried different character encoding selections in Firefox 3.5.5 and Safari 4.0.4 on Mac 10.6 and Firefox 3.0.12 on Centos 5.3. 2. I have attached cp437.html that displays the expected line drawing characters when the character encoding is set to Default in Safari and Western (IBM-850) in Firefox. Note that the page has a META tag that defines charset=ibm437. 3. I have attached mcc.log which is a capture of an application screen with embedded IBM437 line drawing characters. 4. Opening cp437.html with encodings as above, the line drawing characters are displayed as expected. 5. However, a cat off mcc.log within a shellinabox VT100 terminal session gives a different result. What is the expected output? See Screen shot 2009-11-23 at 5.53.01 PM.png What do you see instead? See Screen shot 2009-11-23 at 5.59.57 PM.png What version of the product are you using? On what operating system? Built from 2.10.tar.gz source on CentOS 5.3 Please provide any additional information below. I am struggling to display VT100 line drawing characters in shellinabox. I have tried different character encodings in different browsers running on different OS. The shellinabox daemon is running on CentOS 5.3. What steps will reproduce the problem? 1. I have tried different character encoding selections in Firefox 3.5.5 and Safari 4.0.4 on Mac 10.6 and Firefox 3.0.12 on Centos 5.3. 2. I have attached cp437.html that displays the expected line drawing characters when the character encoding is set to Default in Safari and Western (IBM-850) in Firefox. Note that the page has a META tag that defines charset=ibm437. 3. I have attached mcc.log which is a capture of an application screen with embedded IBM437 line drawing characters. 4. Opening cp437.html with encodings as above, the line drawing characters are displayed as expected. 5. However, a cat off mcc.log within a shellinabox VT100 terminal session gives a different result. What is the expected output? See Screen shot 2009-11-23 at 5.53.01 PM.png What do you see instead? See Screen shot 2009-11-23 at 5.59.57 PM.png What version of the product are you using? On what operating system? Built from 2.10.tar.gz source on CentOS 5.3 Please provide any additional information below. Nov 22, 2009 issue 15 (What values should be used for SELinux (pam_selinux) "contex...) commented on by zod...@gmail.com - I now added a README.Fedora file to the subversion tree. It gives some more hints on how to configure ShellInABox for use on Fedora. I now added a README.Fedora file to the subversion tree. It gives some more hints on how to configure ShellInABox for use on Fedora. Nov 22, 2009 issue 35 (Gentoo gcc 4.3.4 - Linking ascii objects) Status changed by zod...@gmail.com - Thanks for that information. The change is now in the top of the subversion tree. Please let me know, if you have any problems with it. Status: Fixed Thanks for that information. The change is now in the top of the subversion tree. Please let me know, if you have any problems with it. Status: Fixed Nov 22, 2009 r189 (Thanks to Rudolf Spring's help, added support for building o...) committed by zod...@gmail.com - Thanks to Rudolf Spring's help, added support for building on PowerPC architectures. Thanks to Rudolf Spring's help, added support for building on PowerPC architectures. Nov 22, 2009 r188 (Added some documentation explaining how to configure ShellIn...) committed by zod...@gmail.com - Added some documentation explaining how to configure ShellInABox on Fedora. Added some documentation explaining how to configure ShellInABox on Fedora. Nov 22, 2009 issue 35 (Gentoo gcc 4.3.4 - Linking ascii objects) commented on by rudolf.spring - Seems to work - I'm not sure about the -B because it has no impact at all on the ppc platform but it looks much better ;-) Thanks a lot and have a good sleep objcopyflags = case "$(host_cpu)" in \ i[0-9]86) echo '-O elf32-i386 -B i386';; \ x86_64) echo '-O elf64-x86-64 -B i386:x86-64';; \ arm) echo '-O elf32-littlearm -B arm';; \ powerpc) echo '-O elf32-powerpc -B powerpc';; \ esac Seems to work - I'm not sure about the -B because it has no impact at all on the ppc platform but it looks much better ;-) Thanks a lot and have a good sleep objcopyflags = case "$(host_cpu)" in \ i[0-9]86) echo '-O elf32-i386 -B i386';; \ x86_64) echo '-O elf64-x86-64 -B i386:x86-64';; \ arm) echo '-O elf32-littlearm -B arm';; \ powerpc) echo '-O elf32-powerpc -B powerpc';; \ esac Nov 22, 2009 issue 35 (Gentoo gcc 4.3.4 - Linking ascii objects) commented on by zod...@gmail.com - I don't think that ASCII or the fact that you are using Gentoo is the problem here. More likely, the problem is that you are the first reported user to build on a powerpc. You will need to edit Makefile.am and add the missing information to the definition of "objcopyflags". Unfortunately, without having easy access to a powerpc machine with Linux on it, I am not quite sure what needs to be entered here. Try running "objcopy" without any arguments, and it should tell you which build targets it supports. This should help you get started. Once you have a solution, please let me know and I'll add it to the official source tree. I don't think that ASCII or the fact that you are using Gentoo is the problem here. More likely, the problem is that you are the first reported user to build on a powerpc. You will need to edit Makefile.am and add the missing information to the definition of "objcopyflags". Unfortunately, without having easy access to a powerpc machine with Linux on it, I am not quite sure what needs to be entered here. Try running "objcopy" without any arguments, and it should tell you which build targets it supports. This should help you get started. Once you have a solution, please let me know and I'll add it to the official source tree. Nov 22, 2009 issue 35 (Gentoo gcc 4.3.4 - Linking ascii objects) reported by rudolf.spring - What steps will reproduce the problem? gcc version 4.3.4 (Gentoo 4.3.4 p1.0, pie-10.1.5) Linking of ascii text files (cgi_root.html->cgi_root.o, etc.) seems to be a problem in my environment What is the expected output? What do you see instead? ............................... /bin/sh ./libtool --tag=CC --mode=link gcc -g -std=gnu99 -Wall -Os -static -o shellinaboxd shellinaboxd.o externalfile.o launcher.o privileges.o service.o session.o usercss.o shellinabox/cgi_root.o shellinabox/root_page.o shellinabox/vt100.o shellinabox/shell_in_a_box.o shellinabox/styles.o shellinabox/print-styles.o shellinabox/enabled.o shellinabox/favicon.o shellinabox/beep.o liblogging.la libhttp.la -lz -ldl - lutil libtool: link: gcc -g -std=gnu99 -Wall -Os -o shellinaboxd shellinaboxd.o externalfile.o launcher.o privileges.o service.o session.o usercss.o shellinabox/cgi_root.o shellinabox/root_page.o shellinabox/vt100.o shellinabox/shell_in_a_box.o shellinabox/styles.o shellinabox/print-styles.o shellinabox/enabled.o shellinabox/favicon.o shellinabox/beep.o ./.libs/liblogging.a ./.libs/libhttp.a -lz -ldl -lutil /usr/lib/gcc/powerpc-unknown-linux-gnu/4.3.4/../../../../powerpc-unknown-linux- gnu/bin/ld:shellinabox/cgi_root.o: file format not recognized; treating as linker script /usr/lib/gcc/powerpc-unknown-linux-gnu/4.3.4/../../../../powerpc-unknown-linux- gnu/bin/ld:shellinabox/cgi_root.o:1: syntax error collect2: ld returned 1 exit status make[1]: * [shellinaboxd] Error 1 make[1]: Leaving directory `/usr/src/shellinabox-2.10' make: * [all] Error 2 What version of the product are you using? On what operating system? shellinabox-2.10 linux-2.6.30-gentoo-r8 What steps will reproduce the problem? gcc version 4.3.4 (Gentoo 4.3.4 p1.0, pie-10.1.5) Linking of ascii text files (cgi_root.html->cgi_root.o, etc.) seems to be a problem in my environment What is the expected output? What do you see instead? ............................... /bin/sh ./libtool --tag=CC --mode=link gcc -g -std=gnu99 -Wall -Os -static -o shellinaboxd shellinaboxd.o externalfile.o launcher.o privileges.o service.o session.o usercss.o shellinabox/cgi_root.o shellinabox/root_page.o shellinabox/vt100.o shellinabox/shell_in_a_box.o shellinabox/styles.o shellinabox/print-styles.o shellinabox/enabled.o shellinabox/favicon.o shellinabox/beep.o liblogging.la libhttp.la -lz -ldl - lutil libtool: link: gcc -g -std=gnu99 -Wall -Os -o shellinaboxd shellinaboxd.o externalfile.o launcher.o privileges.o service.o session.o usercss.o shellinabox/cgi_root.o shellinabox/root_page.o shellinabox/vt100.o shellinabox/shell_in_a_box.o shellinabox/styles.o shellinabox/print-styles.o shellinabox/enabled.o shellinabox/favicon.o shellinabox/beep.o ./.libs/liblogging.a ./.libs/libhttp.a -lz -ldl -lutil /usr/lib/gcc/powerpc-unknown-linux-gnu/4.3.4/../../../../powerpc-unknown-linux- gnu/bin/ld:shellinabox/cgi_root.o: file format not recognized; treating as linker script /usr/lib/gcc/powerpc-unknown-linux-gnu/4.3.4/../../../../powerpc-unknown-linux- gnu/bin/ld:shellinabox/cgi_root.o:1: syntax error collect2: ld returned 1 exit status make[1]: * [shellinaboxd] Error 1 make[1]: Leaving directory `/usr/src/shellinabox-2.10' make: * [all] Error 2 What version of the product are you using? On what operating system? shellinabox-2.10 linux-2.6.30-gentoo-r8 Nov 22, 2009 issue 32 (Please distribute .deb for 64-bit architecture.) Status changed by zod...@gmail.com - Status: Done Status: Done Nov 21, 2009 r187 (Removed compiler warning when building without SSL support. ) committed by zod...@gmail.com - Removed compiler warning when building without SSL support. Removed compiler warning when building without SSL support. Nov 21, 2009 shellinabox_2.10-1_i386.deb (Pre-built Debian i386 package) file uploaded by zod...@gmail.com - Labels: Type-Package OpSys-Linux Featured Labels: Type-Package OpSys-Linux Featured

issue 35 (Gentoo gcc 4.3.4 - Linking ascii objects) reported by rudolf.spring - What steps will reproduce the problem? gcc version 4.3.4 (Gentoo 4.3.4 p1.0, pie-10.1.5) Linking of ascii text files (cgi_root.html->cgi_root.o, etc.) seems to be a problem in my environment What is the expected output? What do you see instead? ............................... /bin/sh ./libtool --tag=CC --mode=link gcc -g -std=gnu99 -Wall -Os -static -o shellinaboxd shellinaboxd.o externalfile.o launcher.o privileges.o service.o session.o usercss.o shellinabox/cgi_root.o shellinabox/root_page.o shellinabox/vt100.o shellinabox/shell_in_a_box.o shellinabox/styles.o shellinabox/print-styles.o shellinabox/enabled.o shellinabox/favicon.o shellinabox/beep.o liblogging.la libhttp.la -lz -ldl - lutil libtool: link: gcc -g -std=gnu99 -Wall -Os -o shellinaboxd shellinaboxd.o externalfile.o launcher.o privileges.o service.o session.o usercss.o shellinabox/cgi_root.o shellinabox/root_page.o shellinabox/vt100.o shellinabox/shell_in_a_box.o shellinabox/styles.o shellinabox/print-styles.o shellinabox/enabled.o shellinabox/favicon.o shellinabox/beep.o ./.libs/liblogging.a ./.libs/libhttp.a -lz -ldl -lutil /usr/lib/gcc/powerpc-unknown-linux-gnu/4.3.4/../../../../powerpc-unknown-linux- gnu/bin/ld:shellinabox/cgi_root.o: file format not recognized; treating as linker script /usr/lib/gcc/powerpc-unknown-linux-gnu/4.3.4/../../../../powerpc-unknown-linux- gnu/bin/ld:shellinabox/cgi_root.o:1: syntax error collect2: ld returned 1 exit status make[1]: *** [shellinaboxd] Error 1 make[1]: Leaving directory `/usr/src/shellinabox-2.10' make: *** [all] Error 2 What version of the product are you using? On what operating system? shellinabox-2.10 linux-2.6.30-gentoo-r8

What steps will reproduce the problem? gcc version 4.3.4 (Gentoo 4.3.4 p1.0, pie-10.1.5) Linking of ascii text files (cgi_root.html->cgi_root.o, etc.) seems to be a problem in my environment What is the expected output? What do you see instead? ............................... /bin/sh ./libtool --tag=CC --mode=link gcc -g -std=gnu99 -Wall -Os -static -o shellinaboxd shellinaboxd.o externalfile.o launcher.o privileges.o service.o session.o usercss.o shellinabox/cgi_root.o shellinabox/root_page.o shellinabox/vt100.o shellinabox/shell_in_a_box.o shellinabox/styles.o shellinabox/print-styles.o shellinabox/enabled.o shellinabox/favicon.o shellinabox/beep.o liblogging.la libhttp.la -lz -ldl - lutil libtool: link: gcc -g -std=gnu99 -Wall -Os -o shellinaboxd shellinaboxd.o externalfile.o launcher.o privileges.o service.o session.o usercss.o shellinabox/cgi_root.o shellinabox/root_page.o shellinabox/vt100.o shellinabox/shell_in_a_box.o shellinabox/styles.o shellinabox/print-styles.o shellinabox/enabled.o shellinabox/favicon.o shellinabox/beep.o ./.libs/liblogging.a ./.libs/libhttp.a -lz -ldl -lutil /usr/lib/gcc/powerpc-unknown-linux-gnu/4.3.4/../../../../powerpc-unknown-linux- gnu/bin/ld:shellinabox/cgi_root.o: file format not recognized; treating as linker script /usr/lib/gcc/powerpc-unknown-linux-gnu/4.3.4/../../../../powerpc-unknown-linux- gnu/bin/ld:shellinabox/cgi_root.o:1: syntax error collect2: ld returned 1 exit status make[1]: *** [shellinaboxd] Error 1 make[1]: Leaving directory `/usr/src/shellinabox-2.10' make: *** [all] Error 2 What version of the product are you using? On what operating system? shellinabox-2.10 linux-2.6.30-gentoo-r8

Yesterday

Last 7 days

Last 30 days