Joshua1909 / eapeak

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

EAPeak Ncurses Fail When Running in an SSH Session #1

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Install EAPeak from download or from hg repo on "EAPbox"
2. SSH into EAPbox from another machine (using OSX in this case [tried with 
both Terminal.app and iTerm2) 
3. Run ./eapeak -l -c -i mon0

What is the expected output? What do you see instead?

Getting the error: 

 => Traceback (most recent call last):         
File "./eapeak", line 297, in <module>                                          

main()
File "./eapeak", line 178, in main 
errCode = eapeakParser.initCurses()  
"/usr/local/lib/python2.6/dist-packages/eapeak/parse.py", line 481, in 
initCurses                                                                      

                   curses.curs_set(0)   
_curses.error: curs_set() returned ERR

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

Backtrack 5 (Linux bt 2.6.39.4 #1 SMP Wed Aug 17 21:42:30 EDT 2011 x86_64 
GNU/Linux)
Python: 2.6.5   (2.6.5-0ubuntu1)
Scapy Community (commit: 120, update: 23)
python-m2crypto (0.20.1-1ubuntu2)

Versions:
+ EAPeak-v0.1.4_ToorCon_2011.tar.bz2 
+ hg (commit: 10)

Please provide any additional information below.

Discovered this running BT5 in a VM; didn't want to run X, so I setup 
networking and SSH'd in to run EAPeak.

+ After it craps out, it corrupts my bash terminal (see attachment for what 
appears in my SSH console) 
+ Works fine in konsole in an X session on the BT5 VM

Not really sure what the problem is (I'm a Python guy but my (n)curses fu is 
non-existent :/

Let me know if there is any additional information. 

Best

Original issue reported on code.google.com by i...@neopwn.com on 21 Oct 2011 at 5:16

Attachments:

GoogleCodeExporter commented 9 years ago

Original comment by zeroStei...@gmail.com on 25 Oct 2011 at 2:00

GoogleCodeExporter commented 9 years ago
Fixed in changeset 74:1beabe814fa8, tested on an OSX 10.5 machine with 
Terminal.app

Bug was due to the terminal not supporting setting the cursor's visibility 
within the Curses UI via a call to curs_set.

See http://docs.python.org/library/curses.html#curses.curs_set for more details.

On a side note, terminals that do not support colors will still throw an error, 
I'll fix this if EAPeak is used widely enough that this becomes an issue.

Original comment by zeroStei...@gmail.com on 30 Oct 2011 at 8:15