https://github.com/jonzeolla/lab-wifisecurity
A lab illustrating how some basic wifi hacking tools work.
https://github.com/jonzeolla/lab-wifisecurity
information-security infosec lab security wifi-security
Last synced: about 1 year ago
JSON representation
A lab illustrating how some basic wifi hacking tools work.
- Host: GitHub
- URL: https://github.com/jonzeolla/lab-wifisecurity
- Owner: JonZeolla
- License: gpl-3.0
- Created: 2016-12-27T00:19:10.000Z (over 9 years ago)
- Default Branch: master
- Last Pushed: 2016-12-27T00:39:15.000Z (over 9 years ago)
- Last Synced: 2025-04-01T18:10:25.452Z (over 1 year ago)
- Topics: information-security, infosec, lab, security, wifi-security
- Language: Shell
- Homepage:
- Size: 16.6 KB
- Stars: 5
- Watchers: 3
- Forks: 3
- Open Issues: 2
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Wifi Security Lab
## How to clone this branch
* `git clone https://github.com/JonZeolla/lab-wifisecurity`
* Clone the latest revision of the lab-wifisecurity repo.
* `git clone -b 2015-07-07_PCS_WLANSecurity https://github.com/jonzeolla/lab-wifisecurity`
* Clone the revision of the wifi security repo used during the 2015-07-07 lab at Pittsburgh Code & Supply. Cloning any of the pointers (tags) will put you in a detached HEAD state, which is expected.
## Contributing
1. [Fork the repository](https://github.com/jonzeolla/lab-wifisecurity/fork)
1. Create a feature branch via `git checkout -b feature/description`
1. Make your changes
1. Commit your changes via `git commit -am 'Summarize the changes here'`
1. Create a new pull request ([how-to](https://help.github.com/articles/creating-a-pull-request/))
## Related Events
### 2015-07-07 Pittsburgh Code & Supply
#### Breaking Wireless: The Dos and Donts of Wi-Fi
[Event Posting](http://www.meetup.com/Pittsburgh-Code-Supply/events/222346335/)
## Migration
On 2016-12-26, this repo was migrated from the WLANSecurity branch of https://github.com/JonZeolla/Lab to its own standalone repository. This was in order to make contributions and third party use easier, as I received feedback that the branching strategy used before was confusing to some.