Thread - Nostr Hypermedia

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.

↑ Parent

Replies (3)

JackTheMimic 2 months ago

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.

1 replies ↓

JackTheMimic 2 months ago

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.

JackTheMimic 2 months ago

GuardDuty malware detection scan engine - Amazon GuardDuty

Learn about Amazon GuardDuty malware detection methodology and which scan engines does it use.

" 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?

1 replies ↓