I saw messages on this list from early in the year about an rpc.statd
exploit, and I believe it just happened to me. I'd appreciate any help
from you all. I'm on a new 2.2 install from CD-ROM; both nfs-common
and nfs-kernel-server are version 0.1.9.1-1. Someone on this list said
that this
On Fri, Jun 15, 2001 at 03:41:39PM -0400, Michael Stutz wrote:
what I'd like to know from you all is a) was this failed -- is there
any way of knowing whether or not I've been cracked and b) what should
I do next?
Yes, it is a failed crack attempt. You know it failed because if it
I saw messages on this list from early in the year about an rpc.statd
exploit, and I believe it just happened to me. I'd appreciate any help
from you all. I'm on a new 2.2 install from CD-ROM; both nfs-common
and nfs-kernel-server are version 0.1.9.1-1. Someone on this list said
that this problem
On Fri, Jun 15, 2001 at 03:41:39PM -0400, Michael Stutz wrote:
what I'd like to know from you all is a) was this failed -- is there
any way of knowing whether or not I've been cracked and b) what should
I do next?
Yes, it is a failed crack attempt. You know it failed because if it
I got the following (alarming) messages on syslog:
Jan 8 13:34:23 yuban syslogd: Cannot glue message parts together
Jan 8 13:34:23 yuban /sbin/rpc.statd[159]: gethostbyname error for
^X\xf7\xff\xbf^X\xf7\xff\xbf^Y\xf7\
[EMAIL PROTECTED] writes:
I got the following (alarming) messages on syslog:
Jan 8 13:34:23 yuban syslogd: Cannot glue message parts together
Jan 8 13:34:23 yuban /sbin/rpc.statd[159]: gethostbyname error for
^X\xf7\xff\xbf^X\xf7[snip]
Jan 8 13:34:23 yuban
Previously [EMAIL PROTECTED] wrote:
I got the following (alarming) messages on syslog:
This is becoming a FAQ.. it's a failed crack attempt.
Wichert.
--
/ Generally uninteresting signature - ignore at your convenience \
|
I got the following (alarming) messages on syslog:
This is becoming a FAQ.. it's a failed crack attempt.
I got the same attempt on Sunday. This is what I found out about it:
"The rpc.statd program passes user-supplied data to the syslog() function
as a format string. If there is no input
This is just a comment based on all the emails that I have been seeing here
(not that I read them all, but...).
In theory if you are going to leave your system setup on a public network, then
you should really be filtering ALL connections to the box and ONLY ONLY ONLY
allowing the services that
On Tue, Jan 09, 2001 at 12:31:59PM -0800, [EMAIL PROTECTED] wrote:
I got the following (alarming) messages on syslog:
Jan 8 13:34:23 yuban syslogd: Cannot glue message parts together Jan
8 13:34:23 yuban /sbin/rpc.statd[159]: gethostbyname error for
I got the following (alarming) messages on syslog:
Jan 8 13:34:23 yuban syslogd: Cannot glue message parts together
Jan 8 13:34:23 yuban /sbin/rpc.statd[159]: gethostbyname error for
^X\xf7\xff\xbf^X\xf7\xff\xbf^Y\xf7\
[EMAIL PROTECTED] writes:
I got the following (alarming) messages on syslog:
Jan 8 13:34:23 yuban syslogd: Cannot glue message parts together
Jan 8 13:34:23 yuban /sbin/rpc.statd[159]: gethostbyname error for
^X\xf7\xff\xbf^X\xf7[snip]
Jan 8 13:34:23 yuban
Previously [EMAIL PROTECTED] wrote:
I got the following (alarming) messages on syslog:
This is becoming a FAQ.. it's a failed crack attempt.
Wichert.
--
/ Generally uninteresting signature - ignore at your convenience \
|
I filed a bug against hostname for this behavior. Perhaps I should refile
it against libc6... Doogie, if you're reading this and you beat me to the
punch, go for it...
On Tue, 9 Jan 2001 [EMAIL PROTECTED] wrote:
I got the following (alarming) messages on syslog:
Jan 8 13:34:23 yuban
I got the following (alarming) messages on syslog:
This is becoming a FAQ.. it's a failed crack attempt.
I got the same attempt on Sunday. This is what I found out about it:
The rpc.statd program passes user-supplied data to the syslog() function
as a format string. If there is no input
This is just a comment based on all the emails that I have been seeing here
(not that I read them all, but...).
In theory if you are going to leave your system setup on a public network, then
you should really be filtering ALL connections to the box and ONLY ONLY ONLY
allowing the services that
On Tue, Jan 09, 2001 at 12:31:59PM -0800, [EMAIL PROTECTED] wrote:
I got the following (alarming) messages on syslog:
Jan 8 13:34:23 yuban syslogd: Cannot glue message parts together Jan
8 13:34:23 yuban /sbin/rpc.statd[159]: gethostbyname error for
17 matches
Mail list logo
