Date: Thu, 8 Mar 2001 09:40:55 -0500 From: Will Andrews <will@physics.purdue.edu> To: Will Mitayai Keeso Rowe <mit@mitayai.net> Cc: tjk@tksoft.com, Will Mitayai Keeso Rowe <mitayai@dreaming.org>, will@physics.purdue.edu, freebsd-security@FreeBSD.ORG Subject: Re: strange messages Message-ID: <20010308094055.L45561@ohm.physics.purdue.edu> In-Reply-To: <NEBBIEGPMLMKDBMMICFNIEIPELAA.mit@mitayai.net>; from mit@mitayai.net on Thu, Mar 08, 2001 at 09:33:30AM -0500 References: <200103081428.GAA02075@uno.tksoft.com> <NEBBIEGPMLMKDBMMICFNIEIPELAA.mit@mitayai.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--m+jEI8cDoTn6Mu9E Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Mar 08, 2001 at 09:33:30AM -0500, Will Mitayai Keeso Rowe wrote: > Acording to CERT (the latest statd message seems to be > http://www.kb.cert.org/vuls/id/34043) > FreeBSD is not vulnerable to rpc.statd problems. >=20 > But, i still have a question... how can i better log attempts to hack my > machine's rpc.statd? It would be nice to have an IP of the connecting box= so > i can see if they are doing it remotely or by an account on my machine. Tcpwrappers or ipfw? What good is this information? --=20 wca --m+jEI8cDoTn6Mu9E Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.3 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6p5n3F47idPgWcsURAkd+AJ9KnJHY9Tl6l2Z8g/asqH7xXJHloACeLDQ6 KU2gigN+L+L62nGzDL1S5xQ= =SSBo -----END PGP SIGNATURE----- --m+jEI8cDoTn6Mu9E-- 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?20010308094055.L45561>