Posts: 1,272
Threads: 119
Joined: Apr 2022
Reputation:
100
While I encourage all types of code to be written and studied I would caution anyone on posting such a piece of code. You could, hypothetically, be held responsible for any damage a script-kiddy may inflict on a system(s) using your code, modified or not.
The furthest I have ever taken it, and then I even took pause to consider my actions, was sharing "joke" style programs that would do things like simulate the command prompt and give silly responses to commands or take over the GUI for a short period of time pasting bullet holes on the screen wherever the user clicked. Even something like this may prompt a user to reset their system thinking it has been infected causing them to lose unsaved work and hence, inflicting damage.
It's a slippery slope in my opinion. Tread lightly.
New to QB64pe? Visit the QB64 tutorial to get started.
QB64 Tutorial
Posts: 301
Threads: 16
Joined: Apr 2022
Reputation:
51
I think that's just so called malware, Steve. A computer virus has to reproduce itself, inject its own code into other executables or email copies of itself. maybe it's possible with OPEN "x.exe" FOR BINARY AS #1 but could you inject something as bloated as QB64PE output as well?
Posts: 1,586
Threads: 59
Joined: Jul 2022
Reputation:
52
A determined hacker could write in any programming language. Since QB64(PE) just waters down BASIC code to C++ it might be the bed for some "real adjustments".
Now there are such things as "malware hunters" in how some Linux distributions are being advertised. After Kali Linux there seems to be a great obsession with not leaving a trace after enough web surfing, and with finding the "enemy" before they find you.
Posts: 733
Threads: 30
Joined: Apr 2022
Reputation:
43
Tread on those who tread on you