Bug#836586: unknown external IP in xrdp.log after upgrade?!?

2016-09-07 Thread Dominik George
Control: forwarded -1 https://github.com/neutrinolabs/xrdp/issues/421 On Mittwoch, 7. September 2016 12:11:31 CEST Dominik George wrote: > Hang on… this is cool: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=145088=yes > […] And another one:

Bug#836586: unknown external IP in xrdp.log after upgrade?!?

2016-09-07 Thread Dominik George
Hang on… this is cool: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=145088=yes Date: Mon, 29 Apr 2002 20:33:49 -0300 Package: libsnmp4.2 Version: 4.2.4-2 Severity: important The new libwrap stuff for agentX simply does not work. Apr 29 16:33:22 khazad-dum ucd-snmp[13833]: AgentX

Bug#836586: unknown external IP in xrdp.log after upgrade?!?

2016-09-07 Thread Dominik George
Hi, OK, I can actually reproduce the issue - but only on jessie, not on sid (it's also i386 vs. amd64, maybe). Reading code and discussing with upstream now. -nik -- PGP-Fingerprint: 3C9D 54A4 7575 C026 FB17 FD26 B79A 3C16 A0C4 F296 Dominik George · Mobil: +49-1520-1981389 Teckids e.V. ·

Bug#836586: unknown external IP in xrdp.log after upgrade?!?

2016-09-07 Thread Christian Pernegger
2016-09-05 11:01 GMT+02:00 Dominik George : >> Yes, it's connected to the internet, no it's not reachable from >> outside the LAN (on any port). > > Can you please double-check that? I've a dedicated jessie box on firewall / NAT router duty, no forwarded ports. I can't rule

Bug#836586: unknown external IP in xrdp.log after upgrade?!?

2016-09-05 Thread Dominik George
Hi, > > Are you sure this is in fact the one connection you are closing? > > I don't see what else it could be, certainly nothing legitimate. The > only access to the box was me testing xrdp, running a tail -f > alongside. OK. > > > Is the system connected to the internet (and reachable from

Bug#836586: unknown external IP in xrdp.log after upgrade?!?

2016-09-05 Thread Christian Pernegger
> Are you sure this is in fact the one connection you are closing? I don't see what else it could be, certainly nothing legitimate. The only access to the box was me testing xrdp, running a tail -f alongside. > Is the system connected to the internet (and reachable from there on the RDP > port)?

Bug#836586: unknown external IP in xrdp.log after upgrade?!?

2016-09-04 Thread Dominik George
Control: tag -1 + moreinfo Control: tag -1 - security Hi, > [20160904-11:25:17] [INFO ] An established connection closed to > endpoint: NULL:NULL - socket: 11 > [20160904-11:25:17] [DEBUG] xrdp_mm_module_cleanup > [20160904-11:25:17] [INFO ] An established connection closed to > endpoint:

Bug#836586: unknown external IP in xrdp.log after upgrade?!?

2016-09-04 Thread Christian Pernegger
Package: xrdp Version: 0.9.0~20160601+git703fedd-3 Tags: security Hi, while trying to debug why xrdp has stopped working here after the upgrade to 0.9 -- login works fine but dumps one in front of an empty solid teal screen instead of the expected MATE session --, I stumbled across the following