By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.

Bug 1532

Summary: Running nmap causes desktop sharing to crash and no backtrace is produced
Product: TDE Reporter: Darrell <darrella>
Component: tdenetworkAssignee: Timothy Pearson <kb9vqf>
Status: NEW ---    
Severity: normal CC: bugwatch, darrella, kb9vqf
Priority: P5    
Version: R14.0.x [Trinity]   
Hardware: Other   
OS: Linux   
Compiler Version: TDE Version String:
Application Version: Application Name:

Description Darrell 2013-05-29 15:12:40 CDT
Very recent GIT, Slackware 14.0.

Run the following command from within a terminal window:

nmap -sV -A -v localhost

A krfb system tray popup dialog appears, "Desktop sharing: The remote user has closed the connection." Wait for the popup to time out. A crash handler dialog appears. The title bar contains "unknown." The description is "The application unknown (krfb) crashed and caused the signal 11 (SIGSEGV)." Selecting the Backtrace tab results in a message that the backtrace is unusable.

Although nmap is not a Trinity app, I don't think the port test should cause a crash of any kind.
Comment 1 Darrell 2013-08-07 21:28:53 CDT
Actually, just running 'nmap localhost' is sufficient to cause the empty kcrash.

The problem is caused when nmap scans ports 5800 and 5900, which are used by the KDED TDE Internet Daemon. When that daemon is manually stopped, the nmap scan does not produce the empty kcrash.
Comment 2 Darrell 2013-11-20 23:42:06 CST
I compiled TQt3 without -glibmainloop (defaulting to TQt3 internal main event loop). Running 'nmap localhost' no longer causes a spurious kcrash.
Comment 3 Darrell 2013-11-21 00:16:57 CST
Note: as the problem disappeared when compiling TQt3 without -glibmainloop, this bug report could be related to bug 1583.
Comment 4 Timothy Pearson 2013-11-25 00:25:50 CST
Is this fixed by GIT hash 8dd4535 (from Bug 1583)?
Comment 5 Darrell 2013-11-25 00:47:27 CST
The kcrash no longer occurs.

Testing from the past several days revealed a new quirk.

When I log into Trinity as non-root and from within konsole run 'nmap localhost', I see a system tray "Desktop Sharing" popup notification saying "The remote user has closed the connection." When I log into Trinity as root and run the same test, no system tray popup appears at all. I have tried this on three different systems.

Non-root and root have the same KDED service configurations.

Is a popup notification supposed to appear with root or is non-root supposed to see no popup? What do other people see?
Comment 6 Timothy Pearson 2013-11-27 03:31:33 CST
(In reply to comment #5)
> The kcrash no longer occurs.
> 
> Testing from the past several days revealed a new quirk.
> 
> When I log into Trinity as non-root and from within konsole run 'nmap
> localhost', I see a system tray "Desktop Sharing" popup notification saying
> "The remote user has closed the connection." When I log into Trinity as root
> and run the same test, no system tray popup appears at all. I have tried this
> on three different systems.
> 
> Non-root and root have the same KDED service configurations.
> 
> Is a popup notification supposed to appear with root or is non-root supposed to
> see no popup? What do other people see?

The notification should appear in all cases as far as I can tell; as soon as the remote socket is connected (even if no data is transmitted yet) the user should be informed.
Comment 7 Darrell 2013-11-27 10:17:22 CST
Hmm. When I use krdc/krfb to connect to a remote system where root is logged into Trinity, the system tray notification popup appears in root's desktop.

Can you confirm that 'nmap localhost' results in a popup for non-root but not for root?
Comment 8 Darrell 2014-12-19 13:32:42 CST
>The notification should appear in all cases as far as I can tell; as soon as
>the remote socket is connected (even if no data is transmitted yet) the user
>should be informed
The popup is a nuisance. I have a conky config file that runs 'nmap -p 5900 localhost' to inform customers when they have desktop sharing enabled. Just basic security awareness to help them as they don't use desktop sharing unless they ask me to help. Only TDE shows this nuisance popup. Mate, Cinnamon, and GNOME do not. The other desktops show a popup only when an actual connection is made and never with the conky nmap port scan.

I understand the popup when an actual connection is made but not for a port scan. Seems TDE is responding to everything rather than distinguish an actual connection.
Comment 9 Darrell 2014-12-22 15:53:41 CST
I do not understand the difference, but changing the conkyrc nmap -p scan to port 5800 rather than 5900 stops the nuisance popups.
Comment 10 Darrell 2015-11-05 14:13:38 CST
The popups resulting from nmap scans is quite the nuisance. This bug and other VNC related bugs has pretty much halted my usage of TDE.