Remove some challenges, update hints

Author: skmagiik

docs/hints/flag1.md

@@ -6,7 +6,7 @@ First, check out your score:
 ```` gatttool -b de:ad:be:ef:be:f1 --char-read -a 0x002a|awk -F':' '{print $2}'|tr -d ' '|xxd -r -p;printf '\n' ````
 
 Next, lets sumbmit the following flag.
-```` gatttool -b de:ad:be:ef:be:f1 --char-write-req -a 0x002c -n $(echo -n "12345678901234567890"|xxd -ps) ````
+```` gatttool -b de:ad:be:ef:be:f1 --char-write-req -a 0x002c -n $(echo -n "BLE{G3TT1NG_ST4RT3D}"|xxd -ps) ````
 
 Finaly, check out your score again to see your flag got accepted:   
 ```` gatttool -b de:ad:be:ef:be:f1 --char-read -a 0x002a|awk -F':' '{print $2}'|tr -d ' '|xxd -r -p;printf '\n' ````

docs/hints/flag10.md

@@ -1,3 +1,3 @@
 ## Flag 10 Hint
 
-Talke a look at handle 0x003e and do what it says.  Keep in mind that some tools have better connection speeds than other for doing reads and writes.  This has to do with the functionality the tool provides or how it uses cached BT connections on the host OS.  Try testing different tools for this flag.  Once you find the fastest one, whip up a script or bash 1 liner to complete the task.  FYI, once running, this task takes roughly 90 seconds to complete if done right. 
+Check out handle 0x0040 and google search gatt notify.  Some tools like gatttool have the ability to subscribe to gatt notifications

docs/hints/flag11.md

@@ -1,3 +1,3 @@
 ## Flag 11 Hint
 
-Check out handle 0x0040 and google search gatt notify.  Some tools like gatttool have the ability to subscribe to gatt notifications
+Check out handle 0x0042 and google search gatt indicate.  For single response indicate messages, like this challenge, tools such as gatttool will work just fine.   

docs/hints/flag12.md

@@ -1,3 +1,3 @@
 ## Flag 12 Hint
 
-Check out handle 0x0042 and google search gatt indicate.  For single response indicate messages, like this challenge, tools such as gatttool will work just fine.   
+Check out handle 0x0046 and do what it says. Keep in mind that this notification clallange requires you to recieve multiple responses in order to complete. 

docs/hints/flag13.md

@@ -1,3 +1,3 @@
 ## Flag 13 Hint
 
-Check out handle 0x0046 and do what it says. Keep in mind that this notification clallange requires you to recieve multiple responses in order to complete. 
+Check out handle 0x0048 and google search gatt indicate.  Keep in mind that this challenge will require you to parse multiple indicate responses in order to complete the challenge.

docs/hints/flag14.md

@@ -1,3 +1,3 @@
 ## Flag 14 Hint
 
-Check out handle 0x0048 and google search gatt indicate.  Keep in mind that this challenge will require you to parse multiple indicate responses in order to complete the challenge.
+Check out handle 0x004c and do what it says.  Much like ethernet or wifi devices, you can also change your bluetooth devices mac address.

docs/hints/flag15.md

@@ -1,3 +1,3 @@
 ## Flag 15 Hint
 
-Check out handle 0x004c and do what it says.  Much like ethernet or wifi devices, you can also change your bluetooth devices mac address.
+Read handle 0x004e and do what it says.  Setting MTU can be a tricky thing.  Some tools may provide mtu flags, but they dont seem to really trigger MTU negotiations on servers.  Try using gatttool's interactive mode for this task.  By default, the BLECTF server is set to force an MTU size of 20.  The server will listen for MTU negotiations, and look at them, but we dont really change the MTU in the code.  We just trigger the flag code if you trigger an MTU event with the value specified in handle 0x004e.  GLHF!

docs/hints/flag16.md

@@ -1,3 +1,3 @@
 ## Flag 16 Hint
 
-Read handle 0x004e and do what it says.  Setting MTU can be a tricky thing.  Some tools may provide mtu flags, but they dont seem to really trigger MTU negotiations on servers.  Try using gatttool's interactive mode for this task.  By default, the BLECTF server is set to force an MTU size of 20.  The server will listen for MTU negotiations, and look at them, but we dont really change the MTU in the code.  We just trigger the flag code if you trigger an MTU event with the value specified in handle 0x004e.  GLHF!
+Take a look at handle 0x0052.  Notice it does not have a notify property.  Do a write here and listen for notifications anyways!  Things are not always what they seem!

docs/hints/flag17.md

@@ -1,3 +1,3 @@
 ## Flag 17 Hint
 
-Check out handle 0x0050 and do what it says.  This challenge differs from other write challenges as your tool that does the write needs to have write response ack messages implemented correctly.  This flag is also tricky as the flag will come back as notification response data even though there is no "NOTIFY" property.
+Check out all of the handle properties on 0x0054!  Poke around with all of them and find pieces to your flag.