Father, author, blogger, enthusiast of all things PowerShell and automation. http://linktr.ee/mdowst
I remember before scrambling they just put blocks that prevented you from going to certain channels. I somehow figured out if you ran the cable box through the VCR first and put it on channel 2 while the TV was still on 3, it would shift all the channels down one. Cinemax was channel 14, which our box just would not go to. But it would go to 13, so doing my little trick teenage me got to watch a lot of skinamax.
If I understand correctly, the signatures generated by PuTTY aren’t perfectly random, so if someone got a hold of a bunch of keys from a server, they could figure out the pattern. It takes about 60 keys. This affects not just PuTTY, but also FileZilla, WinSCP, TortoiseGit, and TortoiseSVN.
In other words if you have NIST P-521 keys, or any others using 521-bit ECDSA, you should revoke them and generate new key pairs. After you update your software.
For some reason their API would not return anything for assembly. I was curious to see where it would rank too,
Apparently it due to an issue with Kotlin - https://github.com/code-golf/code-golf/issues/151#issuecomment-1126266250
Biggest things I’m seeing is CVE-2023-21709 for Exchange requires a PowerShell script to be run after patching. Also, CVE-2023-29328/29330 for Teams affect all devices (Windows, Mac, iOS, and Android).
The book I wrote. When I first talked with the publisher he asked, “what skills would you look for in someone who wants to do your job?” And that’s the premise I stuck with writing it.
I feel down a rabbit hole, a few years ago wonder the same thing about C#. Here is what I found.
From personal experience, it seems like things outside of your normal listening don’t affect too much. At least in my case, my daughter making me play the Encanto soundtrack 250,000 times hasn’t affected my weekly or daily playlists.
That’s pretty similar with what happened with me and the train. Kept getting random drops from a plant. I went out to investigate and everything tested perfect and the network was staying up. That was until a freight train rolled by. Turns out AT&T had run the line by shoving a piece of PVC through the gravel between two cross-ties, then running the cable through it.
I’ve actually had an excavator take out my network. I’ve also had networks taken out by forklift, train, and a semi-truck towing three other semi-trucks.
Basically every Windows sysadmin is indebted to Mark Russinovich and SysInternals. Fortunetly, PowerToys has come a long way because I’m pretty sure sysinternals haven’t been updated since Windows XP.
No Azure DevOps automatically increments it every time you run the pipeline.