And here's the final #mastodon #online server's rendered logo for one to create a social badge. This is done as part of my data #migration efforts. Basically I was #sanitizing the #data into actual production usable ones into my local datahub.

You still need to comply with #Mastodon #trademark requirements here:

https://joinmastodon.org/branding

Check it out at:

1. https://github.com/ChewKeanHo/visuals-trademarks-mastodon-online-1200x630

For those on #mastodon #social servers, here are the rendered logo for one to create "social badge" and link to your profile. This is done as part of my data #migration efforts. Basically I was #sanitizing the #data into actual production usable ones into my local datahub.

You still need to comply with #Mastodon #trademark requirements here:

https://joinmastodon.org/branding

Check it out at:

1. https://github.com/ChewKeanHo/visuals-trademarks-mastodon-social-1200x630

Over the weekend, I re-drawn some #mastodon trademark logos based on https://joinmastodon.org/branding guidelines as part of my data #migration efforts. Basically I was #sanitizing the #data into actual production usable ones into my local datahub.

Check them out at:

1. https://github.com/ChewKeanHo/visuals-trademarks-mastodon-1200x1200
2. https://github.com/ChewKeanHo/visuals-trademarks-mastodon-1200x630

Jeffrey #Epstein 's brother says the #FBI is #sanitizing the #Epstein files and redacting " #politicians" #names before release ..

What did you expect.. ?

The #Microsoft report on the technical investigations for #Storm0558 key acquisition is a rather interesting read.

They of course can't and don't go into specifics about the nature of the key leakage. I'm totally guessing here, but it might be that the tooling Microsoft used to detect and sanitize the #keymaterial didn't identify the key in the specific key schedule form. Maybe a new #encryption cipher was used that uses a new key schedule format that the tooling didn't support, or the cipher implementation started to store the key schedule in a new, different way.

This incident is a good example on how attempts of #sanitizing logs, memory dumps and similar of sensitive information are a losing game. At best it can be considered best effort, there's always ways information can end up leaking out despite your best efforts in trying to identify it.

For critical systems the encryption key should only ever exists in a security enclave or HSM. That'd be the only way to ensure that the key cannot leak: It's nowhere in the memory to begin with.

ref:
https://msrc.microsoft.com/blog/2023/09/results-of-major-technical-investigations-for-storm-0558-key-acquisition/