# Recog-Ruby: A Recognition Framework [![Gem Version](https://badge.fury.io/rb/recog.svg)](http://badge.fury.io/rb/recog) [![CI Workflow](https://github.com/rapid7/recog-ruby/actions/workflows/ci.yml/badge.svg)](https://github.com/rapid7/recog-ruby/actions/workflows/ci.yml) Recog is a framework for identifying products, services, operating systems, and hardware by matching fingerprints against data returned from various network probes. Recog makes it simple to extract useful information from web server banners, SNMP system description fields, and a whole lot more. The Recog-Ruby repository contains the Ruby language implementation of the Recog recognition framework library and the [Recog](https://github.com/rapid7/recog) content, XML fingerprint files, as a git submodule. That makes it easy to develop, test, and use the contained fingerprints. Recog-Ruby is open source, please see the [LICENSE](LICENSE) file for more information. ## Table of Contents 1. [Repository split](#repository-split) 1. [Installation](#installation) 1. [Maturity](#maturity) 1. [Fingerprints](#fingerprints) 1. [Contributing](#contributing) ## Repository split On March 31, 2022, the Recog content - XML fingerprint files and utilities - were split from the Recog framework library implementation. The original [Recog](https://github.com/rapid7/recog) repository now contains the Recog content and the [Recog-Ruby](https://github.com/rapid7/recog-ruby) repository contains the Ruby language implementation. The Recog content is included in Recog-Ruby as a git submodule and is nested under the `recog` directory. All post-split Recog gem versions equal or greater than 3.0.0 will: 1. contain the XML fingerprint directory under the `recog` directory, and 2. only include the `recog_match` tool since the other tools are focused on fingerprint management. [^back to top](#recog-ruby-a-recognition-framework) ## Installation In order to use the included Ruby code, a recent version of Ruby (2.31+) is required, along with Rubygems and the `bundler` gem. Once these dependencies are in place, use the following commands to grab the latest source code and install any additional dependencies. ```shell $ git clone --recurse-submodules git@github.com:rapid7/recog-ruby.git $ cd recog-ruby $ bundle install ``` [^back to top](#recog-ruby-a-recognition-framework) ## Maturity Please note that while the XML fingerprints themselves are quite stable and well-tested, the Ruby codebase is still fairly new and subject to change quickly. Please contact us (research[at]rapid7.com) before leveraging the Recog code within any production projects. [^back to top](#recog-ruby-a-recognition-framework) ## Fingerprints The fingerprints within [Recog](https://github.com/rapid7/recog) are stored in XML files, each of which is designed to match a specific protocol response string or field. For example, the file [ssh_banners.xml](https://github.com/rapid7/recog/blob/master/xml/ssh_banners.xml) can determine the os, vendor, and sometimes hardware product by matching the initial SSH daemon banner string. A fingerprint file consists of an XML document like the following: ```xml Allegro RomSShell SSH RomSShell_4.62 ``` The first line should always consist of the XML version declaration. The first element should always be a `fingerprints` block with a `matches` attribute indicating what data this fingerprint file is supposed to match. The `matches` attribute is normally in the form of `protocol.field`. Inside of the `fingerprints` element there should be one or more `fingerprint` elements. Every `fingerprint` must contain a `pattern` attribute, which contains the regular expression to be used to match against the data. An optional `flags` attribute can be specified to control how the regular expression is to be interpreted. See [the Recog documentation for `FLAG_MAP`](http://www.rubydoc.info/gems/recog/Recog/Fingerprint/RegexpFactory#FLAG_MAP-constant) for more information. Inside of the fingerprint, a `description` element should contain a human-readable string describing this fingerprint. At least one `example` element should be present, however multiple `example` elements are preferred. These elements are used as part of the test coverage present in `rspec` which validates that the provided data matches the specified regular expression. Additionally, if the fingerprint is using the `param` elements to extract field values from the data (described next), you can add these expected extractions as attributes for the `example` elements. In the example above, this: ```xml RomSShell_4.62 ``` tests that `RomSShell_4.62` matches the provided regular expression and that the value of `service.version` is 4.62. The `param` elements contain a `pos` attribute, which indicates what capture field from the `pattern` should be extracted, or `0` for a static string. The `name` attribute is the key that will be reported in the case of a successful match and the `value` will either be a static string for `pos` values of `0` or missing and taken from the captured field. The `example` string can be base64 encoded to permit the use of unprintable characters. To signal this to Recog an `_encoding` attribute with the value of `base64` is added to the `example` element. Based64 encoded text that is longer than 80 characters may be wrapped with newlines as shown below to aid in readability. ```xml dGllczGEAAAAlQQWMS4yLjg0MC4xMTM1NTYuMS40LjgwMAQuZGF0YS5yZW1vdmVkLjCEAAAAK AQdZG9tYWluQ29udHJvbGxlckZ1bmN0aW9uYWxpdHkxhAAAAAMEATc= ``` Additionally, examples can be placed in a directory with the same base name as the XML file, in the same directory as the XML file: ``` xml/services.xml xml/services/file1 xml/services/file2 ... ``` They can then be loaded using the `_filename` attribute: ```xml ``` This is useful for long examples. [^back to top](#recog-ruby-a-recognition-framework) ## Contributing The users and maintainers of Recog-Ruby would greatly appreciate any contributions you can make to the project. For guidelines and instructions please see [CONTRIBUTING.MD](CONTRIBUTING.md) [^back to top](#recog-ruby-a-recognition-framework)