Date: Thu, 25 Jan 2001 11:10:25 -0700 (MST) From: "Geoffrey T. Falk" <gtf@cirp.org> To: freebsd-security@freebsd.org Subject: rpc.statd bloat Message-ID: <200101251810.LAA04410@h-209-91-79-2.gen.cadvision.com> In-Reply-To: <200101251726.f0PHQei65827@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
In a related note: Is it normal for rpc.statd to bloat? rpc.statd on boojum, my 4.0-RELEASE box, recently experienced a VSIZE > 274000. This box is an NFS server, but I don't think my NFS client (NEXTSTEP 3.2) is using rpc.statd, because it runs just fine without it. Thanks g. On 25 Jan, Steven G. Kargl wrote: > Are there any known compromises of rpc.statd that involve > buffer overflows? I have several entries in /var/log/messages that > look suspicious, but I currently don't know what these entries > mean (see attachment). The suspicious entries appear to be > buffers that someone or something has tried to overflow. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200101251810.LAA04410>