On 12/1/01 at 8:30 PM, Jack Coates <[EMAIL PROTECTED]> wrote:
> On Sat, 1 Dec 2001, Charles Steinkuehler wrote:
> > Or just grab a bunch of multi-port serial cards from
> > e-bay, and setup a log-host using serial links. You can
> > keep the log host disconnected from the net entirely (or
> > m
On 12/1/01 at 3:12 PM, Jack Coates <[EMAIL PROTECTED]> wrote:
> On Sat, 1 Dec 2001, Tony wrote:
> > If so, wouldn't it be easier/safer/more secure to
> > forward them to an internal syslog server?
> syslog-ng is supposed to fix a lot of these problems, but I've never
> gotten around to taking a
On Sat, 1 Dec 2001, Charles Steinkuehler wrote:
> > I like doing this, but there are concerns with doing it in anything less
> > than a perfectly trusted environment: If your log host is unavailable,
> > you're not logging; if malicious listeners are on the LAN, they can see
> > everything you lo
> I like doing this, but there are concerns with doing it in anything less
> than a perfectly trusted environment: If your log host is unavailable,
> you're not logging; if malicious listeners are on the LAN, they can see
> everything you log (could be quite useful when scanning or rooting a
> ser
All valid points, I hadn't thought of those reasons.
Thanks
Tony
>
> On Sat, 1 Dec 2001, Tony wrote:
>
> >
> > I guess I don't completely understand why you need a JFFS for
> > something that under normal circumstances, isn't written to
> > physically. If you have a crash/powerdown situatio
On Sat, 1 Dec 2001, Tony wrote:
>
> I guess I don't completely understand why you need a JFFS for
> something that under normal circumstances, isn't written to
> physically. If you have a crash/powerdown situation, with resumtion
> of service, you just reload your image and continue to
> firewal
