recog 2.1.32 → 2.1.33

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 541810a5f2585b6cafec8c63bb9f0494d8187e08
-  data.tar.gz: aa057ba57c4a5af3bc159598ad22d91313b8a850
+  metadata.gz: 2173eb6ef24d3ea0ff49f561dcbe099ec5b27f27
+  data.tar.gz: 1d52782399bd682f42524a5d40ca48e02f7750a3
 SHA512:
-  metadata.gz: 9ceaad21d56c99e5b079ef18132800b71d6d940f4dccaaa08a66fae48650c27d6988c4032122d8a05acb3aa8ab7e839d142f2b434ea797f0c1309b203f00317c
-  data.tar.gz: ea7e1b16a0b12bc229b8ac3e16dc91b059343c32ebde666dd8956ec3fc95e1136012a94fc01a33006fcf4c8461e9837c45a5aee2b912cd1bf9f3232d7a0ff5b9
+  metadata.gz: ab52b5de2a6d6ab01b56fa64458caab19b52805ab27bad318461ead4ae1062f46603ad5be46ff0792b4ee6911e0f715a646b53bb94268ed3b80758918e11ac60
+  data.tar.gz: 18c29a270f42599cc33e28419b6ffee694e9684838bf7c459d953a8a4cf59ee33a2887cedac9e7c1c5ebaa858a260e1e5732ba125d5077c36a3a0ba06530895a

data/.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,37 @@
+---
+name: Bug report
+about: Create a report to help us improve
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+
+1. Do this...
+2. Do that...
+3. Then something happens...
+
+Code that reproduces the behavior: <!-- This is optional -->
+```ruby
+# paste code here, or create a gist, or link to public code snippet
+```
+
+Matcher that reproduces the behavior: <!-- This is optional -->
+```xml
+<!-- paste matcher xml here, or create a gist, or link to public code snippet -->
+```
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+
+**Environment (please complete the following information):**
+ - Operating System: 
+ - Ruby Version: 
+ - Recog Version: 
+
+**Additional context**
+Add any other context about the problem here.

data/.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,17 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

data/.github/ISSUE_TEMPLATE/fingerprint_request.md

@@ -0,0 +1,27 @@
+---
+name: Fingerprint request
+about: Request new fingerprint coverage
+
+---
+
+**Request for new fingerprint(s) for a product**  
+Briefly describe the product to be fingerprinted, including vendor and version information.  
+<!-- Include links to relevant public documentation from the vendor or other sources, if available -->
+
+**Provide details about the product**  
+What protocol(s) can be used to retrieve identifiable information about the product?  
+<!-- Examples: Telnet, SSH, SNMP, SMTP, HTTP(S), Vendor Proprietary Protocol -->
+
+What information can be collected on each protocol?  
+<!-- Example: HTTP Server banner: nginx/0.8.53 -->
+
+What request, command, and/or payload can be used to retrieve information on each protocol?  
+<!-- Use code fences like the below example to preserve formatting -->
+```
+HTTP HEAD /
+
+HTTP GET /info.php
+```
+
+**Example banner(s) with specific version info**  
+<!-- Paste raw text here, using code fences to preserve formatting if needed-->

data/.github/PULL_REQUEST_TEMPLATE

@@ -0,0 +1,24 @@
+## Description
+A detailed description of your changes.
+
+
+## Motivation and Context
+Explanation of why these changes are being proposed, including any links to other relevant issues or pull requests.
+
+
+## How Has This Been Tested?
+A clear and concise description of your changes were tested.
+
+
+## Types of changes
+<!--- What types of changes does your code introduce? Remove any that do not apply: -->
+- Bug fix (non-breaking change which fixes an issue)
+- New feature (non-breaking change which adds functionality)
+- Breaking change (fix or feature that would cause existing functionality to change)
+
+
+## Checklist:
+<!--- After submitting the PR, check all of the boxes that apply. -->
+- [ ] I have updated the documentation accordingly (or changes are not required).
+- [ ] I have added tests to cover my changes (or new tests are not required).
+- [ ] All new and existing tests passed.

data/.gitignore

@@ -3,6 +3,7 @@ coverage/
 doc/
 pkg/
 .idea/
+.vscode/
 /Gemfile.lock
 
 # ignore rvm files

data/lib/recog/version.rb

@@ -1,3 +1,3 @@
 module Recog
-  VERSION = '2.1.32'
+  VERSION = '2.1.33'
 end

data/xml/telnet_banners.xml

@@ -674,6 +674,7 @@
     <example _encoding="base64">V2VsY29tZSB0byBNaWNyb3NvZnQgVGVsbmV0IFNlcnZpY2UgDQoKDWxvZ2luOgo=</example>
     <param pos="0" name="os.vendor" value="Microsoft"/>
     <param pos="0" name="os.family" value="Windows"/>
+    <param pos="0" name="os.product" value="Windows"/>
   </fingerprint>
   <!-- The following fingerprints are for generic Broadcom hardware where the
        vendor has left the default banner in place. These could be rebadged by

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: recog
 version: !ruby/object:Gem::Version
-  version: 2.1.32
+  version: 2.1.33
 platform: ruby
 authors:
 - Rapid7 Research
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2018-11-04 00:00:00.000000000 Z
+date: 2018-11-16 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rspec
@@ -121,6 +121,10 @@ executables:
 extensions: []
 extra_rdoc_files: []
 files:
+- ".github/ISSUE_TEMPLATE/bug_report.md"
+- ".github/ISSUE_TEMPLATE/feature_request.md"
+- ".github/ISSUE_TEMPLATE/fingerprint_request.md"
+- ".github/PULL_REQUEST_TEMPLATE"
 - ".gitignore"
 - ".rspec"
 - ".travis.yml"