Fixup modules #4011
Fixup modules #4011
Conversation
Introduced in rapid7#3992
People often like to supress failed attempts. Note that this change may or may not have any effect, given the status of rapid7#3995. This module was introduced in PR rapid7#3947.
|
@todb-r7 Thanks for the tip. The next modules will have better descriptions. :) |
|
Ironically, this PR corrected the English/Grammar in |
|
Better description? I tried to grasp what was going on from the screenshots and glancing at the run() bits but pslisting is about all I could tease out. The original description about "enumerating the environment" was pretty vague, and didn't cover barometric pressure or wetland erosion or anything. On October 17, 2014 6:31:30 PM CDT, Jon Hart notifications@github.com wrote:
Sent from a tiny computer. |
|
LOL @todb-r7
|
A few minor fixes to modules. This kind of PR traditionally used to happen once a week -- I'm trying to up the frequency of these edits to once a day, so that we don't spend several days with imperfect grammar for Framework folks.
/cc @shuckins-r7 @cdoughty-r7 -- if you want something more or less frequent, let me know.
/cc @rapid7/framework-public-committers and @rapid7/framework-rapid7-committers -- please double check your titles and descriptions prior to landing. While you might be super excited to get a shell after troubleshooting and testing, the titles and descriptions are about the most visible parts of modules that most normal people see.
Also, modules often show up on other sites (packetstorm, osvdb, bugtraq) when things are landed, or even when things are being PR'ed; AFAIK, these third-party indexers of our material don't wait for Metasploit Pro releases, and they don't tend to update to fix spelling errors. :)
Pre-emptively assigning to @wvu-r7 since he tends to land these things with aplumb and gusto.