From: Ryan Ngai Hon Kong <hkngai@jos.com.my>
To: "'deedsmis@aculink.net'" <deedsmis@aculink.net>,
"'linux-admin@vger.kernel.org'" <linux-admin@vger.kernel.org>
Subject: RE: What Is hosts2-ns
Date: Tue, 28 May 2002 08:59:54 +0800 [thread overview]
Message-ID: <75194D81CD3BD611B3CB00306E0114543BA6DF@JOSEXCHG> (raw)
One of the trojan port listed on my lists said port 81 is RemoConChubo
trojan.
Good luck.
Ryan
-----Original Message-----
From: SoloCDM [mailto:deedsmis@aculink.net]
Sent: Sunday, May 26, 2002 11:01 PM
To: David Jackson
Cc: Linux-Administration (Majordomo)
Subject: Re: What Is hosts2-ns
David Jackson stated the following:
>
> > On Linux, what is hosts2-ns? How is it accessed from a remote host?
> > Someone recently tried to access my server through port 81.
>
> Accessed how?
>
> telnet you_hostname 81
> http://www.your_hostname.com:81
>
> Check /etc/services that's where port are assigned. Post any related
> messages from logs.
The only other related part was the origin:
yin.globalmedia.org/129.250.225.10. Portsentry caught it before any
damage could take place.
Another source said it is probably a new WinIIS worm.
--
Note: When you reply to this message, please include the mailing
list/newsgroup address and my email address in To:.
*********************************************************************
Signed,
SoloCDM-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2002-05-28 0:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-28 0:59 Ryan Ngai Hon Kong [this message]
2002-05-30 19:03 ` What Is hosts2-ns SoloCDM
-- strict thread matches above, loose matches on Subject: below --
2002-05-25 23:12 David Jackson
2002-05-26 15:00 ` SoloCDM
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=75194D81CD3BD611B3CB00306E0114543BA6DF@JOSEXCHG \
--to=hkngai@jos.com.my \
--cc=deedsmis@aculink.net \
--cc=linux-admin@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox