Okay dude.
1. When you verify a block you have to decrypt and orient the data in ordered bytes.
2. When you run a node on hosted servers, the company hosting it scans all transmitted, saved, and processed RAM data for malicious package fingerprints.
3. These fingerprints are just a hash digest of the bytes of a known malicious package.
4. Seeing the fingerprint CONTIGUOUSLY of a malicious package the server host would kill the VM that they host your Nginx or Apache2 instance on.
5. This would happen as soon as you try to verify the transaction with an OP_RETURN output.
6. I and many others have explained this ad nauseum but morons like you don't understand how Bitcoin works so you just post "This isn't a hacker movie" type shit as if you understand something you clearly don't.
7. GFY I don't care what you have to say.
2. Is false! AWS for example does not scan data on ECS, EKS, S3 or whatever by default so your claim is bullshit
Literally do. Why don't you try to set up a server, and send Xor'd malware packages to it. Have your server decrypt it, then tell me if your instance is accessible.
That’s bullshit, but can send me the documentation where AWS is scanning a service set up by yourself. I will wait…
Okay so, you're retarded gotcha.
Thread collapsed
Thread collapsed
Thread collapsed
Do you know what hash digests are? It doesn't "know" what the data is. It compares the data to a hash digest of know malware.
{
If (4D616C77617265{data scanned}==4D616C77617265
then (kill service)
}
This is not secret information.
Thread collapsed
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?
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 😂
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 😂😂😂
Thread collapsed
Thread collapsed
Thread collapsed
Thread collapsed
Thread collapsed
Thread collapsed
Thread collapsed
Thread collapsed
Thread collapsed
