infosex.exchange <3

You are probably looking for the infosec.exchange Mastodon instance

This host is mostly for my random stuff, and in little part acts like a well-intentioned placeholder for the typosquatted domain.

Discoverability and Archiving

Currently I'm using this host for saving the items from my own feeds to the Wayback Machine and provide in-links for search engines. I hate that I have to do this, but the non-sense ideology of Mastodon pretty much ruined the search feature for Fediverse as a whole, and this wasn't changed by the fact that they owned their mistake and implemented search eventually.

Yes, I (or anyone else) could do similar things with other peoples published feeds, regardless of the tantrum. No, you can't defederate this, because the process doesn't rely on an instance.

Gluttony Section for Search Engines

C Harness to #LibAFL

https://github.com/v-p-b/libfuzzer_kfx/blob/main/C2LIBAFL.md

I nice part of making an archive of my Twitter posts is that I realize I wrote stuff like this o.O #fuzzing
this post | permalink
@cR0w @cybersoldier And probably Headscale (or Tailscale if you are fine with SaaS)
this post | permalink
I implemented threading in my RSS2Bsky script so my larger posts are better propagated across networks:

https://github.com/v-p-b/rss2bsky.py

#RSS #Syndication #Bluesky #POSSE
this post | permalink
This is a long test post, sorry...

Secure trust data mining linux cache poisoning encapsulation cyclic redundancy check cloud computing PKI signature FTP hijacking. Trust ephemeral port IP forwarding linux stream cipher port exponential backoff internet control message protocol race condition full duplex exposure IP spoofing. Challenge-handshake authentication protocol public key hypertext markup language topology war dialing disaster recovery plan decryption authorized. Account harvesting masquerade NAT stream cipher, cookie intranet certificates patch covert channel penetration test tunnel IP forwarding egress filtering.

https://www.securityipsum.com/

Ephemeral port reverse engineer fingerprint form-based authentication day zero. FTP UDP address resolution protocol boot sector, PPTP ransomware business continuity plan intrusion detection. IP flooding authentication disaster recovery plan corruption decryption MD5 dictionary attack socket egress filtering fragment digital signature exponential backoff worm. Reverse proxy encapsulation shell tunnel bastion host.
this post | permalink
This is a long test post, sorry...

Secure trust data mining linux cache poisoning encapsulation cyclic redundancy check cloud computing PKI signature FTP hijacking. Trust ephemeral port IP forwarding linux stream cipher port exponential backoff internet control message protocol race condition full duplex exposure IP spoofing. Challenge-handshake authentication protocol public key hypertext markup language topology war dialing disaster recovery plan decryption authorized. Account harvesting masquerade NAT stream cipher, cookie intranet certificates patch covert channel penetration test tunnel IP forwarding egress filtering.

https://www.securityipsum.com/

Ephemeral port reverse engineer fingerprint form-based authentication day zero. FTP UDP address resolution protocol boot sector, PPTP ransomware business continuity plan intrusion detection. IP flooding authentication disaster recovery plan corruption decryption MD5 dictionary attack socket egress filtering fragment digital signature exponential backoff worm. Reverse proxy encapsulation shell tunnel bastion host.
this post | permalink
@swapgs It really feels like some prod manager pushed through this genius idea without asking security first
this post | permalink
"Recall snapshots and associated data are protected by secure VBS Enclaves."

"protects against malware through rate-limiting and anti-hammering measures"

"biometric credentials protect your privacy and actively authenticate you to query your semantic indices and view associated snapshots."

Sounds like MS did their homework. Still hate the idea though...
this post | permalink
Update on Recall security and privacy architecture | Windows Experience Blog
https://blogs.windows.com/windowsexperience/2024/09/27/update-on-recall-security-and-privacy-architecture/
this post | permalink
Previewing Recall with Click to Do on Copilot+ PCs with Windows Insiders in the Dev Channel
https://blogs.windows.com/windows-insider/2024/11/22/previewing-recall-with-click-to-do-on-copilot-pcs-with-windows-insiders-in-the-dev-channel/

Here we go again...
this post | permalink
OZZ: Identifying Kernel Out-of-Order Concurrency Bugs
with In-Vivo Memory Access Reordering

https://dl.acm.org/doi/pdf/10.1145/3694715.3695944

/via exploits.club
this post | permalink
Next Page