search

pentestgeek / phishing-frenzy-templates

Phishing Scenarios Used for Phishing Frenzy
206 stars 104 forks source link

Template: Travel Agency #2

Closed frenchzilla closed 10 years ago

zeknox commented 10 years ago

Nice work @frenchzilla ! Really excited to take a look at this PR template. In the meantime could you try to structure your files in this fashion:

root
|--archive
|   |-- templateName.zip
|
|--email
|   |-- email.html.erb
|
|--images
|   |-- email.jpg
|   |-- website.jpg
|
|--www
|   |-- index.php
|   |-- failed.php

Let me know if you have any questions about the structure.

Thanks!

zeknox commented 10 years ago

If you are having issues getting this structure into github here is a very basic generic workflow that might assist.

clone your forked repository:

git clone git@github.com:frenchzilla/phishing-frenzy-templates.git

create a separate branch for this new template. Not required but a best practice

git checkout -b travel_agency_template

now if you check the status you should see that your branch is clean and doesn't have any staged changes:

git status

Now you can copy in your folder into this directory that incorporates the template you have built. Once you have copied it into this directory you can run git status again to see the staged files.

Once you are ready to you can add the files to a commit:

git add .

Run git status once again and you can see files have been added to the commit.

Now we need to commit these changes with a message

git commit -m 'added travel agency phishing template that is working well'

Once you have committed the changes, you can push them up to your forked repository in preparation for a Pull Request.

git push origin travel_agency_template

Now this branch will be pushed to your forked repository. You can browse this branch in the github web interface and choose the submit pull request option.

Hope this helps!