@vxunderground tbf, historically, if you’re running a small campaign, deliberately getting a common, mostly harmless (as in ”just need to clean it out”) detection is a great way to not get any analysts looking deeper
this of course falls apart if it in any way gets attention
@vxunderground trying to prove a system you don’t control is secure purely based on code and output running on that same system is cooked from the get go, it’s just a cat and mouse game
on desktops you don’t have a hardware chain of trust, on laptops it effectively ends at the firmware
@MeatyClaus@vxunderground they don’t need to do that, they can always just redirect you regardless, but they have to be under hella load to even want to do so, since you pay more for the cutting edge
@NewPlatinumm@vxunderground Azure itself integrates it in some places, like “confidential VMs”, which will only release the keys used to decrypt the OS disk if attestation passes
@NewPlatinumm@vxunderground the point of attestation is basically to get “proof” that a machine is not compromised somehow. this can be integrated into other systems which would only release secrets if the machine is attested.
@TeeWithNoSize Okay, but regardless, if you’re banned from the platform used for CVD, how do you propose that they should do CVD if they even wished to?
Microsoft can’t whine about CVD if they’ve closed the door in the first place!
@0xfluxsec@vxunderground Shoutouts to whoever in the industry decided to read my blog post and actually add rules to detect that adware that plagued keygens for years though. Seems the way to reduce false positives is to make better rules yourself 🙃
@0xfluxsec@vxunderground At the same time, Defender hasn’t even caught a real virus on my machine in years, just endless Wacatac false positives, and “HackTool” detections that I can’t exclude. Norton 2010 could be configured to exclude based on detected names, why can’t Defender?
Did you know RPCS3 was the second software to implement the Vulkan API?
Back in 2016, shortly after joining RPCS3, kd-11 implemented a Vulkan renderer on March 10 - less than one month after the API's release on February 16.
The first game on the list was Vulkan's launch title.