James Brundage | MVP
@mrpowershell.com did:plc:hlchta7bwmobyum375ltycg5
Jack of all Trades, Master of PowerShell. Prolific Programmer Microsoft MVP in Azure / PowerShell https://mrpowershell.com/ https://github.com/StartAutomating https://github.com/PowerShellWeb NB, Neurodivergent, Nerdy, Newsjunkie. Ask me anything.
Bluesky’a katılma tarihi:
- Takipçi
- 1.847
- Takip edilen
- 529
- Post
- 5.195
- Sıralamaya girdiği gün
- 0
Özet
James Brundage | MVP (@mrpowershell.com), 8 Ağustos 2023 tarihinde katılan bir Bluesky kullanıcısı. 1.847 takipçisi var, 529 hesabı takip ediyor ve 5.195 post paylaştı.
Sıralama geçmişi
Bu hesabın postlarının Debya günlük listesine girdiği en iyi günler.
Bu hesap henüz günlük sıralamaya girmedi.
Son beğendiği postlar
Bluesky ağındaki herkese açık beğeniler.
Well since this recent event got me interested in Powershell, can you suggest any resources for a Linux person (who mostly does Perl for scripting?)
Postu gösterWell I actually did those things to recover candidates, but stopped when I found the keys from the 4104 events (which we now known they dont work because of the bug). I dont recommend anything to anyone because all of this is very deep into FAFO territory, I just work on backups
Postu gösterCould this be done after the fact though using whatever logs were maintained by the compromised system? This is an interesting feature of powershell , which I was glad to find it runs on Linux too 🤣
Postu gösterAbsolutely share the thoughts. Thinking of auditing the pagefile but to be honest this is a longshot. Still one never knows, but I definitely dont want to try to reconstruct from the filesystem
Postu gösterIt was a AES256 , so the data are unrecoverable. We didn't pay the ransom and the hospital was effectively up and running in less than 24hrs. People with BYOD device compromises like me are sorta evaluating options. I was hopeful I could recover the key that was used (I did) but is useless
Postu göster
Blokladığı hesaplar
Bluesky’da bloklar herkese açık kayıtlardır.