[Snyk] Security upgrade setuptools from 39.0.1 to 65.5.1

.codeclimate.yml

@@ -0,0 +1,23 @@
+version: "2"
+checks:
+  method-count:
+    config:
+      threshold: 50
+exclude_patterns:
+  - "parsers/examples/"
+  - "debian/"
+  - "deps/"
+  - "scripts/"
+  - "wordlists/"
+  - "backup/"
+  - "docker/"
+  - "log/"
+  - "tmp/"
+  - "images/"
+  - "**/__init__.py"
+  - "**/*.conf"
+  - "**/*.sh"
+  - "**/*.qss"
+  - "**/*.txt"
+  - "**/*.yml"
+  - "**/*.md"

.flake8

@@ -0,0 +1,4 @@
+[flake8]
+select=E501,F811,F823,F831,F841,E502,E703,E704,E713,E741,E742,E743,W291,W601,W602
+exclude=.git,.idea,tmp,backup,log,images,venv
+max-line-length: 120

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,37 @@
+---
+name: Bug report about: Create a bug report title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Legion version**: {Enter Legion version you are running}
+
+**Which install method are you using**: {Choose either 'Docker' or 'Traditional install' method}
+
+**DESCRIPTION**
+
+Enter a clear description. E.g., It's dark in the room.
+
+**PRECONDITIONS**
+Describe any preconditions that might be required. Be specific. Include versions, execution method, operating system,
+and anything else that might be needed to replicate the conditions. E.g., Be in room 5a on 123 plop lane, Plopsville,
+NY. It's a soulless modern retrofit within a once beautiful and grand building. It's hidden by a poorly painted dark
+green door six rooms down from the elevator with a cartoon drawn on it over on the west side.
+
+**STEPS TO REPRODUCE**
+Describe the sequence of events needed to reproduce the problem. E.g.,
+
+1. Enter room 5a.
+2. Flip light switch.
+3. Realize it's still dark.
+
+**EXPECTED RESULT**
+Enter a clear description of what you expected under normal conditions. E.g., A lit room.
+
+**ACTUAL RESULT**
+Enter a clear description of the outcome deemed to be a problem. E.g., A dark room.
+
+**ADDITIONAL INFORMATION**
+Enter any additional relevant information including screenshots. E.g., The room has a distinct smell. The switch used is
+on the left side of the door.

.gitignore

@@ -102,3 +102,28 @@ venv.bak/
 
 # mypy
 .mypy_cache/
