> how, can i see the tcp port 4350 that states to be opened useing nmap
There is _the_ official document of registered ports at
http://www.iana.org/assignments/port-numbers and it claims 4350 is
"Net Device" - what ever that means. The entry is created by microsoft
so we may assume it is some w
On Mon, May 28, 2001 at 11:09:29PM -0400, S. Kraig wrote:
> the 'international kernel' and after enabling that form of encryption...
> so where do I start in doing this?
http://www.kerneli.org/
Hi, I have been playing around with loop back file
systems recently (mostly playing with Linux-care's bootable buisness card mini
CD-ROM linux system...which uses a compressed ext2 file system image) and
realized that the -e (encryption) option provides a perfect mechanism for a
different pr
Hello,
On Tue, May 29, 2001 at 03:05:52AM +0300, killah wrote:
> how, can i see the tcp port 4350 that states to be opened useing nmap
As root, you can do:
fuser -v -n tcp 4350
and:
lsof -i tcp:4350
The lsof command, if it finds anything, will return a PID as part of it's
outp
On Mon, May 28, 2001 at 11:09:29PM -0400, S. Kraig wrote:
> the 'international kernel' and after enabling that form of encryption...
> so where do I start in doing this?
http://www.kerneli.org/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EM
Hi, I have been playing around with loop back file
systems recently (mostly playing with Linux-care's bootable buisness card mini
CD-ROM linux system...which uses a compressed ext2 file system image) and
realized that the -e (encryption) option provides a perfect mechanism for a
different pr
killah writes:
how, can i see the tcp port 4350 that states to be opened useing nmap
what is his proccess and which file is it's owned ?
You can use the "lsof" command to see what processes is bound to a given
port. As I recall, it would be "lsof -i TCP:4350" and "lsof -i UDP:4350",
but
how, can i see the tcp port 4350 that states to be opened useing nmap
what is his proccess and which file is it's owned ? doing ps with many
different parameters doesn't saw me any unusual. maybe guys you can help
me. Also after connecting with netcat to that port, seems closed and
when
i am repea
Hello,
On Tue, May 29, 2001 at 03:05:52AM +0300, killah wrote:
> how, can i see the tcp port 4350 that states to be opened useing nmap
As root, you can do:
fuser -v -n tcp 4350
and:
lsof -i tcp:4350
The lsof command, if it finds anything, will return a PID as part of it's
out
killah writes:
> how, can i see the tcp port 4350 that states to be opened useing nmap
> what is his proccess and which file is it's owned ?
>
You can use the "lsof" command to see what processes is bound to a given
port. As I recall, it would be "lsof -i TCP:4350" and "lsof -i UDP:4350",
b
how, can i see the tcp port 4350 that states to be opened useing nmap
what is his proccess and which file is it's owned ? doing ps with many
different parameters doesn't saw me any unusual. maybe guys you can help
me. Also after connecting with netcat to that port, seems closed and
when
i am repe
Jim Breton <[EMAIL PROTECTED]> writes:
> On Mon, May 28, 2001 at 01:46:07PM +0200, Tomasz Olszewski wrote:
> > If an user
> > creates his own $HOME/.xserverrc, it overrides the system wide
> > xserverrc.
>
> So make /usr/bin/X11/X a wrapper for the "real" X.
>
> Problem with this is, if you upgr
On Mon, May 28, 2001 at 01:46:07PM +0200, Tomasz Olszewski wrote:
> If an user
> creates his own $HOME/.xserverrc, it overrides the system wide
> xserverrc.
So make /usr/bin/X11/X a wrapper for the "real" X.
Problem with this is, if you upgrade or re-install the package
containing it, it will get
Hello Debian Users!
On niedziela, 27 maj 2001, 17:00:37 + Jim Breton wrote:
> Yep... actually this _is_ the correct way to deal with this.
But I want to make the "-nolisten tcp" option always active. If an user
creates his own $HOME/.xserverrc, it overrides the system wide
xserverrc. Besides,
Hello Debian Users!
On niedziela, 27 maj 2001, 13:06:33 -0500 Dana J . Laude wrote:
> The easy way to do it is instead of using "startx" use
> "startx -- -nolisten tcp".
Yes, I know this :) The problem is that I need that option to be set by
default, independently from the method an user chooses
Jim Breton <[EMAIL PROTECTED]> writes:
> On Mon, May 28, 2001 at 01:46:07PM +0200, Tomasz Olszewski wrote:
> > If an user
> > creates his own $HOME/.xserverrc, it overrides the system wide
> > xserverrc.
>
> So make /usr/bin/X11/X a wrapper for the "real" X.
>
> Problem with this is, if you upg
On Mon, May 28, 2001 at 01:46:07PM +0200, Tomasz Olszewski wrote:
> If an user
> creates his own $HOME/.xserverrc, it overrides the system wide
> xserverrc.
So make /usr/bin/X11/X a wrapper for the "real" X.
Problem with this is, if you upgrade or re-install the package
containing it, it will ge
Hello Debian Users!
On niedziela, 27 maj 2001, 17:00:37 + Jim Breton wrote:
> Yep... actually this _is_ the correct way to deal with this.
But I want to make the "-nolisten tcp" option always active. If an user
creates his own $HOME/.xserverrc, it overrides the system wide
xserverrc. Besides
Hello Debian Users!
On niedziela, 27 maj 2001, 13:06:33 -0500 Dana J . Laude wrote:
> The easy way to do it is instead of using "startx" use
> "startx -- -nolisten tcp".
Yes, I know this :) The problem is that I need that option to be set by
default, independently from the method an user chooses
> -Original Message-
> From: Marcelo Drudi Miranda [mailto:[EMAIL PROTECTED]
> Sent: 26. svibanj 2001 4:49
> To: debian-security@lists.debian.org
> Subject: Re: proftpd exploit??
>
>
> Em Thu, 24 May 2001 20:34:56 +0200
> Matthias Richter <[EMAIL PROTECTED]> escreveu:
>
> > Andres Herrera
> startx -- -nolisten tcp
Obviously this would do the trick, but see below as to why it is not
a good option.
> only as part of the perennially-discussed task-harden. Doesn't even
> effect remote xsessions, as you should be using ssh to tunnel your
> sessions anyway.
There is no way of ss
> -Original Message-
> From: Marcelo Drudi Miranda [mailto:[EMAIL PROTECTED]]
> Sent: 26. svibanj 2001 4:49
> To: [EMAIL PROTECTED]
> Subject: Re: proftpd exploit??
>
>
> Em Thu, 24 May 2001 20:34:56 +0200
> Matthias Richter <[EMAIL PROTECTED]> escreveu:
>
> > Andres Herrera wrote on Thu
> startx -- -nolisten tcp
Obviously this would do the trick, but see below as to why it is not
a good option.
> only as part of the perennially-discussed task-harden. Doesn't even
> effect remote xsessions, as you should be using ssh to tunnel your
> sessions anyway.
There is no way of s
23 matches
Mail list logo
