From 8057e0d62f401558c2bb020cf143fbf2089dc069 Mon Sep 17 00:00:00 2001 From: jlee-r7 Date: Thu, 13 Dec 2012 09:08:15 -0800 Subject: [PATCH] Updated Common Metasploit Module Bad Coding Practice (markdown) --- Common-Metasploit-Module-Bad-Coding-Practice.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Common-Metasploit-Module-Bad-Coding-Practice.md b/Common-Metasploit-Module-Bad-Coding-Practice.md index 22e3455490..6e5c103b45 100644 --- a/Common-Metasploit-Module-Bad-Coding-Practice.md +++ b/Common-Metasploit-Module-Bad-Coding-Practice.md @@ -7,7 +7,7 @@ Note: Some of these examples use puts() for demo purposes, but you should always 1. Not checking the return value of a Metasploit API 2. Ruby 1.9.3 vs 1.8.7... gotcha! 3. Not checking the return value when using match() -4. Not checking nil before accessing a function +4. Not checking nil before accessing a method 5. Using exception handling to shut an error up 6. Not taking advantage of the 'ensure' block 7. Adding the 'VERBOSE' option