vermaneerajin / shellinabox

Automatically exported from code.google.com/p/shellinabox
Other
0 stars 0 forks source link

FC15 & shellinabox: stop working ( README.fedora not help ) #136

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?

1. use any fc15

cat /etc/redhat-release
Fedora release 15 (Lovelock)

Linux xxx.hidden.domain  2.6.32-028stab091.2-ent #1 SMP Fri Jun 3 
01:00:01 MSD 2011 i686 i686 i386 GNU/Linux

1a. selinux been not active

2. install shellinabox-2.10- svn rev239 or older

3. try login http://localhost:4200

What is the expected output?

 Expected to login .
 Has worked on fc13 ->> after upgrade to fc15 stop working

 What do you see instead?

see attachment

Original issue reported on code.google.com by rnskl...@web.de on 1 Sep 2011 at 6:10

Attachments:

GoogleCodeExporter commented 8 years ago
Without tracing through sub-processes, you won't be able to make sense of this 
log file. It just prints "forkpty() failed", which could have all sorts of 
different reasons.

Original comment by zod...@gmail.com on 1 Sep 2011 at 6:33

GoogleCodeExporter commented 8 years ago
helo Zod...

Been rev 239 code of shellinabox ready for sub-process trace with 
http://valgrind.org ś software ?

I'll give it an try.

best regards

Original comment by rnskl...@web.de on 2 Sep 2011 at 7:39

GoogleCodeExporter commented 8 years ago
ok and as well i'll deliver that one :
http://fedoraproject.org/wiki/StackTraces
..

Original comment by rnskl...@web.de on 2 Sep 2011 at 7:50

GoogleCodeExporter commented 8 years ago
GDB stracktrace not possible as shellinabox  has no debug symbol options i.e no 
./configure --enable-debug 

Original comment by rnskl...@web.de on 9 Sep 2011 at 5:19

GoogleCodeExporter commented 8 years ago
It builds everything with "-g" by default. No need to set any options.

Original comment by zod...@gmail.com on 9 Sep 2011 at 5:23

GoogleCodeExporter commented 8 years ago
the default fedora rpms have no -g enabled.

http://gcc.gnu.org/onlinedocs/gcc/Debugging-Options.html helped 
 CFLAGS="-ggdb -g" ;./configure --prefix=/usr

but :
(gdb) run
Starting program: /root/rpmbuild/BUILD/shellinabox-2.10/shellinaboxd
[Thread debugging using libthread_db enabled]
Cannot find new threads: generic error
Missing separate debuginfos, use: debuginfo-install glibc-2.14-5.i686 
keyutils-libs-1.2-7.fc15.i686 krb5-libs-1.9.1-5.fc15.i686 
libcom_err-1.41.14-2.fc15.i686 libselinux-2.0.99-4.fc15.i686 
openssl-1.0.0e-1.fc15.i686 openssl-devel-1.0.0e-1.fc15.i686 
zlib-1.2.5-3.fc15.i686
(gdb)

... 

Original comment by rnskl...@web.de on 9 Sep 2011 at 5:34

GoogleCodeExporter commented 8 years ago
ok got that installed

(gdb) run
Starting program: /root/rpmbuild/BUILD/shellinabox-2.10/shellinaboxd
[Thread debugging using libthread_db enabled]
Cannot find new threads: generic error
(gdb)

how i solve that ?

i' m  not an Coder

Original comment by rnskl...@web.de on 9 Sep 2011 at 5:41

GoogleCodeExporter commented 8 years ago
I would recommend not building the RPM while debugging. Instead, just build the 
source tree that you can check out from Subversion.

./configure && make

should do the trick.

Original comment by zod...@gmail.com on 9 Sep 2011 at 5:46

GoogleCodeExporter commented 8 years ago
NO that don´t solve it.

(gdb)  run -d -n -v -t -u root
Starting program: /root/rpmbuild/BUILD/shellinabox-2.10/shellinaboxd -d -n -v 
-t -u root
[Thread debugging using libthread_db enabled]
Cannot find new threads: generic error
(gdb)  thread apply all bt full
Cannot find new threads: generic error
(gdb)

 I can offer you to let you temporarly login to the box

please email me privatly email to technik at remsnet dot de

regards

Horst Venzke

Original comment by rnskl...@web.de on 9 Sep 2011 at 6:06

GoogleCodeExporter commented 8 years ago
ok i may think i looked at the wrong way.

the apache part is the issue.

mod_security stops shellinabox from working ;(

Original comment by rnskl...@web.de on 9 Sep 2011 at 6:58