ommand=/sbin/shutdown -p now
> RebootCommand=/sbin/shutdown -r now
>
> [security]
> DisallowTCP=false
>
> [xdmcp]
> DisplaysPerHost=1
> Enable=true
>
> [chooser]
>
> [debug]
> # Uncomment the line below to turn on debugging
> #Enable=true
Hi Herbert,
On Mi 13 Mai 2020 07:28:52 CEST, herbert wrote:
Package: xorg-server
Version: 2:1.20.4-1
Severity: wishlist
As it is, when an XDMCP session is used over TCP keepalive packets
are periodically sent and the session is torn down if no replies
come back.
During a transient network
Package: xorg-server
Version: 2:1.20.4-1
Severity: wishlist
As it is, when an XDMCP session is used over TCP keepalive packets
are periodically sent and the session is torn down if no replies
come back.
During a transient network failure, this causes an X session that
could otherwise survive
Package: xdm
Version: 1:1.1.11-3
Severity: normal
Dear Maintainer,
When configured for XDMCP (to LISTEN on UDP port 177), xdm also opens
a random, high-numbered TCP (tcp6, IPv6) port to LISTEN. Currently my
xdm shows:
root@p639:~# netstat -anp | grep xdm
tcp6 0 0 :::51359
Your message dated Sun, 12 Apr 2015 08:54:32 +0200
with message-id <20150412085432.5d5650f0@s5.lokal>
and subject line done
has caused the Debian Bug report #761398,
regarding Xorg refuses remote login over XDMCP with Xephyr
to be marked as done.
This means that you claim that the probl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Now I tried this recipe:
http://www.ibm.com/developerworks/library/os-multiuserloginsvnc/index.html
[see below]
It works fine for me with tightvncserver, but I had to restart the remote
server once in
order to be able to log in to it with xtightvnc
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
As reported earlier today, I wanted to try out remote XDMCP-login using gdm3,
which was
not workable at all, see there: 761
Package: xserver-xorg-core
Version: 2:1.16.0-1
Severity: important
Dear Maintainer,
it is not possible to use X server as XDMCP client. Running:
root@Terminal:~# X -query
leads to crash during session initialization.
is properly set workstation with working XDMCP protocol.
Looking to
Your message dated Sun, 13 Jul 2014 14:29:14 +0200
with message-id <20140713122914.gx3...@betterave.cristau.org>
and subject line Re: Bug#691844: Fix released
has caused the Debian Bug report #691844,
regarding xauth: Failed X11 forwarding when using GDM via XDMCP
to be marked as done.
This
Processing commands for cont...@bugs.debian.org:
> clone 691844 -1
Bug #691844 [xauth] xauth: Failed X11 forwarding when using GDM via XDMCP
Bug 691844 cloned as bug 692579
> reassign -1 gdm3
Bug #692579 [xauth] xauth: Failed X11 forwarding when using GDM via XDMCP
Bug reassigned from p
Le dimanche 04 novembre 2012 à 01:01 +0100, Julien Cristau a écrit :
> > When using GDM via XDMCP, for examle when accessing GDM via
> > vncserver->XDMCP->localhost, ssh is no longer able to forward X11.
> >
> > Invalid MIT-MAGIC-COOKIE-1 keyxter
On Sun, Nov 04, 2012 at 01:01:12AM +0100, Julien Cristau wrote:
> On Tue, Oct 30, 2012 at 10:41:35 +0100, Stefan Voelkel wrote:
>
> > Package: xauth
> > Version: 1:1.0.4-1
> > Severity: normal
> > Tags: upstream patch
> >
> >
> > When using
On Tue, Oct 30, 2012 at 10:41:35 +0100, Stefan Voelkel wrote:
> Package: xauth
> Version: 1:1.0.4-1
> Severity: normal
> Tags: upstream patch
>
>
> When using GDM via XDMCP, for examle when accessing GDM via
> vncserver->XDMCP->localhost, ssh is no longer able to f
Package: xauth
Version: 1:1.0.4-1
Severity: normal
Tags: upstream patch
When using GDM via XDMCP, for examle when accessing GDM via
vncserver->XDMCP->localhost, ssh is no longer able to forward X11.
Invalid MIT-MAGIC-COOKIE-1 keyxterm Xt error: Can't open display:
loc
Your message dated Thu, 7 Apr 2011 03:56:32 +0200
with message-id <20110407015632.ga2...@debian.org>
and subject line Re: Bug#621423: /usr/bin/xrdb: xdmcp rogue hostname security
has caused the Debian Bug report #621423,
regarding /usr/bin/xrdb: xdmcp rogue hostname security
to be marked a
be root access on the
server. Debian seems to have flagged this as low priority because xdmcp
is not enabled in default setup; though the issue is exploitable via
dhcp also.
In my environment we use xdmcp for users to log in to our servers.
Could I please have ideas about workaround protection?
I
Your message dated Fri, 11 Feb 2011 21:12:29 +0100
with message-id <4d55982d.2070...@debian.org>
and subject line Bug#612190: Removed package(s) from unstable
has caused the Debian Bug report #525430,
regarding X crashes when using gdmchooser to initiate XDMCP connection.
to be marked a
Seb James (24/04/2009):
> This bug occurs when using the radeonhd X.org driver on my Lenny
> machine, dellbuntu. It does not occur when using the radeon X.org
> driver.
Great. :) -radeonhd is deprecated and will be removed, please keep
using -radeon.
KiBi.
signature.asc
Description: Digital si
Processing commands for cont...@bugs.debian.org:
> reassign 525430 xserver-xorg-video-radeonhd
Bug#525430: X crashes when using gdmchooser to initiate XDMCP connection.
Bug reassigned from package `gdm' to `xserver-xorg-video-radeonhd'.
> thanks
Stopping processing here.
Plea
reassign 525430 xserver-xorg-video-radeonhd
thanks
Le vendredi 24 avril 2009 à 15:36 +0100, Seb James a écrit :
> This bug occurs when using the radeonhd X.org driver on my Lenny
> machine, dellbuntu. It does not occur when using the radeon X.org driver.
If it’s a X crash, it’s likely a X bug. E
reassign 449164 gdm
thank you
Juergen Kosel wrote:
> Hello,
>
> Brice Goglin schrieb:
> > Juergen Kosel wrote:
> >> Package: xorg
> >> Version: 1:7.1.0-19
> >> Severity: normal
> >>
> >> Hello,
> >>
> >> after adding
Processing commands for [EMAIL PROTECTED]:
> reassign 449164 gdm
Bug#449164: xorg: IPv6 addresses in hosts breaks XDMCP logins
Bug reassigned from package `xorg' to `gdm'.
> thank you
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking syst
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
Brice Goglin schrieb:
> Juergen Kosel wrote:
>> Package: xorg
>> Version: 1:7.1.0-19
>> Severity: normal
>>
>> Hello,
>>
>> after adding the IPv6 addresses of my machines to /etc/hosts, login by X
Juergen Kosel wrote:
> Package: xorg
> Version: 1:7.1.0-19
> Severity: normal
>
> Hello,
>
> after adding the IPv6 addresses of my machines to /etc/hosts, login by XDMCP
> becomes impossible. Either the server doesn't provide the greeter windows
> (with login
Package: xorg
Version: 1:7.1.0-19
Severity: normal
Hello,
after adding the IPv6 addresses of my machines to /etc/hosts, login by XDMCP
becomes impossible. Either the server doesn't provide the greeter windows
(with login prompt) at all. Or user becomes imediattly logged out again.
The
yManager*setup: /usr/X11R6/lib/X11/xdm/Xsetup
DisplayManager*startup: /usr/X11R6/lib/X11/xdm/Xstartup
DisplayManager*reset: /usr/X11R6/lib/X11/xdm/Xreset
!
DisplayManager*resources: /usr/X11R6/lib/X11/xdm/Xresources
DisplayManager*session: /usr/X11R6/lib/X11/
Hi,
About 6 years ago, you reported a bug to the Debian BTS regarding
corrupted XDMCP packets breaking remote login in xdm with a non-standard
config. Did you reproduce this problem recently? With Xorg/Etch? If not,
I will close this bug in the next weeks.
Thanks,
Brice
--
To UNSUBSCRIBE
Your message dated Thu, 01 Mar 2007 23:16:05 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#187148: xdm: only answers one XDMCP request and then shuts
down socket
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been
Your message dated Fri, 26 Jan 2007 23:41:59 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#251037: Strange xdmcp behavior, maybe a trojan horse?
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this
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 thi
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.
Thanks,
Brice
--
To UNSUBSCRIBE, email to [EMAIL PROTECT
Author: dnusinow
Date: 2005-10-30 20:46:33 -0500 (Sun, 30 Oct 2005)
New Revision: 803
Modified:
branches/modular/lib/Xdmcp/aclocal.m4
branches/modular/lib/Xdmcp/configure
Log:
Re-run autogen.sh with xorg m4 macros installed locally
Modified: branches/modular/lib/Xdmcp/aclocal.m4
Author: dnusinow
Date: 2005-10-25 17:13:43 -0500 (Tue, 25 Oct 2005)
New Revision: 785
Modified:
branches/modular/lib/Xdmcp/debian/
Log:
Pull in xsfbs
Property changes on: branches/modular/lib/Xdmcp/debian
___
Name: svn:externals
Author: dnusinow
Date: 2005-10-25 17:11:24 -0500 (Tue, 25 Oct 2005)
New Revision: 784
Added:
branches/modular/lib/Xdmcp/A8Eq.c
branches/modular/lib/Xdmcp/AA16.c
branches/modular/lib/Xdmcp/AA32.c
branches/modular/lib/Xdmcp/AA8.c
branches/modular/lib/Xdmcp/Alloc.c
branches/modular
0 is being
disabled
Mon Aug 22 23:22:00 2005 xdm info (pid 1172): shutting down
Mon Aug 22 23:22:01 2005 xdm info (pid 1172): exiting
Mon Aug 22 23:22:03 2005 xdm info (pid 21765): starting
Mon Aug 22 23:22:03 2005 xdm error (pid 21765): XDMCP socket creation
failed: Address family not supported by pr
Author: fabbione
Date: 2004-10-23 23:36:46 -0500 (Sat, 23 Oct 2004)
New Revision: 102
Modified:
xorg-lib-xdmcp/trunk/debian/CHANGESETS
xorg-lib-xdmcp/trunk/debian/libxdmcp-dev.lintian
xorg-lib-xdmcp/trunk/debian/libxdmcp6.lintian
Log:
* Add Id keyword to lintian overrides.
Modified
Author: fabbione
Date: 2004-10-23 22:53:55 -0500 (Sat, 23 Oct 2004)
New Revision: 95
Modified:
xorg-lib-xdmcp/trunk/debian/CHANGESETS
xorg-lib-xdmcp/trunk/debian/libxdmcp6.postrm
Log:
* Fix call to ldconfig in postrm.
Modified: xorg-lib-xdmcp/trunk/debian/CHANGESETS
Author: fabbione
Date: 2004-10-23 06:55:34 -0500 (Sat, 23 Oct 2004)
New Revision: 92
Added:
xorg-lib-xdmcp/trunk/debian/libxdmcp6.postinst
xorg-lib-xdmcp/trunk/debian/libxdmcp6.postrm
Modified:
xorg-lib-xdmcp/trunk/debian/CHANGESETS
Log:
* Add libxdmcp6.postinst and postrm.
For some
Author: fabbione
Date: 2004-10-22 12:07:55 -0500 (Fri, 22 Oct 2004)
New Revision: 88
Removed:
xorg-lib-xdmcp/trunk/debian/patches/008_fix_xgetpw_macro.diff
Modified:
xorg-lib-xdmcp/trunk/debian/CHANGESETS
xorg-lib-xdmcp/trunk/debian/control
xorg-lib-xdmcp/trunk/debian/rules
Log
Author: fabbione
Date: 2004-10-22 03:00:38 -0500 (Fri, 22 Oct 2004)
New Revision: 83
Added:
xorg-lib-xdmcp/trunk/debian/libxdmcp-dev.install
xorg-lib-xdmcp/trunk/debian/libxdmcp-dev.lintian
xorg-lib-xdmcp/trunk/debian/libxdmcp6.install
xorg-lib-xdmcp/trunk/debian/libxdmcp6.lintian
On Sun, May 30, 2004 at 01:00:23AM +0200, Bartłomiej Ochman wrote:
> First thing first, in my opinion xdm works perfectly well in all those
> situations. I think I understand now *why* it behaves this way. And what's
> worst, it can be assumed as the right behavior. :-(
Hmmm. :(
[...]
> So Xse
sed by Xserver
and RFC1122, where "weak end host" is defined. During connection setup,
Xserver sends its IP address in a XDMCP packet to a xdm process on a remote
host. But which IP should be sent by a multihomed Xserver? The logic says,
the IP of the interface which leads to a remote
On Thu, May 27, 2004 at 08:12:30PM +0200, Bartłomiej Ochman wrote:
> 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.
Does it soun
at an other ip than reported.
>
> [...]
> >You confuse me further. Why is an X server on your local machine trying
> >to connect via XDMCP to a remote machine, if you're not the person
> >instructing it to do so?
> >
> >Do you have a guest on your machine?
ooks to me like you
launched a local X server, asking a remove XDM process to manage it, but
the remote XDM rejected your connection, so the X server exited.
Yes, but both my Xserver and xdm process runs at an other ip than reported.
[...]
You confuse me further. Why is an X server on your local
ot;xserver-common" do you believe to be at fault for the behavior you are
seeing?
> I was unable to connect to a remote xdm, but only when it is outside a
> broadcast domain.
Forgive my ignorance, but what is a "broadcast domain"?
> X crashes with a message:
>
&g
Processing commands for [EMAIL PROTECTED]:
> tag 251037 + moreinfo
Bug#251037: Strange xdmcp behavior, maybe a trojan horse?
There were no tags set.
Tags added: moreinfo
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system adminis
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
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
-GNU-libc systems) in XFree86 X server by including correct header =
file
for ntohl() prototype (thanks, Erik Andersen). (Closes: #216806)
.
* Restore original xdm behavior of interpreting an XDMCP request port of
zero (the default) as an instruction not to open a port at all.
Equi
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.7.95.1
> retitle 239341 xdm: opens TCP port for XDMCP connections even when configured
> not to
Bug#239341: xdm: unknown purpose tcp port open
Changed Bug title.
> sev
, presenting the
> host itself and all other machines willing to serve. That worked
> well for several years. Now, the chooser still appears, but the
> login service is unavailable.
>
> Debugging showed that the xdm is (in contrast to older versions)
> willing to answer only one xdmcp
, presenting the
> host itself and all other machines willing to serve. That worked
> well for several years. Now, the chooser still appears, but the
> login service is unavailable.
>
> Debugging showed that the xdm is (in contrast to older versions)
> willing to answer only one xdmcp
veral years. Now, the chooser still appears, but the
login service is unavailable.
Debugging showed that the xdm is (in contrast to older versions)
willing to answer only one xdmcp request and then shuts down
the xdmcp socket (i.e. binds the socket to the Xserver, so it
doesn't accept oth
veral years. Now, the chooser still appears, but the
login service is unavailable.
Debugging showed that the xdm is (in contrast to older versions)
willing to answer only one xdmcp request and then shuts down
the xdmcp socket (i.e. binds the socket to the Xserver, so it
doesn't accept oth
lt;[EMAIL PROTECTED]>
Date: Fri, 11 Oct 96 18:42 BST
From: Ian Jackson <[EMAIL PROTECTED]>
To: Debian bugs submission address <[EMAIL PROTECTED]>
Subject: XDMCP problem with multihomed X servers (design error?)
Package: xbase
Version: 3.1.2-9
I have an X server running on a machine wi
42 BST
Message-Id: <[EMAIL PROTECTED]>
Date: Fri, 11 Oct 96 18:42 BST
From: Ian Jackson <[EMAIL PROTECTED]>
To: Debian bugs submission address <[EMAIL PROTECTED]>
Subject: XDMCP problem with multihomed X servers (design error?)
Package: xbase
Version: 3.1.2-9
I have an X server r
he loadable
locales (#A.855 Mark Robinson).
+ Fix wrong check in Xaw when rebuilding the line table. If the width
of a line becomes smaller, it should clear to eol. (Paulo Cesar Pereira
de Andrade)
+ In the X server, permit XDM-AUTHENTICATION-1 without also requiring
able
locales (#A.855 Mark Robinson).
+ Fix wrong check in Xaw when rebuilding the line table. If the width
of a line becomes smaller, it should clear to eol. (Paulo Cesar Pereira
de Andrade)
+ In the X server, permit XDM-AUTHENTICATION-1 without also requiring
ons, either of which could be
local or remote.
/etc/gdm/gdm.conf:
[servers] comment out all lines (so gdm doesn't spawn X on its own)
[xdmcp] Enable=true; DisplaysPerHost=2
[chooser] Hosts=comma,separated,list,including,localhost; Broadcast=false
/etc/hosts.allow and hosts.deny:
Guys, pardon me if I am not asking the right question in the right mailing
list. I am running 3.0 on my ULTRA 5 sparc. I just upgraded :) But I want
to use X :1 -query ipaddress -once & etc to connect to other better
machines. When I was using RH7.2/7.3 I added the above line to the
/etc/inittab fi
Hopes this helps:
$ man Xserver
...
XDMCP OPTIONS
X servers that support XDMCP have the following options.
See the X Display Manager Control Protocol specification
for more information.
-query host-name
Enable XDMCP and send
Hopes this helps:
$ man Xserver
...
XDMCP OPTIONS
X servers that support XDMCP have the following options.
See the X Display Manager Control Protocol specification
for more information.
-query host-name
Enable XDMCP and
ient to make it ask for a login with XDMCP. Can anyone point me
> in the direction of a package or some docs?
Replying to myself, for the others that were wondering, after some help
and some looking around on the web, I noticed there is actually a XDMCP
HOWTO (part of the LDP Howto's, means
ient to make it ask for a login with XDMCP. Can anyone point me
> in the direction of a package or some docs?
Replying to myself, for the others that were wondering, after some help
and some looking around on the web, I noticed there is actually a XDMCP
HOWTO (part of the LDP Howto's, means
I want to set up an old Pentium 120 as an X terminal, to log in remotely
on my desktop. I have read some documentation, and figured out that one
of the ?dm packages does the serving, but I cannot figure out what to do
on the client to make it ask for a login with XDMCP. Can anyone point me
in the
I want to set up an old Pentium 120 as an X terminal, to log in remotely
on my desktop. I have read some documentation, and figured out that one
of the ?dm packages does the serving, but I cannot figure out what to do
on the client to make it ask for a login with XDMCP. Can anyone point me
in the
67 matches
Mail list logo
