Bug#251037: Strange xdmcp behavior, maybe a trojan horse?

On Fri, Jan 26, 2007 at 10:25:56PM +0100, Brice Goglin wrote: > Hi, > > About 3 years ago, you reported a bug to the Debian BTS regarding a > strange xdmcp behavior, possibly similar to a "trojan horse". > Did you reproduce this problem recently? If not, I will close this bug > in the next weeks.

Bug#251037: Strange xdmcp behavior, maybe a trojan horse?

Branden Robinson wrote: Hello, That's probably a bug. It may have something to do with: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1985 *That* bug has been open for over 8 years. :( [and from another mail]: > Does it sound like this one?: > > http://bugs.debian.org/cgi-bin/bugreport.c

Bug#251037: Strange xdmcp behavior, maybe a trojan horse?

Branden Robinson wrote: I am having some difficulty understanding your report. :-( First, why did you file this bug against "xserver-common"? I meant "xserver-xfree86", but... but... Forgive my ignorance, but what is a "broadcast domain"? "[...] A broadcast domain is the set of all devi

Bug#251037: More info on strange xdmcp behavior

Hello, I've discovered, what are those IPs, they were on my lo:1...lo:5 set by some software I use to block access from there. But then, why has it used them instead of outgoing eth0? I'd consider it still a bug. Regards, BO

Bug#251037: Strange xdmcp behavior, maybe a trojan horse?

Package: xserver-common Version: 4.3.0.dfsg.1-1 I was unable to connect to a remote xdm, but only when it is outside a broadcast domain. X crashes with a message: Fatal server error: XDMCP fatal error: Session failed Session failed for display 194-237-107-43.customer.telia.com:9: can