Date: Tue, 4 May 1999 11:24:32 -0700 (PDT) From: Matthew Dillon <dillon@apollo.backplane.com> To: "Raymond Wiker" <raymond@orion.no> Cc: <freebsd-stable@FreeBSD.ORG>, <security@FreeBSD.ORG> Subject: Re: FreeBSD 3.1 remote reboot exploit (fwd) Message-ID: <199905041824.LAA14835@apollo.backplane.com> References: <005401be9932$60574860$380051c2@greg.qmpgmc.ac.uk> <14126.49715.589157.172436@foobar.orion.no>
index | next in thread | previous in thread | raw e-mail
:Greg Quinlan writes:
: > This sounds so.. so very familiar!!
: >
: > I have been the target of exploits before......
: >
: > The exact same thing I have been experiencing........but not for about 5
: > days now!
: >
: > I'm not convinced its a pure exploit.. (i.e. a program specifically written
: > for the purpose)
:
: My first post to freebsd-stable (and security) - and it's a
:me-too :-)
:
: I'm running 3.1-RELEASE on a 486 with 16 MB of RAM, and this
:machine has been falling over regularly. Up until now I have suspected
:the local electricity, but it had rebooted this morning, even though
:it's now on a UPS.
:
: I have two other machines running 3.1-RELEASE in a slightly
:less hostile environment (i.e, no direct connections outwards), and
:they have been much more stable. I cannot rule out a hardware problem
:on the 486; I'll know for sure as soon as I upgrade it.
:
: //Raymond.
Setup a serial console and monitor it so you can see the panic message.
Or, better, configure the kernel to drop into DDB when it panics so you
can do a stack 'trace', and report the results.
-Matt
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199905041824.LAA14835>