Find me more often on Bluesky: https://bsky.app/profile/teknomantik.old-home.net
Nerdy guy with opinions, mostly that people should care about each other. Dad, sysadmin, overly-distracted anime fan, baseball and hockey enjoyer. Pronouns in bio, deal with it. He/him.
Updated social stuff:
My Twitter account is abandoned and soon to be empty save for my final tweet from October 2023.
I'm here infrequently at best. Find me on Bluesky: https://bsky.app/profile/teknomantik.old-home.net
Nerdy guy with opinions, mostly that people should care about each other. Dad of two awesome young humans, sysadmin for the money, overly-distracted anime fan, baseball and hockey enjoyer. Pronouns in bio, deal with it. He/him. ⚾ #Rockies 🏒 #GoAvsGo
Cursed one-liner:
(Get-Date).AddMinutes(((cscript //nologo c:\windows\system32\slmgr.vbs /dlv
| Where-Object { $_ -like 'Timebased*' }) -replace '^T.*: ([0-9]+).*','$1'))
@steter I'm not even a dev, just a sysadmin, and I've lost count of the times I've seen unsanitized string inputs/non-parameterized queries that could easily be abused for SQL injection. The giveaway is usually if you see something that breaks in weird ways when there's an apostrophe in the input.
That said, there are ideally multiple protections in place. For instance, service accounts used for collecting untrusted inputs should have the bare minimum privilege necessary to do their job.