lsusb
Look what they need to mimic a fraction of our power.
I've always been particularly revolted by powershell syntax and utilities
Yes, if it was as object based as it claims, Get-WmiObject would subtract WmiObject from Get. Instead it is like having all the clutchy drawbacks from being object based without reaping any of the potential bemefits.
If you want anything that actually is object based, just use xon.sh - sane and familiar syntax with insane amounts of power just like that
Get-Disk would have sufficed here, no real need to use WMI here. That said, you would still need to filter USB device and select properties you want to retrieve.
And unrelated, but if WMI class needs to be queried, Get-CimInstance is the preferred method instead of Get-WmiObject for quite some time.
Text Based OS > Object Based OS
Everything that is wrong with PowerShell in my opinion is driven by the Object Oriented nature of Windows as an OS.
Since everything in Linux is text, grep is king.
Don’t you think immediately getting the property you’re interested in from an object is easier and more readable than first grepping some output to get the line you want and then removing the leading and trailing garbage on that line manually?
I thing PS scripting would be much more fun if the words weren’t so annoyingly long.
It would be better if they leaned into it. Instead it is object based…. Until it isn’t because then it’s clunky.
Microsoft products in this area are weird to me. Like C#, Powershell is great on one hand yet annoying and more difficult to rangle on the other compared to other solutions that are out there.
At least it's more readable than Bash.
Although that's not much of an accomplishment.
Please explain for a dummy.
OP was trying to get the information for a hard disk in their computer, but after running a command it looks like the serial number for that disk is
💙BThe humor is in the amount of hoops to jump through to get some basic info out using Powershell. Under Linux one would use a single command or just check what the system exposes in the form of a file.
I have no idea how to do forensics under Windows to be honest. You'd probably have to write something to get to the block layer so it can be dumped and analyzed. Perhaps OP can amuse us how he went about it.
It's just one command with a bunch of selects, you could probably just run the first part. I can try it myself later.
There are a lot of software that forensics can use, I don't know how common windows is but considering its usage for everything else in companies and governments, I wouldn't be surprised if forensics use primarily Windows.
