google-code-export / web-shell

Automatically exported from code.google.com/p/web-shell
1 stars 1 forks source link

having issues with webshell.py executing without errors #22

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. attempt to connect to port 8022 via SSL on browser (iPhone + Safari)
2. script kicks out the following immediately:

----
Exception happened during processing of request from ('192.168.1.202', 49236)
Traceback (most recent call last):
  File "/usr/local/lib/python2.4/SocketServer.py", line 222, in handle_request
    self.process_request(request, client_address)
  File "/usr/local/lib/python2.4/SocketServer.py", line 241, in process_request
    self.finish_request(request, client_address)
  File "/usr/local/lib/python2.4/SocketServer.py", line 254, in finish_request
    self.RequestHandlerClass(request, client_address, self)
  File "/usr/local/lib/python2.4/SocketServer.py", line 521, in __init__
    self.handle()
  File "/usr/local/lib/python2.4/BaseHTTPServer.py", line 316, in handle
    self.handle_one_request()
  File "/usr/local/lib/python2.4/BaseHTTPServer.py", line 310, in handle_one_request
    method()
  File "./webshell.py", line 1258, in do_GET
    if multiplex.proc_keepalive(sid, w, h):
  File "./webshell.py", line 1026, in __call__
    r = self.orig(*l)
  File "./webshell.py", line 1065, in proc_keepalive
    return self.proc_spawn(sid)
  File "./webshell.py", line 1026, in __call__
    r = self.orig(*l)
  File "./webshell.py", line 1130, in proc_spawn
    0, 0
OverflowError: signed integer is greater than maximum
----

What version of the product are you using? On what operating system?

This is webshell 0.9.2 on FreeBSD 6.2-RELEASE

Please provide any additional information below.

I updated ports and built the package for py-openssl which in turn built python 
2.4.4:

# pkginfo
...edit...
py24-openssl-0.6    Python interface to the OpenSSL library
python24-2.4.4      An interpreted object-oriented programming language

My understanding is that FreeBSD 6 is using OpenSSL and I have checked that I 
have it enabled in 
rc.conf, I also regularly SSH into this machine.  There is no Apache install on 
this machine but my 
understanding as well is that the web interface in webshell does not depend on 
that.

I have taken a look through sshd.conf and ssh.conf and haven't seen anything 
that seems too 
unusual.

Any help appreciated!

Thanks -
d.

Original issue reported on code.google.com by dylan.g...@gmail.com on 29 Jul 2007 at 3:01

GoogleCodeExporter commented 9 years ago
do you have an AMD64? If that is so, it is a bug in the linux kernel. Next 
release should have a fix.
Marc.-

Original comment by mre...@gmail.com on 30 Jul 2007 at 6:42

GoogleCodeExporter commented 9 years ago
Thanks very much for all the work you're doing on this.  I apologize I always 
forget that my box this is 
running on is SPARC64 - a Sun Netra.  But everything is current and works well, 
I build from ports and not 
binaries so if you're abstracted back to python I would think it wouldn't be an 
issue (the processor / arch).  Do 
you know though if anyone is running this on FreeBSD 6.2?

So the changes you made did affect a couple of things.  Each time I log in and 
accept the cert the error comes 
up - but  i get to the keypad and there is no login window though or anything.  
There seems to be no 
response at that point.  But if I do connect again on end it will spawn another 
process and they are all sitting 
idle when i look at what processes are up.  And ^C exiting twice to kill the 
script then kills each process and 
they seem to close without holding ports open when i look at sockstat.

I know you're slammed probably and thank you again for all the work on this 
project.  It is sorely needed and I 
have this server being used a lot lately so I really thank you for this app!

Best,
d.

Original comment by dylan.g...@gmail.com on 30 Jul 2007 at 8:16

GoogleCodeExporter commented 9 years ago
All is well with new version. Having small SSL cert issue but checking it out.

Thank you again.

Original comment by dylan.g...@gmail.com on 31 Jul 2007 at 5:51