Hello and welcome to the Monday, January 8, 2004 edition of the Sands and its Storm Center's Stormcast.

My name is Johannes Ulrich, and I'm recording from Jacksonville, Florida.

Well, we got a couple of good diaries to talk about here for the weekend.

The first one is by Rob about how to use PowerShell commands in order to get information

similar to the good old NetStad command.

NetStat, of course, of your go-to tool, if you're trying to figure out what ports a system

is listening on and also what particular process

listens on a specific port.

PowerShell has a number of commands here that you can use a get process to get the processes

like your process IDs and process name.

And then there are two commands for the connections.

There is get net udip endpoint and get net TCP endpoint.

These functions have quite a bit of detail to provide.

One thing I found particular need is that you can also get how long a connection has been listening.

And with that, figure out if you have any sort of long-running processes that are listening

on the network. So create for a quick sort of triage to see if anything bad is happening on

the system, but also just for routine system

maintenance.

Enxavi wrote up a new example of an older fishing trick where the fishing site first claims

that the password is incorrect and then tricks the user into resubmitting the password.

Of course, there is a better chance of getting a

correct password if they both match. The other issue here is I've sometimes seen the advice and

...