Guard duty is a service you have to use. And you can configure it. So my initial claim is still valid that aws is not scanning by default ๐
https://docs.amazonaws.cn/en_us/guardduty/latest/ug/guardduty-malware-detection-scan-engine.html
" Signature-based detection not only includes matching of bytes but also a snippet of code that is potentially complex, and the scanner can parse content and make decisions."
"With no restriction on the file formats that GuardDuty scans for malware, the scan engines that it uses can detect different types of malware, such as cryptominers, ransomware, and webshells."
Any other bullshit you want to spout there, Genius?
Discussion
Yeah, and you have the "option" to enable HTTPS too. You are an absolute moron.
You definitely never heard of a read only container! Otherwise you would know that mailware is not a problem. Especially not for a fucking bitcoin node.
Consultants ๐๐๐
Moron. I'm not talking about malware activation, I'm talking about existence which a read-only container would still apply to. I'm not saying that a malware package would infect a node, dipshit. The existence of the file would make the server host kill the VM.
No it wouldnโt because it all depends on your personal settings. Which in default state donโt even exist ๐คท๐ผโโ๏ธ
Once again you claimed bullshit which doesnโt matter because all this is possible today ๐ฑ๐ฑ๐ฑ and spoiler alert! Nothing happened ๐คช
So itโs nothing more than #knotards being in full retard mode again to push the luke agenda
Again, you don't know what you are talking about. Try relaying 84+ byte transactions, it won't get past the broadcast phase. And again, I run many reference clients because I'm not a one client tard like you. I can't emphasize this enough, you are not smart enough to know how dumb you are. I'm blocking you now. Good luck not choking on your own drool.
That moment when you donโt have any arguments ๐๐๐