PiD4x wrote:NeoTheOne175 wrote::shock: @ PiD4x's posts
You must really spend a lot of time thinking about this!
lol, it took about 10seconds for those ideas to come/ expand on what FORCEMAN said - and then about 25 mins to write it all write down / write down new ideas as they came in haha
You wonna see crazy you should see all the .txt files and half-finnished POC code (I get bored real fast and move on to somthing else and come back like 6 months latter haha) thati have in my my docs folder . All new, never seen b4 ideas (at leasst google turns up no results lol), that are slightly 'crazy', yet feasable, that are on my "todo list" ranging from ides about cryptography hardware that sit between the HD and controler (actualy most of the time there was reading those ata specs, like 3pdf's with 900pages between them! - but the SATA parts where kind of interesting lol), to MMOLRPG's and everything inbetween lol
Wow. Just...wow. I'm no programmer, so I probably wouldn't be able to fully understand all the work you've put into this, but I am interested in cryptography software, especially public-key encryption. I've already found a number of different cryptography applications free online that I plan to install on my computer.
PiD4x wrote:-basic spreader can hit public access machines
-spreader 2.0 can hit public access and internal services
- 3.0 can hit mainframes, etc.
What I think would be better than this would be to have v1 hit only "Level 1" ISMs (i.e., the ISMs that only have a monitor as a defense) and does the least damage (maybe only wipes logs on system?). v2 hits better-defended ISMs (monitor, proxy, firewall) and mainframes and wipes logs and usr. v3 hits ISMs, mainframes, and LANs, and wipes logs, usr, and sys. Public access machines are omitted because you can't hack them, and even if you could, you wouldn't be doing any significant damage (after all, they only have a couple of phone numbers). Perhaps you could add a "chance-of-success"-type factor into each version of the spreader. Maybe each version could have a 100% chance of success for a certain task (i.e., v1 has 100% chance of wiping logs on target ISM), but you can direct it to try to do more damage (like wiping usr or sys) with a smaller chance of success; v1 would have the smallest chance of success of doing anything but wiping the logs (something miniscule like 5%-10%). v2 would have a better chance at doing more damage and possibly spreading to other systems owned by the same company (15%-40%). v3 would have an even better chance (50%-75%), and v4 would have a 90%-100% chance.