freqy/protomolecule
3
1
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Compare commits

merge into: freqy:master
Branches Tags
freqy:master
freqy:development
freqy:e-branch
freqy:slave
freqy:tui-viewport
freqy:concurrency
freqy:tui
...
pull from: freqy:e-branch
Branches Tags
freqy:master
freqy:development
freqy:e-branch
freqy:slave
freqy:tui-viewport
freqy:concurrency
freqy:tui

4 Commits
master ... e-branch

Author SHA1 Message Date
e
e7894bbbd5 edited notes 2022-08-19 00:08:25 -04:00
e
3f36dc03c8 Update 'NOTES-e.md' 2022-08-18 02:55:12 +00:00
e
d0f96f9df8 actual notes? 2022-08-17 22:17:59 -04:00
e
ca19ed5310 adding notes 2022-08-17 22:15:49 -04:00
1 changed files with 6 additions and 0 deletions
Show Stats Expand all files Collapse all files

6
NOTES-e.md Normal file
View File

@ -0,0 +1,6 @@
# Notes
**Starting Statements**
1. We require both RFCOMM and L2Ping capabilites. I believe I was able to find a janky L2Ping golang conversion, and I believe that Golang can handle RFCOMM sockets by default. This will be used for Deauth, even if it is "useless" going forward, it is a fun trick just to have in the toolkit. l2ping (ping flood deauth), rfcomm (connect flood deauth)
2.