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

edited notes

Browse Source
This commit is contained in:
e 2022-08-19 00:08:25 -04:00
parent 3f36dc03c8
commit e7894bbbd5
1 changed files with 3 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
NOTES-e.md
View File

@ -1,10 +1,6 @@
# Notes
### by e
After re-reading a lot of this, I will need to re-write my notes as a lot of the shit I wrote was wrong as hell.
**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.
Two big takeaways that I still think we need 100% is rfcomm and l2ping capabilities. rfcomm may be able to be done through sockets in Golang by default now??? idk, will have to look into this. after looking at l2ping.c, it should be easyish in go, but I am no coder.
I do believe this may be the biggest vector of attack on nRF devices though - obviously.
The more I read into this, the more I will update this, as well as clean it up. ADHD brain took over a bit