Nmap Development mailing list archives

Re: zenmap as root error


From: eldraco <eldraco () gmail com>
Date: Fri, 11 Apr 2008 13:26:06 -0300

Hi list, 

Aaron, did you remember to execute 'xhost +' as a normal user before trying 
zenmap as root?

This is what it means "refused by server" in your error.

If I don't allow other users to connect to my X as a normal user, even root 
can't connect.

For me this is how is happening now:

1- 
#zenmap
Segmentation Fault

2- 
# export DISPLAY=:0
# zenmap
(...)
Segmentation Fault

3- 
$ xhost +
# export DISPLAY=:0
#zenmap

it works......


Cheers.

sebas







El Friday 11 April 2008 05:17:03 Diman Todorov escribió:
On Apr 10, 2008, at 4:25 PM, Aaron Leininger wrote:
I apologize for the delay in getting back to you all on this, my
day job has been overwhelming lately.

I tried your suggestion with the following result:
nonroot$ sudo su -
myrootprompt# export DISPLAY=:0
myrootprompt# zenmap
Xlib: connection to ":0.0" refused by server
Xlib: Invalid MIT-MAGIC-COOKIE-1 key
Segmentation fault

I did some digging on this error in google and I found a response
suggesting the error stems from trying to run something in an x-
session that is owned by another user.

I opened a root-shell directly and ran zenmap again
myrootprompt# zenmap
With the result that it opened normally.

Can anyone tell me why I am seeing this behavior? Why does zenmap
segmentation fault out if I open a normal shell and run: sudo
zenmap but if I open a root shell, it launches fine. This seems odd
to me.

it is odd :) It is definitely a bug. Maybe the GSoCers will get
around to fixing that.

cheers,
diman

_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://SecLists.Org



-- 
Ing. Sebastián García
http://minsky.surfnet.nl:11371/pks/lookup?op=get&search=0x3E42ED27F864EDE6

_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://SecLists.Org


Current thread: