Bugtraq mailing list archives
Re: remotely kill solaris syslogd
From: paul () CSE UCSC EDU (Paul Tatarsky)
Date: Thu, 23 Oct 1997 08:29:49 -0700
./syslogd_kill <ip-with-no-DNS> <victim IP>
Kind of wild if you feed it a subnet broadcast address as the <victim IP>. I wouldn't try that lightly if you don't have access to restart all the dead syslogd's on all Solaris boxes on that wire. At least that's what happened to me running 2.5.1 and 2.5 with various patch revs, but none with 103738-04. Excuse me, I have to restart a few syslogd's and apply some patches. -------------------------------------------------------------------- Paul Tatarsky paul () cse ucsc edu UC Santa Cruz CE/CIS Systems Manager --------------------------------------------------------------------
Current thread:
- Remotely kill Solaris syslogd lb - STAFF (Oct 21)
- Re: Remotely kill Solaris syslogd Andrew Reynhout (Oct 21)
- Oops: Re: Remotely kill Solaris syslogd Andrew Reynhout (Oct 21)
- Responses to syslogd killing lb (Oct 21)
- Re: Responses to syslogd killing Zack Weinberg (Oct 21)
- <Possible follow-ups>
- Re: remotely kill solaris syslogd Chris Wilson (Oct 21)
- Re: remotely kill solaris syslogd Paul Tatarsky (Oct 23)
- IRIX /var/inst/patchbase Paul Tatarsky (Oct 23)
- Re: IRIX /var/inst/patchbase Alain Renaud (Oct 25)
- KSR[T] Advisory #004: printfilter / groff / lpd KSR[T] (Oct 25)