Server Setup

We have been able to setup the Linux server on which we will eventually run our Twisted server for data recording. I fixed a couple of bugs within our email generator and spoofer. We have created and started working on the Twisted web server that is the next part of our project.

With fall break occurring this past weekend we have gotten less done was desired. However we continued to work with our email generator and sender in order to fix a few bugs. For example our program was configured incorrectly and would not let the user pass an email into the program and it would only use the one found referenced within the configuration file. In addition we got some time to look over and research Twisted a little bit more. We should hopefully get a prototype of the Twisted server setup within the next week/week and a half in order to record data from the targets interacting with the emails.

Phishery

My partner and I were able to get our code together this week and we have managed to get a majority of it working. We have a controlling class set up that will accept inputs from the user if they exist or otherwise grab information from the yaml config file. The controller will then grab the list of users from the csv and generate the unique email before sending each one to its  recipients. The emails are not all going through to their destination, some are halting at spam filters so this week will hopefully be spent QAing and fixing these emails so they can properly arrive at their destination. We have also decided, for the moment, that we will name our project Phishery. At east until we come up with a better name.

Spoofing Emails

Since I have gotten my configuration file set up and have successfully ran my href replacer it is now time to attempt to hook these up with the SimpleEmailSpoofer. I started my importing my own fields from my configuration file or by passing them directly to the spoofer class. I then proceeded to weed out the unnecessary fields that the original class offered. Next I reworked how the actual message was created due to both the difference in storing/generating information and the removal of some fields. Finally I was able to wrap it all up nicely within one method, that would be able to be called from a controller, requiring only a passed email and receiving email address to send a spoofed email. after fixing a few bugs I was able to successfully able to send a spoofed email such as the following.


I tested out a few emails and saw that while a few of the emails went to the inbox of the receiver (which was me) a few ended up getting flagged by gmail's automatic spam filter and ended up in my spam folder instead. This will require further testing to make sure this would not happen during an actual experiment.

Within this next week I hope to get together with my partner so that we can make a joint controller class and successfully hook up all of our code we have been working on for the past month. This will allow us to read "target" data from a csv file similar to the one that will be similar to the one we are going to use later in the experiment, generate the unique emails for each "target", and then send the email from a spoofed address.