diff options
| -rw-r--r-- | .Doxyfile | 2 | ||||
| -rw-r--r-- | README.md | 10 |
2 files changed, 8 insertions, 4 deletions
| @@ -865,7 +865,7 @@ WARN_LOGFILE = | |||
| 865 | # spaces. See also FILE_PATTERNS and EXTENSION_MAPPING | 865 | # spaces. See also FILE_PATTERNS and EXTENSION_MAPPING |
| 866 | # Note: If this tag is empty the current directory is searched. | 866 | # Note: If this tag is empty the current directory is searched. |
| 867 | 867 | ||
| 868 | INPUT = ./src | 868 | INPUT = README.md src |
| 869 | 869 | ||
| 870 | # This tag can be used to specify the character encoding of the source files | 870 | # This tag can be used to specify the character encoding of the source files |
| 871 | # that doxygen parses. Internally doxygen uses the UTF-8 encoding. Doxygen uses | 871 | # that doxygen parses. Internally doxygen uses the UTF-8 encoding. Doxygen uses |
| @@ -1,5 +1,9 @@ | |||
| 1 | # VXGG REWRITE | 1 | # VXGG Rewrite {#mainpage} |
| 2 | 2 | ||
| 3 | ## The first attempt was shit, so I did it again | 3 | ========================== |
| 4 | 4 | ||
| 5 | VX-GAMBLEGROUND, aka VGXX, is a piece of "funware" I wrote. It's ransomware with a twist: it's not meant to completley fuck your system, just temporarily encrypt your stuff until you win a game of slots. The end product, although working, was not great. Because I have recently found myself with freetime and a new unending boredom, I decided I might as well rewrite this into something I could be slightly more proud of | 5 | ## A Rewrite Of The Abysmal VXGAMBLEGROUND Ransomware |
| 6 | |||
| 7 | VXGAMBLEGROUND, aka vxgg, is a bit of fun ransomware I wrote a while back. The joke, inspired by telegram degens, was that the unfortunate victim of this ransomware would have to gamble bitcoin at a slot machine to get their files back. A combination of the joke losing its humor and curses being annoying led me to a state of begruding. I got to a point where I really couldn't care less about the quality of my work and just wanted to get it done, so I pushed through and created a heaping pile of spaghetti code. The final product did techincally work, but it was held together by duct-tape and dreams; one of the ways to crash the program was by resizing the terminal window | ||
| 8 | |||
| 9 | Looking back on it, I'm glad I stuck through. It was probably my first "big" C project that I actually bothered to finish, even if its finished state was hot garbage. After some more time, I've decided that I want to rewrite it, to improve on all the random shit I did and make something I could be marginally more proud of. No more corrupting files, no more silly crashes | ||