LPD configuration +
From: Sanjeev B.S. (sanjeev@mbu.iisc.ernet.in)Date: 10/10/01
- Previous message: Robin Lynn Frank: "Reasonable precautions"
- In reply to: hg9627: "Re: LPD configuration"
- Next in thread: Sanjeev B.S.: "LPD: Summary, fury and more"
- Next in thread: Jarno Huuskonen: "Re: LPD configuration"
- Reply: Sanjeev B.S.: "LPD: Summary, fury and more"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Wed, 10 Oct 2001 09:13:44 +0530 (IST) From: "Sanjeev B.S." <sanjeev@mbu.iisc.ernet.in> To: <focus-linux@securityfocus.com> Subject: LPD configuration + Message-ID: <Pine.LNX.4.33.0110100903340.32710-100000@mbu.iisc.ernet.in>
Hello,
Thanks to all who have replied, I shall summerise soon the essence
of the whole lot. My problem in particular was that of a paraoid's..., in
the sense that if someone penetrates the firewall is there a way out to
secure. In other words, just as we can make root login from console (note,
it's not just the hostname now), can we do the same for lpd (and
associated dameons) accessibility!? I do not see how it can be done, but
interested to know if it can be... Or is there another way out!?
Sorry for being paranoid, but I would be able to relax if I can
have confidence in the daemons running. The problem is, we have lots of
computers around (not just linux but also SGI et al) getting routinely
cracked.
Thanks very much in advance for any information and have a nice day,
Sincerely,
-Sanjeev
- Previous message: Robin Lynn Frank: "Reasonable precautions"
- In reply to: hg9627: "Re: LPD configuration"
- Next in thread: Sanjeev B.S.: "LPD: Summary, fury and more"
- Next in thread: Jarno Huuskonen: "Re: LPD configuration"
- Reply: Sanjeev B.S.: "LPD: Summary, fury and more"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]