4 ms·
On the topic of scanning a device for CSAM, even if this were extended to computers, and Microsoft/Linux/etc. coded it into the OS, how would this even work whe
by Jigsy 3y ago
On the topic of scanning a device for CSAM, even if this were extended to computers, and Microsoft/Linux/etc. coded it into the OS, how would this even work when it comes to RAM where an image isn't directly touching a hard drive? (Though I'm not sure how that would work exactly.)
Esp. in cases like isolated virtual machines running old versions of say Windows or Linux where child molesters and pedophiles don't have to worry about the scanning software.
I can't pretend to be an expert on the subject, but isn't a VM in a separate area of RAM where it doesn't bleed out?
- dcow 3y agoThey hypervisor or host OS can just read the memory.
- Jigsy 3y agoI see. That said, continuous RAM scanning would be incredibly resource intensive.
- justinclift 3y agoDon't AMD server class processors have some way to encrypt VM memory so the host can't read it? Looking around quickly, it seems to be Secure Encrypted Virtualization (SEV): https://www.amd.com/en/developer/sev.html https://www.amd.com/en/developer/sev.html
- vaylian 3y agoThe chatcontrol law does not require scanning on the OS level. The chatcontrol law requires scanning on the ISP level and on the internet service level. That means: * ISPs are required to check for connections to flagged servers. They also have to check for illegal URLs (yes, HTTPS will make that pointless) * Services like chat/e-mail/file-sharing services need to effectively check if a user is sending illegal material (no, the law doesn't take into account the complexity of open source ecosystems and the many options you have for client software and server hosting options)