Fixing lists

Author: DeveloppSoft

_posts/2015-05-10-Too-busy-right-now.md

@@ -30,18 +30,23 @@ I'm taking many courses to finish my lower-level graduation.
 3 of these require to build a project.
 for June I have to:
 
-  - build a website
-  - build a complex system for a big company
-  - build a game in Java
+<ul class="collection">
+  <li class="collection-item">build a website</li>
+  <li class="collection-item">build a complex system for a big company</li>
+  <li class="collection-item">build a game in Java</li>
+</ul>
 
 beside these jobs I have the exams for other courses for July.
 
-  - Physics
-  - Technical Physics
-  - Mechanics
-  - Logic Circuits
-  - Database 1
-  - Geometry
+
+<ul class="collection">
+  <li class="collection-item">Physics</li>
+  <li class="collection-item">Technical Physics</li>
+  <li class="collection-item">Mechanics</li>
+  <li class="collection-item">Logic Circuits</li>
+  <li class="collection-item">Database 1</li>
+  <li class="collection-item">Geometry</li>
+</ul>
 
 ##### My fails
 

_posts/2015-11-24-preparing-csploit-2.md

@@ -20,15 +20,18 @@ can exploit the whole power of the MSF.
 
 here some new feature that I hope you like:
 
-  - - full module infos ( authors, references, description ... )
-  - - improved module options management
-  - - jobs ( long-running exploits as browser related ones )
-  - - upgrade a shell session to meterpreter
-  - - execute post modules on sessions
-  - - you can now have your msfconsole :heart:
-  - - command history for consoles and sessions
-  - - session/console output will still here until you close cSploit
-  - - event-based system ( notifications/feedback when something changes)
+
+<ul class="collection">
+  <li class="collection-item">full module infos ( authors, references, description ... )</li>
+  <li class="collection-item">improved module options management</li>
+  <li class="collection-item">jobs ( long-running exploits as browser related ones )</li>
+  <li class="collection-item">upgrade a shell session to meterpreter</li>
+  <li class="collection-item">execute post modules on sessions</li>
+  <li class="collection-item">you can now have your msfconsole :heart:</li>
+  <li class="collection-item">command history for consoles and sessions</li>
+  <li class="collection-item">session/console output will still here until you close cSploit</li>
+  <li class="collection-item">event-based system ( notifications/feedback when something changes)</li>
+</ul>
 
 ##### The new UI
 

_posts/2016-01-14-working-on-ssl.md

@@ -9,8 +9,10 @@ Rigth now I'm working on putting some extra feature into cSploit to intercept se
 
 I'm working on 2 features:
 
-  - DNS aliasing to bypass HSTS
-  - inject cSploit CA certificate
+<ul class="collection">
+  <li class="collection-item">DNS aliasing to bypass HSTS</li>
+  <li class="collection-item">inject cSploit CA certificate</li>
+</ul>
 
 I think that the cleaner approach is the root CA certificate injection,
 as it will allow us to sniff even those connection that are started over SSL.
@@ -29,4 +31,4 @@ If the unsecured resource contains any secured link we can strip them out.
 I will work more on this features today, the deadline for the work should be tomorrow around 3 PM UTC.
 
 This is a gift that I'm making to this my friend, however the work will be used to improve cSploit,
-I hope that you will enjoy and apreciate my work.
+I hope that you will enjoy and apreciate my work.

_posts/2016-12-02-csploit_2-updates.md

@@ -19,18 +19,22 @@ Currently we are focusing on the daemon, but we planned to start developing the
 ##### How will it work?
 We will use a web based UI (provide more portability accross the different platforms) that will communicate with the daemon thanks to a REST api.
 
-##### What we did
--	A nice database
--	Ability to manages hosts, services and even scanned networks!
--	WiFi cracking (no, it is not a joke :smirk:!)
--	The network radar
+##### What we did...
+<ul class="collection">
+  <li class="collection-item">A nice database</li>
+  <li class="collection-item">Ability to manage hosts, ports, services and even scanned networks!</li>
+  <li class="collection-item">Wifi cracking (no, it's not a joke :smirk:)</li>
+  <li class="collection-item">Network radar</li>
+</ul>
 
 ##### What's planed?
-- I will continue to work on the WiFi attacks by implementing Wps and rogue APs (thanks to the [mana](https://github.com/sensepost/mana)) attacks.
-- Napitek is working on the evilproxy project (manipulate victims traffic after an MITM attack).
-- IwraStudios is working on dns2proxy project (will let us intercept https).
-- Tux-mind is working really hard on the daemon (can't quote evrything :smile:!).
-- If I forgot someone, I am sorry!
+<ul class="collection">
+  <li class="collection-item">I will work on implementing rogue APs (thanks to the [mana](https://github.com/sensepost/mana) project) and Wps attacks</li>
+  <li class="collection-item">Tux-mind is working very hard on the daemon (can't quote everything :smile:!).
+  <li class="collection-item">Napitek is working on evilproxy</li>
+  <li class="collection-item">IwraStudios is working on dns2proxy</li>
+ </li>
+</ul>
 
 ##### The end
 Well... I guess it is the end, thanks guys!

docs.md

@@ -16,9 +16,11 @@ My apologies for that, I'm doing my best to achieve a stable app :v:.
 
 A short error message isn't often self-explanatory. Sometimes it too difficult to explain an issue with a short message and here you can find a few common examples that explain some errors:
 
-  - - cannot start process: this message is printed when the core of cSploit cannot start the required process.
-  - - **cmd** returned **#number**: this message is printed when **cmd** has exited with an error code **number**
-  - - **cmd** killed by signal **number**: this message is printed when **cmd** has been killed by signal **number**
+<ul class="collection">
+  <li class="collection-item">cannot start process: this message is printed when the core of cSploit cannot start the required process</li>
+  <li class="collection-item">**cmd** returned **#number**: this message is printed when **cmd** has exited with an error code **number**</li>
+  <li class="collection-item">**cmd** killed by signal **number**: this message is printed when **cmd** has been killed by signal **number**</li>
+</ul>
 
 The errors above are bugs that are specific for your device. Hence, please report them if no one already did.
 

story.md

@@ -4,9 +4,11 @@ position: 4
 ---
 After being initially created by evilsocket, I ( tux-mind ) started working on dSploit in summer 2012, i forked it and added the following features:
 
-  - - Vulnerability finder
-  - - Exploit finder
-  - - MetaSploitFramework integration ( draft )
+<ul class="collection">
+  <li class="collection-item">Vulnerability finder</li>
+  <li class="collection-item">Exploit finder</li>
+  <li class="collection-item">MetaSploitFramework integration ( draft )</li>
+</ul>
 
 After some weeks the project owner ( evilsocket ) asked me to merge it to the upstream branch.
 Initially there were about 2 main developers (me and evilsocket) and an UI developer ( androguide ).