On Tue, Nov 19, 2002 at 09:35:36PM -0500, Edward Guldemond wrote:
> On Wed, Nov 20, 2002 at 02:47:13AM +0100, Olaf Dietsche wrote:
> > Well, it seems I should heed my own advice ;-). man xinit doesn't
> > mention xserverrc, maybe this is a debian thing. But it does mention
> > $HOME/.xserverrc; try
On Tue, Nov 19, 2002 at 09:35:36PM -0500, Edward Guldemond wrote:
> On Wed, Nov 20, 2002 at 02:47:13AM +0100, Olaf Dietsche wrote:
> > Well, it seems I should heed my own advice ;-). man xinit doesn't
> > mention xserverrc, maybe this is a debian thing. But it does mention
> > $HOME/.xserverrc; try
El mié, 20-11-2002 a las 03:35, Edward Guldemond escribió:
> Actually, I noticed something interesting when I was testing this out
> on my home box. When I used "startx", X didn't listen on TCP. When I
> used xinit, it did. I guess that xerverrc only gets read when you use
> startx.
IIRC, they
El mié, 20-11-2002 a las 03:35, Edward Guldemond escribió:
> Actually, I noticed something interesting when I was testing this out
> on my home box. When I used "startx", X didn't listen on TCP. When I
> used xinit, it did. I guess that xerverrc only gets read when you use
> startx.
IIRC, they
On Wed, Nov 20, 2002 at 02:47:13AM +0100, Olaf Dietsche wrote:
> Well, it seems I should heed my own advice ;-). man xinit doesn't
> mention xserverrc, maybe this is a debian thing. But it does mention
> $HOME/.xserverrc; try to link or copy /etc/X11/xinit/xserverrc to your
> home dir as .xserverrc
Edward Guldemond <[EMAIL PROTECTED]> writes:
> On Wed, Nov 20, 2002 at 12:53:27AM +0100, Olaf Dietsche wrote:
>>
>> Look at "man xinit" and "man Xserver". There you will find an option
>> "-nolisten".
>
> In /etc/X11/xinit/xserverrc, I have the following line:
> exec /usr/bin/X11/X -dpi 100 -noli
On Tue, Nov 19, 2002 at 04:51:03PM -0800, Rick Moen wrote:
> Quoting Edward Guldemond ([EMAIL PROTECTED]):
>
> > In /etc/X11/xinit/xserverrc, I have the following line:
> > exec /usr/bin/X11/X -dpi 100 -nolisten tcp
> >
> > So why is X still listening on TCP?
>
> Because xdm/kdm/gdm don't heed /
Quoting Edward Guldemond ([EMAIL PROTECTED]):
> In /etc/X11/xinit/xserverrc, I have the following line:
> exec /usr/bin/X11/X -dpi 100 -nolisten tcp
>
> So why is X still listening on TCP?
Because xdm/kdm/gdm don't heed /etc/X11/xinit/xserverrc, but rather
/etc/X11/xdm/Xservers ?
>> When this
On Wed, Nov 20, 2002 at 02:47:13AM +0100, Olaf Dietsche wrote:
> Well, it seems I should heed my own advice ;-). man xinit doesn't
> mention xserverrc, maybe this is a debian thing. But it does mention
> $HOME/.xserverrc; try to link or copy /etc/X11/xinit/xserverrc to your
> home dir as .xserverrc
On Wed, Nov 20, 2002 at 12:53:27AM +0100, Olaf Dietsche wrote:
> > Now, is there any security implications of having this port open? (I
> > am nmap'ing this box's external Internet interface as it is my ipmasq
> > box.) If so, what files do I have to edit to get rid of it? I don't
> > need X lis
Edward Guldemond <[EMAIL PROTECTED]> writes:
> Starting nmap V. 2.54BETA31 ( www.insecure.org/nmap/ )
> Interesting ports on (removed) (XX.XX.XXX.XX):
> (The 1552 ports scanned but not shown below are in state: closed)
> Port State Service
> 22/tcp openssh
> 1024/tcp open
Edward Guldemond <[EMAIL PROTECTED]> writes:
> On Wed, Nov 20, 2002 at 12:53:27AM +0100, Olaf Dietsche wrote:
>>
>> Look at "man xinit" and "man Xserver". There you will find an option
>> "-nolisten".
>
> In /etc/X11/xinit/xserverrc, I have the following line:
> exec /usr/bin/X11/X -dpi 100 -noli
On Tue, Nov 19, 2002 at 04:51:03PM -0800, Rick Moen wrote:
> Quoting Edward Guldemond ([EMAIL PROTECTED]):
>
> > In /etc/X11/xinit/xserverrc, I have the following line:
> > exec /usr/bin/X11/X -dpi 100 -nolisten tcp
> >
> > So why is X still listening on TCP?
>
> Because xdm/kdm/gdm don't heed /
All,
I was doing a routine nmap of my network today, and noticed when I
nmap'd a box running KDE that the following showed up:
Starting nmap V. 2.54BETA31 ( www.insecure.org/nmap/ )
Interesting ports on (removed) (XX.XX.XXX.XX):
(The 1552 ports scanned but not shown below are in state: closed)
Po
Quoting Edward Guldemond ([EMAIL PROTECTED]):
> In /etc/X11/xinit/xserverrc, I have the following line:
> exec /usr/bin/X11/X -dpi 100 -nolisten tcp
>
> So why is X still listening on TCP?
Because xdm/kdm/gdm don't heed /etc/X11/xinit/xserverrc, but rather
/etc/X11/xdm/Xservers ?
>> When this
On Wed, Nov 20, 2002 at 12:53:27AM +0100, Olaf Dietsche wrote:
> > Now, is there any security implications of having this port open? (I
> > am nmap'ing this box's external Internet interface as it is my ipmasq
> > box.) If so, what files do I have to edit to get rid of it? I don't
> > need X lis
Edward Guldemond <[EMAIL PROTECTED]> writes:
> Starting nmap V. 2.54BETA31 ( www.insecure.org/nmap/ )
> Interesting ports on (removed) (XX.XX.XXX.XX):
> (The 1552 ports scanned but not shown below are in state: closed)
> Port State Service
> 22/tcp openssh
> 1024/tcp open
All,
I was doing a routine nmap of my network today, and noticed when I
nmap'd a box running KDE that the following showed up:
Starting nmap V. 2.54BETA31 ( www.insecure.org/nmap/ )
Interesting ports on (removed) (XX.XX.XXX.XX):
(The 1552 ports scanned but not shown below are in state: closed)
Po
18 matches
Mail list logo
