colby-pdq / bluekeep-scanner-ps-parser Goto Github PK

This is a request from Josh: https://www.pdq.com/blog/import-bluekeep-scan-results-into-pdq-inventory-part-1/

According to this comment, rdpscan's parameter is --port: robertdavidgraham/rdpscan#23 (comment)

Write-Warning ("Blah {0:N1}" -f $Seconds)

I'm running into too many issues with trying to set it dynamically. I'm just going to set it to a static value of something like 8 or 16 for now.

At some point during the development of this script I thought it was a good idea to use a loop counter to approximate 5 minutes instead of just using a stopwatch :D

Another one of those "what was I thinking?" sort of deals. If both are specified, just add -Computers to -Collections (after deduping).

1. My implementation of jobs is kinda janky.
2. Supposedly runspaces are faster than jobs: https://foxdeploy.com/2016/03/23/coding-for-speed/

I am waiting to hear back from our lawyers about which license I can use. Personally, I want to use the MIT license.

Right now you have to give -RDPScanEXE an absolute path, or it will blow up. This should be easy to fix with Resolve-Path.

I haven't decided yet whether to use comment-based help or put it in a help file/files.

sorry if I use this message to communicate with you
in regards of this stuff https://gitlab.com/ColbyBouma/pdqstuff
it's possible to implement a function to export and import packages from command line?
regards

It's easy for Verbose and Warning messages to get lost in the deluge of scan results. A log file would probably be handy.

The log file in #5 may mitigate this, but it also may be handy to show all warnings at the end instead of in the middle of the deluge.

Some people may not want the results output to the standard stream.