First Commit

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,47 @@
+# Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, OS choice, favourite programming language (especially if it's JavaScript), nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* Calling this project a "Jammer"
+* The use of sexualized language or imagery and unwelcome sexual attention or advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting such as promoting chicken foodism
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at mail@spacehuhn.com. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

.github/CONTRIBUTING.md

@@ -0,0 +1,95 @@
+# Request for contributions
+
+Please contribute to this repository if any of the following is true:
+- You have expertise in Arduino/ESP8266 development, WiFi, or C/C++
+- You want to help lower the burden to first time contributors
+- You want this open source community to be more collaborative and inclusive
+
+# How to contribute
+
+Prerequisites:
+
+- Familiarity with [pull requests](https://help.github.com/articles/using-pull-requests) and [issues](https://guides.github.com/features/issues/).
+- Knowledge of [Markdown](https://help.github.com/articles/markdown-basics/) for editing `.md` documents.
+- Knowledge of [WiFi Deauth](https://en.wikipedia.org/wiki/Wi-Fi_deauthentication_attack) for understanding the project.
+
+In particular, this community seeks the following types of contributions:
+
+- **Ideas**: participate in an issue thread or start your own to have your voice
+heard.
+- **Resources**: submit a pull request to add to RESOURCES.md with links to related content.
+- **Outline sections**: help us ensure that this repository is comprehensive. if
+there is a topic that is overlooked, please add it, even if it is just a stub
+in the form of a header and single sentence. Initially, most things fall into
+this category.
+- **Writing**: contribute your expertise in an area by helping us expand the included
+content.
+- **Copy editing**: fix typos, clarify language, and generally improve the quality
+of the content.
+- **Formatting**: help keep content easy to read with consistent formatting.
+
+<a name="bugs"></a>
+## Bug reports
+
+A bug is a _demonstrable problem_ that is caused by the code in the repository.
+Good bug reports are extremely helpful - thank you!
+
+Guidelines for bug reports:
+
+1. **Use the GitHub issue search** &mdash; check if the issue has already been
+   reported.
+
+2. **Check if the issue has been fixed** &mdash; try to reproduce it using the
+   latest `master` or development branch in the repository.
+
+3. **Isolate the problem**.
+
+A good bug report shouldn't leave others needing to chase you up for more
+information. Please try to be as detailed as possible in your report. What is
+your environment? What steps will reproduce the issue? What browser(s) and OS
+experience the problem? What would you expect to be the outcome? All these
+details will help people to fix any potential bugs.
+
+Example:
+
+> Short and descriptive example bug report title
+>
+> A summary of the issue and the browser/OS environment in which it occurs. If
+> suitable, include the steps required to reproduce the bug.
+>
+> 1. This is the first step
+> 2. This is the second step
+> 3. Further steps, etc.
+>
+> `<url>` - a link to the serial output on pastebin
+> `<pic>` - a photo of your build with apparent wiring
+>
+> Any other information you want to share that is relevant to the issue being
+> reported. This might include the lines of code that you have identified as
+> causing the bug, and potential solutions (and your opinions on their
+> merits).
+
+
+<a name="features"></a>
+## Feature requests
+
+Feature requests are welcome. But take a moment to find out whether your idea
+fits with the scope and aims of the project. It's up to *you* to make a strong
+case to convince the project's developers of the merits of this feature. Please
+provide as much detail and context as possible.
+
+
+<a name="pull-requests"></a>
+## Pull requests
+
+Good pull requests - patches, improvements, new features - are a fantastic
+help. They should remain focused in scope and avoid containing unrelated
+commits.
+
+**Please ask first** before embarking on any significant pull request (e.g.
+implementing features, refactoring code, porting to a different language),
+otherwise you risk spending a lot of time working on something that the
+project's developers might not want to merge into the project.
+
+Please adhere to the coding conventions used throughout a project (indentation,
+accurate comments, etc.) and any other requirements (such as test coverage).

.github/FUNDING.yml

@@ -0,0 +1,12 @@
+# These are supported funding model platforms
+
+github: spacehuhntech
+patreon: # Replace with a single Patreon username
+open_collective: # Replace with a single Open Collective username
+ko_fi: spacehuhn
+tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
+community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry
+liberapay: # Replace with a single Liberapay username
+issuehunt: # Replace with a single IssueHunt username
+otechie: # Replace with a single Otechie username
+custom: # Replace with up to 4 custom sponsorship URLs e.g., ['link1', 'link2']

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,6 @@
+> Please search for existing (open and closed) issues first to avoid duplicates.  
+Also have a look at the [Wiki](https://github.com/spacehuhntech/esp8266_deauther/wiki).  
+
+```
+PASTE YOUR ERROR/COMPILE LOGS HERE
+```

.github/ISSUE_TEMPLATE/1--error-report.md

@@ -0,0 +1,45 @@
+---
+name: 1. Problem or error report
+about: I encountered a problem and need help to solve it
+title: ""
+labels: help wanted
+assignees: ''
+---
+
+> Have you searched for existing (open and closed) issues describing the same problem?
+
+Yes/No
+
+**Describe the error**
+A clear and concise description of what the problem is.
+What do you think causes it?
+
+```
+Error/Compile/Output Log
+```
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Environment (please complete the following information):**
+ - OS: [e.g. iOS]
+ - Browser [e.g. chrome, safari]
+ - Version [e.g. 1.0]
+ - Hardware [e.g. DSTIKE, DIY]
+
+**Attempts**
+What have you already tried and didn't work out.
+
+**Additional context**
+Provide as much information as possible, better too much than too little!
+If you don't use this template, your issue might be closed and tagged invalid!

.github/ISSUE_TEMPLATE/2--question.md

@@ -0,0 +1,11 @@
+---
+name: 2. Question
+about: I have a question about this project
+title: ""
+labels: question
+assignees: ''
+
+---
+
+> Please search for existing (open and closed) issues first to avoid duplicates.  
+Also have a look at the [Wiki](https://github.com/spacehuhntech/esp8266_deauther/wiki).  

.github/ISSUE_TEMPLATE/3--feature-request.md

@@ -0,0 +1,24 @@
+---
+name: 3. Feature request
+about: I have an idea to improve this project
+title: ""
+labels: feature request
+assignees: ''
+
+---
+
+**Do similar feature requests issues already exist (open and closed)?**
+If yes, please link them here:
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.
+If you don't use this template, your issue might be closed and tagged invalid!

.github/ISSUE_TEMPLATE/4--bug-report.md

@@ -0,0 +1,34 @@
+---
+name: 4. Bug report
+about: I found a reproducible bug in the code
+title: ""
+labels: bug
+assignees: ''
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Environment (please complete the following information):**
+ - OS: [e.g. iOS]
+ - Browser [e.g. chrome, safari]
+ - Version [e.g. 1.0]
+ - Hardware [e.g. DSTIKE, DIY]
+
+**Additional context**
+Add any other context about the problem here.
+If you don't use this template, your issue might be closed and tagged invalid!

.github/ISSUE_TEMPLATE/5--documentation.md

@@ -0,0 +1,18 @@
+---
+name: 5. Documentation
+about: I have something to improve or add to the docs
+title: ''
+labels: documentation
+assignees: ''
+
+---
+
+**Describe your changes**
+A clear and concise description of what you like to add or change.
+
+**Location**
+Where should these changes be made or the information published?
+Wiki, README, ...
+
+**Additional context**
+Add any other context about your proposal.

.github/config.yml

@@ -0,0 +1,15 @@
+# Configuration for welcome - https://github.com/behaviorbot/welcome
+newIssueWelcomeComment: >
+  Congrats on opening your first issue on this repository! 🎉<br>
+  This is a automated message to help you avoid common pitfalls when asking for help online.<br>
+  👉 Be sure to:<br>
+  * 🇬🇧 Communicate in English so everybody can understand you<br>
+  * 📖 Have a look at the [Wiki](https://github.com/spacehuhntech/esp8266_deauther/wiki) and [README](https://github.com/SpacehuhnTech/esp8266_deauther/blob/v2/README.md) for information<br>
+  * 🔍 Search for similar [issues (open and closed)](https://github.com/SpacehuhnTech/esp8266_deauther/issues?q=is%3Aissue+)<br>
+  * ✍️ Provide enough information to understand, recreate and help out with your problem<br>
+  * ℹ️ Let us know if you find a solution and please share it with us<br>
+  * 📕 Close the issue when your problem has been solved
+
+newPRWelcomeComment: 
+
+firstPRMergeComment: 

.github/stale.yml

@@ -0,0 +1,19 @@
+# Number of days of inactivity before an issue becomes stale
+daysUntilStale: 180
+# Number of days of inactivity before a stale issue is closed
+daysUntilClose: 7
+# Issues with these labels will never be considered stale
+exemptLabels:
+  - pinned
+  - bug
+  - translation
+  - feature request
+# Label to use when marking an issue as stale
+staleLabel: stale
+# Comment to post when marking an issue as stale. Set to `false` to disable
+markComment: >
+  This issue has been automatically marked as stale because it has not had
+  recent activity. It will be closed if no further activity occurs. Thank you
+  for your contributions.
+# Comment to post when closing a stale issue. Set to `false` to disable
+closeComment: false

.github/workflows/nightly.yml

@@ -0,0 +1,21 @@
+name: Trigger nightly build
+
+on:
+  push:
+
+jobs:
+
+  notify-nightly:
+    name: "Trigger new build on nightly-deauther"
+    runs-on: ubuntu-latest
+    steps:
+      - name: Build message title
+        id: notif
+        run: echo ::set-output name=TITLE::Deauther V2 $(echo ${{ github.sha }} | cut -c -7)
+
+      - name: Send message
+        run: |
+          curl -X POST https://api.github.com/repos/spacehuhntech/nightly-deauther/dispatches \
+          -H 'Accept: application/vnd.github.everest-preview+json' \
+          -u ${{ secrets.ACCESS_TOKEN }} \
+          --data '{"event_type": "${{ steps.notif.outputs.TITLE }}", "client_payload": {}}'

.gitignore

@@ -0,0 +1,12 @@
+
+*.bin
+
+*.elf
+
+*.map
+
+.DS_Store
+
+*.pyc
+
+utils/web_converter/css_html_js_minify/__pycache__/

LICENSE

@@ -0,0 +1,23 @@
+Do not redistribute, advertise or sell this software as a "jammer"!!!
+
+MIT License
+
+Copyright (c) 2020 Spacehuhn Technologies
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.