| Bsky | https://bsky.app/profile/cornanon.bsky.social/ |

| Bsky | https://bsky.app/profile/cornanon.bsky.social/ |
…
…
… hey @da_667 , @reverseics , and @hacks4pancakes , I may have found a game that’s relevant to interests. 🌽😸🌽

Date Everything! is a sandbox dating simulator set in the comfort of your own home, featuring 100 fully voice acted datable characters! Let the romance flow between your bed, smoke alarm and… Overwhelming Sense of Existential Dread? Are you ready to Date Everything?
No matter how vague or oddly specific a security concern is, if it's real, there exists some infosec nerd that hyperfixated on it years ago far past the point of expertise.
There's also roughly a 30% chance this nerd is trans, and another 30% chance this nerd is a furry, and a 25% chance they're both.
The pcapng file format stores a ton of crazy metadata in your files. What exactly gets stored depends on what is used to create the pcapng file, but Wireshark and mergecap do reveal a bit about the computer used to create the pcap.
@netresec wrote a nice blog post about this a few weeks ago, including how to make regular pcap the default setting in wireshark (and Erik reached out to me to warn me about some pcaps I had shared publicly, I still need to update my git repo to remove said pcapng files...how annoying of a process it is to do this! So don't be a dummy like me, make pcap your default, and be cautious where you share pcapng files).
Did you know that there is a setting in Wireshark for changing the default save file format from pcapng to pcap? In Wireshark, click Edit, Preferences. Then select Advanced and look for the capture.pcap_ng setting. Change the value to FALSE if you want Wireshark to save packets in the pcap file form[...]
Anyone who talks publicly about using burner phones is doing OPSEC cosplay.
Every word of the prior sentence is load-bearing.