If you think it's that critical, (i think it's that critical) start by
blocking any connections from anywhere to that machine/port. See if
anyone complains. Check any old firewall logs for that port while you're
at it. Then continue your investigation!!
Fabrizio
On 9/28/07, *Simon Smith* <simon () snosoft com <mailto:simon () snosoft com>>
wrote:
Got output... and it was... no idea what it was... can't paste it due to
confidentiality though.
Fabrizio wrote:
.NET Remoting is "a generic system for different applications to
use to
communicate with one another." It's part of the .NET framework,
obviously. (not trying to be a smart ass)
I'm gonna take a wild guess and say it's not a good thing......
Connect to it, and see if you get any output, if you haven't already
done so.
Fabrizio
On 9/28/07, * Simon Smith* < simon () snosoft com
<mailto:simon () snosoft com>
<mailto:simon () snosoft com <mailto:simon () snosoft com>>> wrote:
Has anyone ever heard of .NET REMOTING running on port 31337? If so,
have you ever seen it "legitimate"?
_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
<http://lists.grok.org.uk/full-disclosure-charter.html>
<http://lists.grok.org.uk/full-disclosure-charter.html>
Hosted and sponsored by Secunia - http://secunia.com/
<http://secunia.com/>
------------------------------------------------------------------------
_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/