+
+# temps
+tmp/
+
+# init
+.initialized
+
+# extension scripts
+scripts/ms08-067_check.py
+scripts/ndr.py
+scripts/rdp-sec-check.pl
+scripts/smbenum.sh
+scripts/snmpbrute.py
+scripts/installDeps.sh
+scripts/smtp-user-enum.pl
+scripts/snmpcheck.rb
+
+scripts/CloudFail
+
+docker/runLocal.sh
+docker/cleanupUntagged.sh
+docker/cleanupExited.sh
+
+log/*.log
+fixname.sh

.travis.yml

@@ -0,0 +1,33 @@
+env:
+  global:
+    - COMMIT=${TRAVIS_COMMIT::8}
+
+language: python
+
+sudo: true
+
+python:
+  - 3.6.9
+
+cache: pip
+
+install:
+  - cp ./requirements.txt ./deps/
+  - bash ./deps/installPythonLibs.sh
+
+script:
+  - flake8
+  - python -m unittest
+
+after_success:
+  - (test $TRAVIS_PULL_REQUEST != "false") && exit 0
+  - (test $TRAVIS_BRANCH != "master" && test $TRAVIS_BRANCH != "development") && exit 0
+  - cd ./docker/
+  - echo "$DOCKER_PASS" | docker login --username $DOCKER_USER --password-stdin
+  - export REPO=gvit/legion
+  - docker build -f Dockerfile -t $REPO:$COMMIT . --no-cache
+  - docker tag $REPO:$COMMIT $REPO:travis-$TRAVIS_BUILD_NUMBER
+  - test $TRAVIS_BRANCH = "master" && docker tag $REPO:$COMMIT $REPO:latest
+  - test $TRAVIS_BRANCH = "master" && docker push gvit/legion:latest
+  - test $TRAVIS_BRANCH = "development" && docker tag $REPO:$COMMIT $REPO:development
+  - test $TRAVIS_BRANCH = "development" && docker push gvit/legion:development

CHANGELOG.txt

@@ -0,0 +1,113 @@
+LEGION 0.3.9
+
+* Start time message box ensuring run as root
+* Start time message box to help users resolve NMAP v7.92 segfaults
+* Bug fixes for edge cases
+* Screenshot tool revisions
+* Default config revisions
+* Open maximized
+* Don't open with top of window off screen
+* Stage module revisions (nothing hard coded anymore, adds option to specify any NSE script for any stage)
+* Ensure pyExploiutDb is updated at all times
+
+LEGION 0.3.8
+
+* Bug fixes
+* Preparation to move to postgresql backend
+
+LEGION 0.3.7
+
+* Bug fixes for several edge cases
+* Screenshot fixes
+* Service version data overwrite bug fixed
+* Stale service version data bug fixed
+* Refactor of docker base image
+
+LEGION 0.3.6
+
+* Significant code refactoring
+
+LEGION 0.3.5
+
+* Bug Fixes
+* Copy from tables using double click
+* CVE -> ExploitDB redesign using pyExploitDb and bugfixes
+
+LEGION 0.3.4
+
+* Depnendancy polish
+* Minor UI and schedule changes
+
+LEGION 0.3.3
+
+* Fix hydra 8.7+ issues
+* Fix minor UI update issues
+
+LEGION 0.3.2
+
+* Stage 3 is now vulners scan
+* Former stages 3, 4 and 5 are respectively 4, 5 and 6 now
+* Config editor dialog
+
+LEGION 0.3.1
+
+* UI polish everywhere (element sizing, scaling, icons, tooltips, etc.)
+* Code cleanup
+* UI performance improvements
+* More port actions
+
+LEGION 0.3.0
+
+* UI polish everywhere (element sizing, scaling, icons, etc.)
+* Code cleanup
+* Highly configurable host addition dialog
+* Stability improvements
+* Docker image of preconfigured application published to DockerHub
+
+LEGION 0.2.4
+
+* Open SPRT and Legion files
+* Resolve file open/save access issue
+* Consolidate lower panel
+
+LEGION 0.2.3
+
+* Bug fixes for edge cases
+* Elapsed and estimated remaining time for processes
+* Host 1-M CVE UI element added
+* Service 1-M CVE UI element added
+* CVE object model revised
+* Improved UI performance
+
+LEGION 0.2.2
+
+* Bug fixes for edge cases
+* In UI Logging panel
+* Thread safe logging
+* Add AzureCveQuery Plugin
+* Setup to use AsyncIO
+* Dep installer fixes
+* Addition of .justcloned to re-initalize on cloning / pull to update
+
+LEGION 0.2.1
+
+* Fixed DB relationships
+* Removed X requirement for screen captures
+* Revised HTTP/HTTPS detection
+* Fixed Host panel columns
+* Fixed process lanuches for discovered services
+* Fixed context menus so they show applicable actions for context
+* Fixed note unique keys
+
+LEGION 0.2.0
+
+* Port to PyQt5
+* Handle process output encoding issues
+* Added dependancy installer
+
+LEGION 0.1.1
+
+* Support for WSL (Windows Subsystem for Linux)
+* Removed Elixir
+* Converted to Python3.5+
+* Process handeling ensures dead processes are shown as crashed or finished

CONTRIBUTING.md

@@ -0,0 +1,44 @@
+# Contributing
+
+Are you interested in contributing to Legion? We love contributors! We ask that you follow the guidelines below when
+making contributions to the project. We ask that you also follow our contributor [**Code of Conduct**](#code-of-conduct)
+. We look forward to working with you - get started in one of the sections below.
+
+#### Did you find a bug?
+
+* Awesome. First, ensure that your bug isn't a duplicate by checking
+  the [Issues](https://github.com/GoVanguard/legion/issues). **If the issue already exists**, go ahead and comment on
+  the issue with your bug report information, following the guidelines below as if you were reporting a new issue - just
+  don't make a new issue.
+* **If you can't find the issue**, its time to [open a new issue](https://github.com/GoVanguard/legion/issues/new). Fill
+  in the issue with a clear title and description. Where possible, include steps to reproduce the bug, code samples, and
+  screenshots. Tag the issue if it fits into one of our existing categories.
+
+#### Did you patch a bug?
+
+* Excellent - your first steps are to open a new [Pull Request](https://github.com/GoVanguard/legion/pulls) with your
+  patch. Be prepared to answer questions or receive feedback from the team.
+* Ensure the PR has a description that clearly details the problem and your solution. Be sure to include issue numbers
+  if possible.
+* Follow our coding practices and standards for whatever files you're working on.
+
+#### Do you want to add a feature?
+
+* We love new features! Please [make an issue](https://github.com/GoVanguard/legion/issues/new) for discussion, with a
+  clear title and description of the proposed feature. Add the Proposal tag, and use the comments to follow up with the
+  team.
+* Wait for a response and approval to your proposal before working on your patch and submitting a PR. This way, if we
+  find any problems with the proposal, and discuss remediation before work gets wasted.
+* Once your feature is complete, all you need to do is [submit a PR](https://github.com/GoVanguard/legion/pulls).
+
+#### Do you have a general question?
+
+* If you have any questions not related to legion's code, features, or bugs use [email protected]
+
+#### Code of Conduct
+
+We like to keep the rules simple.
+
+* Behavior meant to malign, disrespect, denigrate, harass, or attack any person will not be tolerated.
+* Use respectful language and foster a community of collaboration.
+