Subject: Re: syslog and chroot
To: None <tech-security@NetBSD.ORG>
From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
List: tech-security
Date: 08/17/1997 12:00:49
-----BEGIN PGP SIGNED MESSAGE-----


>>>>> "Jukka" == Jukka Marin <jmarin@pyy.jmp.fi> writes:
    Jukka> Yep.  But I still want to be able to log on other machines
    Jukka> over the network.  How could this be done more securely
    Jukka> (and without losing any log events during the moments that
    Jukka> the network is down)?  How do other people do this?

  There are two ways, probably complementary.
  a) support TCP connections for syslogd.
  b) support spooling on a local disk when loghost is down.

  Handling many TCP connections may be difficult inside syslogd
(practically, there is no theoretical problem). I would suggest that a
syslogd-helper might make things easier to maintain.
  
]  10s to Tokyo, 15m to the Cottage? What if I'm already there? | one quark   [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    | two quark   [
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ | red q blue q[
] panic("Just another NetBSD/notebook using, kernel hacking, security guy");  [



-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: latin1
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface

iQB1AwUBM/cgKMmxxiPyUBAxAQGK2QL/di6DqAMEi5elaksfYftK93mJZ10cqiI3
Ed4tQVU9t2X57Hd6dFL2wjnq0xZb+YISfF2Bzw3XRNKl9xsM7xO1kjBfjo7qfC+h
3CnE6hGWETQgLAUi2Efva7xizNt+tEX/
=f0a8
-----END PGP SIGNATURE-----