Does anyone proofread anymore? This is from a breach notification letter from a county agency. The notification letter is dated January 19, 2023 and states, in relevant part:
"What Happened?
DPSS is writing to you because of a privacy incident that occurred on January 19, 2023 at the County of Los Angeles (County) DPSS. A County employee accessed your personal information contained in our electronic systems without a legitimate business reason. County personnel discovered the incident during an internal investigation on December 27, 2022. "
And of course, they don't explain why the lengthy gap between discovery and notification -- unless the notification really was sent on January 19 and they are just first sending it to the state now? What a confusing submission.
I still need to fix some minor annoyances in the other two, but this is fairly straightforward and simple. Please read the code and report any problems.
Will add later on a YAML file option for large batches.
il jailbreak per le Tesla è servito! L’hack sblocca tutte le funzioni a pagamento e fornisce l’accesso root
I veicoli elettrici #Tesla sono famosi per il loro #approccio immediato alla fornitura di opzioni premium.
Gli acquirenti possono acquistare immediatamente una versione “a pagamento” dell’auto e godere di tutte le funzionalità aggiuntive, oppure possono acquistare una versione base per se stessi, ma #sbloccare molte #funzionalità del #pacchetto premium come parte di un normale abbonamento a pagamento.
Did we ever find out which ransomware group hit the San Bernardino County Sheriff's Department in April?
The county issued an update last week saying they couldn't rule out that personal info and protected health info had been accessed. And I'm thinking, "Hey, you paid the attackers $1.1 million and they didn't tell you what they accessed or give you a file list or anything? Or did they give you a file list but you're saying you can't confirm the claims?"
API keys, passwords, auth tokens, cryptographic secrets… in the era of cloud-based development, we've all got a bunch of them. But where do you put them? How do you keep them safe? And how can you access them conveniently from your Python code, both in development and production, without putting them at risk?
It was super fun to interview @jerry for this week's episode of the Infosec Sidekick Podcast!
I had wanted to do this a while back; when the heat of the twitter migration was taking place, but I almost feel like now was a better time.
With the dust somewhat settled, @jerry and I talk about Information Sharing, Community Building, and how Mastadon plays a role in that.
I genuinely appreciate this conversation and hope it can provide you some value and entertainment throughout your week.
You will be sure to find gems in this episode, such as the unlikely comparison to twitter vs mastadon as Monsters Inc. Power Generation (don't ask, just listen lol)