We are open to everyone who wants to be a part of this project and continue to make it the best MiTM tool available.
The Ettercap source code is stored on the Sourceforge pages using a GIT repository. Below are the steps to you should follow to ensure you are working off the same code base as everyone else involved in the project.
root@your_machine: ~# - git clone -b ettercap_rc git://ettercap.git.sourceforge.net/gitroot/ettercap/ettercap ettercap_rc root@your_machine: ~# - git checkout ettercap_rc
Once you moved to the rc branch you can begin to review the current source code in development.
Please note that very few individuals have the ability to commit code directly within the GIT repository.
How to submit code you've worked on
1 - Once you've worked all the known bugs out of your code, you can create a patch file and send it to the ettercap.project gmail account
2 - One of the core developers will review the code, make any necessary changes and merge the code into the proper branch.
3 - You will receive full credit as a contributor to the project within the source documentation.
Testing can occur at anytime and should be completed against the ettercap_rc branch. However, an e-mail will be sent out on the 1st of every month to everyone who requested to be part of the testing team that will include any changes made compared to the last release.
When compiling ettercap be sure you purge all other instances and prepare for a clean installation. Do not compile with any flags other than debug in order to ensure a consistent test across the entire testing base.
During testing, you can test however you want, but there are a few high level principles that will need to be followed:
- Ensure you include as much information about your system as makes sense (uname -a may possibly be enough)
- If you report a bug we need full details of what you were doing when it happened, and what you expected to happen
- If an actual crash occurs provide the file that ettercap creates so we can review exactly what was happening when the crash occurred
- Detail, detail, detail, the more details you can provide the better chance we have to replicate the issue and fix it.
Development & Testing Schedule
All code needs to be submitted by the 20th of every month. If your code is not received by the 20th, then it will be put off until the following month.
All code received by the 20th of the month will be reviewed and included where applicable.
A call to all testers will go out via the beta testing lists and other social media sites on the first of every month.
Official testing will close on the 10th of every month with the goal to complete a monthly release around the 15th of each month.