diff --git a/08.md b/08.md index 6829c7d..b3c908c 100644 --- a/08.md +++ b/08.md @@ -12,7 +12,7 @@ ## Setup -![Challenge Setup](docs/07_setup.png) +![Challenge Setup](docs/08_setup.png) ## Notes @@ -20,6 +20,6 @@ ![logic analyzing](docs/08_logic.png) -Created a similar Glitch-o-Bolt config: [08_GoB_config.py](docs/08_GoB_config.py) +Created a similar Glitch-o-Bolt config (not used in the demo below): [08_GoB_config.py](docs/08_GoB_config.py) ![glitching solution](docs/08_GoB.png) \ No newline at end of file diff --git a/08.md b/08.md index 6829c7d..b3c908c 100644 --- a/08.md +++ b/08.md @@ -12,7 +12,7 @@ ## Setup -![Challenge Setup](docs/07_setup.png) +![Challenge Setup](docs/08_setup.png) ## Notes @@ -20,6 +20,6 @@ ![logic analyzing](docs/08_logic.png) -Created a similar Glitch-o-Bolt config: [08_GoB_config.py](docs/08_GoB_config.py) +Created a similar Glitch-o-Bolt config (not used in the demo below): [08_GoB_config.py](docs/08_GoB_config.py) ![glitching solution](docs/08_GoB.png) \ No newline at end of file diff --git a/09.md b/09.md index 23d4962..7bf69f1 100644 --- a/09.md +++ b/09.md @@ -41,11 +41,11 @@ ![logic analyzer setup](docs/09_logic_01.png) -So I didnt have to push the buttons manually (because that would have been a disaster) I wired up the arduino to the buttons and LED and created an arduino sketch to ineract with input and output pins and time when pins go high/low: [arduino code](docs/09_arduino.ino) +So I didnt have to push the buttons manually (because that would have been a disaster) I wired up the arduino to the buttons and LED and created an arduino sketch to ineract with input and output pins and time when pins go high/low: [09_arduino.ino](docs/09_arduino.ino) I also created a python class to talk to the arduino: [arduinIO.py](docs/arduinIO.py) -This was all tied together with of course, a glitch-o-bolt config: [glitch-o-bolt config](docs/09_GoB_config.py) +This was all tied together with of course, a glitch-o-bolt config: [09_GoB_config.py](docs/09_GoB_config.py) With the logic analyzer still hooked up it was possible to see the delay buy usign the timing markers on the start of the button press and the start of the LED turning off: diff --git a/08.md b/08.md index 6829c7d..b3c908c 100644 --- a/08.md +++ b/08.md @@ -12,7 +12,7 @@ ## Setup -![Challenge Setup](docs/07_setup.png) +![Challenge Setup](docs/08_setup.png) ## Notes @@ -20,6 +20,6 @@ ![logic analyzing](docs/08_logic.png) -Created a similar Glitch-o-Bolt config: [08_GoB_config.py](docs/08_GoB_config.py) +Created a similar Glitch-o-Bolt config (not used in the demo below): [08_GoB_config.py](docs/08_GoB_config.py) ![glitching solution](docs/08_GoB.png) \ No newline at end of file diff --git a/09.md b/09.md index 23d4962..7bf69f1 100644 --- a/09.md +++ b/09.md @@ -41,11 +41,11 @@ ![logic analyzer setup](docs/09_logic_01.png) -So I didnt have to push the buttons manually (because that would have been a disaster) I wired up the arduino to the buttons and LED and created an arduino sketch to ineract with input and output pins and time when pins go high/low: [arduino code](docs/09_arduino.ino) +So I didnt have to push the buttons manually (because that would have been a disaster) I wired up the arduino to the buttons and LED and created an arduino sketch to ineract with input and output pins and time when pins go high/low: [09_arduino.ino](docs/09_arduino.ino) I also created a python class to talk to the arduino: [arduinIO.py](docs/arduinIO.py) -This was all tied together with of course, a glitch-o-bolt config: [glitch-o-bolt config](docs/09_GoB_config.py) +This was all tied together with of course, a glitch-o-bolt config: [09_GoB_config.py](docs/09_GoB_config.py) With the logic analyzer still hooked up it was possible to see the delay buy usign the timing markers on the start of the button press and the start of the LED turning off: diff --git a/10.md b/10.md index 4054731..d896d13 100644 --- a/10.md +++ b/10.md @@ -17,7 +17,7 @@ ## Notes -This was very similar to the previous one. Minor tweaks to the glitch-o-bolt config: [glitch-o-bolt config](docs/10_GoB_config.py) +This was very similar to the previous one. Minor tweaks to the glitch-o-bolt config: [10_GoB_config.py](docs/10_GoB_config.py) ![glitching solution](docs/10_GoB.png) \ No newline at end of file diff --git a/08.md b/08.md index 6829c7d..b3c908c 100644 --- a/08.md +++ b/08.md @@ -12,7 +12,7 @@ ## Setup -![Challenge Setup](docs/07_setup.png) +![Challenge Setup](docs/08_setup.png) ## Notes @@ -20,6 +20,6 @@ ![logic analyzing](docs/08_logic.png) -Created a similar Glitch-o-Bolt config: [08_GoB_config.py](docs/08_GoB_config.py) +Created a similar Glitch-o-Bolt config (not used in the demo below): [08_GoB_config.py](docs/08_GoB_config.py) ![glitching solution](docs/08_GoB.png) \ No newline at end of file diff --git a/09.md b/09.md index 23d4962..7bf69f1 100644 --- a/09.md +++ b/09.md @@ -41,11 +41,11 @@ ![logic analyzer setup](docs/09_logic_01.png) -So I didnt have to push the buttons manually (because that would have been a disaster) I wired up the arduino to the buttons and LED and created an arduino sketch to ineract with input and output pins and time when pins go high/low: [arduino code](docs/09_arduino.ino) +So I didnt have to push the buttons manually (because that would have been a disaster) I wired up the arduino to the buttons and LED and created an arduino sketch to ineract with input and output pins and time when pins go high/low: [09_arduino.ino](docs/09_arduino.ino) I also created a python class to talk to the arduino: [arduinIO.py](docs/arduinIO.py) -This was all tied together with of course, a glitch-o-bolt config: [glitch-o-bolt config](docs/09_GoB_config.py) +This was all tied together with of course, a glitch-o-bolt config: [09_GoB_config.py](docs/09_GoB_config.py) With the logic analyzer still hooked up it was possible to see the delay buy usign the timing markers on the start of the button press and the start of the LED turning off: diff --git a/10.md b/10.md index 4054731..d896d13 100644 --- a/10.md +++ b/10.md @@ -17,7 +17,7 @@ ## Notes -This was very similar to the previous one. Minor tweaks to the glitch-o-bolt config: [glitch-o-bolt config](docs/10_GoB_config.py) +This was very similar to the previous one. Minor tweaks to the glitch-o-bolt config: [10_GoB_config.py](docs/10_GoB_config.py) ![glitching solution](docs/10_GoB.png) \ No newline at end of file diff --git a/11.md b/11.md index b4a68fd..e40c279 100644 --- a/11.md +++ b/11.md @@ -84,7 +84,7 @@ `for (int i = 0; i < strlen(password); i++) {` - if could glitch the loop so skips over it entirely and “success” would stay 1 -Of course I wrote a glitch-o-bolt script to brute-force this: [glitch-o-bolt config](docs/11_GoB_config.py) +Of course I wrote a glitch-o-bolt script to brute-force this: [11_GoB_config.py](docs/11_GoB_config.py) The watchdog is there because sometimes it glitched into a state that caused it to stop responding, if it doesnt respond for 2 seconds then the watchdog will restart the device (with a long glitch). diff --git a/08.md b/08.md index 6829c7d..b3c908c 100644 --- a/08.md +++ b/08.md @@ -12,7 +12,7 @@ ## Setup -![Challenge Setup](docs/07_setup.png) +![Challenge Setup](docs/08_setup.png) ## Notes @@ -20,6 +20,6 @@ ![logic analyzing](docs/08_logic.png) -Created a similar Glitch-o-Bolt config: [08_GoB_config.py](docs/08_GoB_config.py) +Created a similar Glitch-o-Bolt config (not used in the demo below): [08_GoB_config.py](docs/08_GoB_config.py) ![glitching solution](docs/08_GoB.png) \ No newline at end of file diff --git a/09.md b/09.md index 23d4962..7bf69f1 100644 --- a/09.md +++ b/09.md @@ -41,11 +41,11 @@ ![logic analyzer setup](docs/09_logic_01.png) -So I didnt have to push the buttons manually (because that would have been a disaster) I wired up the arduino to the buttons and LED and created an arduino sketch to ineract with input and output pins and time when pins go high/low: [arduino code](docs/09_arduino.ino) +So I didnt have to push the buttons manually (because that would have been a disaster) I wired up the arduino to the buttons and LED and created an arduino sketch to ineract with input and output pins and time when pins go high/low: [09_arduino.ino](docs/09_arduino.ino) I also created a python class to talk to the arduino: [arduinIO.py](docs/arduinIO.py) -This was all tied together with of course, a glitch-o-bolt config: [glitch-o-bolt config](docs/09_GoB_config.py) +This was all tied together with of course, a glitch-o-bolt config: [09_GoB_config.py](docs/09_GoB_config.py) With the logic analyzer still hooked up it was possible to see the delay buy usign the timing markers on the start of the button press and the start of the LED turning off: diff --git a/10.md b/10.md index 4054731..d896d13 100644 --- a/10.md +++ b/10.md @@ -17,7 +17,7 @@ ## Notes -This was very similar to the previous one. Minor tweaks to the glitch-o-bolt config: [glitch-o-bolt config](docs/10_GoB_config.py) +This was very similar to the previous one. Minor tweaks to the glitch-o-bolt config: [10_GoB_config.py](docs/10_GoB_config.py) ![glitching solution](docs/10_GoB.png) \ No newline at end of file diff --git a/11.md b/11.md index b4a68fd..e40c279 100644 --- a/11.md +++ b/11.md @@ -84,7 +84,7 @@ `for (int i = 0; i < strlen(password); i++) {` - if could glitch the loop so skips over it entirely and “success” would stay 1 -Of course I wrote a glitch-o-bolt script to brute-force this: [glitch-o-bolt config](docs/11_GoB_config.py) +Of course I wrote a glitch-o-bolt script to brute-force this: [11_GoB_config.py](docs/11_GoB_config.py) The watchdog is there because sometimes it glitched into a state that caused it to stop responding, if it doesnt respond for 2 seconds then the watchdog will restart the device (with a long glitch). diff --git a/docs/08_setup.png b/docs/08_setup.png new file mode 100644 index 0000000..c734ebc --- /dev/null +++ b/docs/08_setup.png Binary files differ