Wichert Akkerman wrote:
> There is some orbit-configuration file you should be able to create to
> tell it not to listen to TCP ports. From what I hear that kill all ports
> but one. And unfortunately it seems to be completely undocumented (I
> can't even find what filename to use..).
$ cat ~/.or
Hi List,
Just wanted to thank publically all the people who helped me with
the Automatic Password Changing subject.
I can now say that it is working pretty well with no problems, and I am
quite happy about it :)
Thanks All !
--
On Wed, Mar 22, 2000 at 01:52:47PM +, Sergio Brandano wrote:
>
> Ingemar Fällman wrote
>
> >Start X whit the parameter '-nolisten tcp' (startx -- -nolisten tcp)
> >then X wont listen on port 6000
>
> I am using gdm. Let see how I can do that. Anyway, will this affect
> ssh?
someone else a
Ethan Benson wrote:
>saft is controlled from /etc/inetd.conf at least it was when i somehow
>ended up with it.
In order to kill saft I had to purge the sendfile package.
Sergio
On Wed, Mar 22, 2000 at 01:44:14PM +, Sergio Brandano wrote:
>
> >saft is controlled from /etc/inetd.conf at least it was when i somehow
>
> I can see it depends on inetd, by running netstat -anp | egrep 487,
> but i see no reference to it in the /etc/init.d files.
thats because services c
Sergio Brandano wrote:
> Ingemar Fällman wrote
>
> >Start X whit the parameter '-nolisten tcp' (startx -- -nolisten tcp)
> >then X wont listen on port 6000
in /etc/gdm/gdm.conf
add -nolisten tcp after /usr/bin/X11/X in the servers section
my config looks like this:
[servers]
#0=/usr/bin/X11/X
1
On Wed, 22 Mar 2000, Ethan Benson wrote:
> Netbus and nterm, no idea.
Depending on which version you have installed on your system, the command
netstat -ap
will give you a list of the ports on which your computer is listening and
(the p switch) the process id that is listening on each of them.
Ingemar Fällman wrote
>Start X whit the parameter '-nolisten tcp' (startx -- -nolisten tcp)
>then X wont listen on port 6000
I am using gdm. Let see how I can do that. Anyway, will this affect
ssh?
Sergio
Greetings,
What about printing via a UNIX socket? Is that even supported?
Regards,
Alex.
-BEGIN GEEK CODE BLOCK-
Version: 3.12
GCM d- s:+ a--- C UL P L+++ E W++ N o-- K- w
O--- M- V- PS+ PE- Y PGP t+ 5 X- R tv+ b DI--- D+
G e-- h++ r--- y
--END GEEK CODE BLOCK--
On Wed,
> printer is lpd, /etc/init.d/lprng stop.
That is not a god idea if you want to be able to print.
> X11 is opened whenever you start X, no way around that, a ipchains rule is
> the best way to deal with X IMO. Netbus and nterm, no idea.
Start X whit the parameter '-nolisten tcp' (startx -- -nol
>saft is controlled from /etc/inetd.conf at least it was when i somehow
I can see it depends on inetd, by running netstat -anp | egrep 487,
but i see no reference to it in the /etc/init.d files.
>ended up with it. printer is lpd, /etc/init.d/lprng stop. X11 is
done!
>opened whenever you s
On Wed, Mar 22, 2000 at 01:24:31PM +, Sergio Brandano wrote:
>
> Alexander Hvostov wrote:
>
> > Would anyone happen to know if it's possible (without hacking the sources
> > and breaking something) to disable the TCP listen ports that a great deal
> > of GNOME apps seem to listen on?
>
> I
Alexander Hvostov wrote:
> Would anyone happen to know if it's possible (without hacking the sources
> and breaking something) to disable the TCP listen ports that a great deal
> of GNOME apps seem to listen on?
I have the same need. Also, the following thing occours with exactly?
the same co
Previously Alexander Hvostov wrote:
> Would anyone happen to know if it's possible (without hacking the sources
> and breaking something) to disable the TCP listen ports that a great deal
> of GNOME apps seem to listen on?
There is some orbit-configuration file you should be able to create to
tell
Hi Again, and thanks for more info :)
I'll try perl -npi.bak -e 's/^root:[^:]*:(.*)$/root:pants:\1/o' /etc/shadow
hope it works, and I'll keep all informed :)
Thanks for all and much respect :)
Tim Haynes wrote:
> On Wed, Mar 22, 2000 at 12:36:59PM +0100, Neil D. Roberts wrote:
>
> > Hi, um,
Just one query,
if ones root password is getting accidentially changed, shouldnt you be looking
for the source to stop it?
Just my thoughts,
Aaron
Tim Haynes wrote:
> On Wed, Mar 22, 2000 at 12:36:59PM +0100, Neil D. Roberts wrote:
>
> > Hi, um, bad news ? Yep, but I was lucky though . . .
> >
>
On Wed, Mar 22, 2000 at 11:53:06AM +, Tim Haynes wrote:
> As someone else has said, btw, would you recognise your own encrypted root
> password? (Would whoever mailed me that directly please bounce it to the
> *list* as well?!)
I don't keep a Fcc: of all my outgoing mail but I'll reproduce my
On Wed, Mar 22, 2000 at 12:36:59PM +0100, Neil D. Roberts wrote:
> Hi, um, bad news ? Yep, but I was lucky though . . .
>
> Ok, I got the perl -npi.bak -e 's/^root:[^:]*:/root:pants/o' /etc/shadow ,
> pants being my shadowed password. I put this in a file called fixpw.sh,
> chmoded it to 700 and
Hi, um, bad news ? Yep, but I was lucky though . . .
Ok, I got the perl -npi.bak -e 's/^root:[^:]*:/root:pants/o' /etc/shadow
, pants being my shadowed password. I put this in a file called
fixpw.sh, chmoded it to 700 and executed it. Then on tty2 I tried to
login and it didn´t let me, so before I
Gee, thanks, I´m on my way :) Tell how things work out. . . . .
Tim Haynes wrote:
> On Wed, Mar 22, 2000 at 11:33:04AM +0100, Neil D. Roberts wrote:
> > Thanks Tim ! :)
> >
> > So this line changes the root password ? Ok, the password has a nice length,
> > with upper and lower case, numbers and
On Wed, Mar 22, 2000 at 11:33:04AM +0100, Neil D. Roberts wrote:
> Thanks Tim ! :)
>
> So this line changes the root password ? Ok, the password has a nice length,
> with upper and lower case, numbers and a couple simbols. Pretty solid ?
Good, way to go.
> Anyway, so what does
perl -npi
Thanks Tim ! :)
So this line changes the root password ? Ok, the password has a nice length,
with upper and lower case, numbers and a couple simbols. Pretty solid ? Anyway,
so
what does "perl -npi.bak -e 's/^root:[^:]*:/root:pants/o' /etc/shadow" actually
do, does it create a file, or is it t
Hi,
Thanks for the info :) So, if there was a file like this, how would I need
to
look for it ? The real issue is that there is a process which is currently doing
this in one of the office machines, and I can´t do anything about it. I tried
looking into the cron.daily - weekly and monthly, bu
> First time on this list :) Anyway, I have a little brain cracker
> here, or at least for me it is. Does anybody happen to know how to have
> an automatic process which sets "roots" password every 1 hour ? What I
> mean basically is so that when the root password gets changed
> accidentally, t
On Wed, Mar 22, 2000 at 02:07:10AM -0800, Alexander Hvostov wrote:
> That's a bad idea because it defeats the purpose of the password being there
> to start with. You see, the password is ordinarily encrypted and kept under
> tight safeguards, to make it hard to figure out what it is. If you were
Neil,
That's a bad idea because it defeats the purpose of the password being
there to start with. You see, the password is ordinarily encrypted and
kept under tight safeguards, to make it hard to figure out what it is. If
you were to reset the password periodically, you would presumably have to
st
Hi,
First time on this list :) Anyway, I have a little brain cracker
here, or at least for me it is. Does anybody happen to know how to have
an automatic process which sets "roots" password every 1 hour ? What I
mean basically is so that when the root password gets changed
accidentally, this p
Greetings,
Would anyone happen to know if it's possible (without hacking the sources
and breaking something) to disable the TCP listen ports that a great deal
of GNOME apps seem to listen on?
My suspicion is that these ports are used for GNOME's CORBA support, which
is great, but I tend to feel s
28 matches
Mail list logo
