Just an update on how all things wendigo are going. I’ve been pretty busy/away recently so I’ve had a bit of a break from code/blogging, but I’m back.
The highlights are:
– Emailing a random from GitHub to ask about their code, I was writing a cryptomining wendigo module (which is currently just wishful thinking, I need to get a c implementation cause python is really slow, and possibly find a way to throttle the thread so I doesn’t take up too many cpu resources, which would be suspicious, and find a way to exit after a certain amount of time, or update the main program so threads can be killed gracefully), anyway, I came across a funny line of code: if os.fork() or os.fork(): sys.exit(). I had my suspicions, and I knew how it worked (forking, short circuit evaluation, etc.) but I couldn’t quite figure out its purpose. But I found out that double forking detaches from the terminal such that when thee terminal is closed the process isn’t killed, handy. Ideally wendigo is running as a daemon, and doesn’t close when it’s parent does, and it’s also a little less suspicious if it’s parent isn’t around. So, stolen.
– I put my first year algorithms lectures to good use with a data mining module. It uses a depth first search (with a stack) to search for word documents, pdfs and text files. But more importantly, when it finds them, they are encrypted and pushed to GitHub for easy access, without compromising the stolen data (because if anyone else wants the data they’ll have to get it themselves, or just buy it from Google).
My Portfolio 