recog 2.3.22 → 3.0.2

data/features/data/tests_with_failures.xml

@@ -1,20 +0,0 @@
-<?xml version="1.0"?>
-<fingerprints>
-   <fingerprint pattern="^foo$">
-     <description>foo test</description>
-     <!-- Fail: doesn't match -->
-     <example>bar</example>
-   </fingerprint>
-   <fingerprint pattern="^This matches$">
-     <!-- Warn: no name -->
-     <!-- Fail: doesn't match -->
-     <example>This almost matches</example>
-   </fingerprint>
-   <fingerprint pattern="^(\S+) ([\d.]+)$">
-     <description>bar test</description>
-     <!-- Fail: expected os.version doesn't match the capture group -->
-     <example os.version="5.0" >bar 1.0</example>
-     <param pos="2" name="os.version" />
-     <param pos="1" name="os.name" value="Bar" />
-   </fingerprint>
-</fingerprints>

data/features/data/tests_with_warnings.xml

@@ -1,17 +0,0 @@
-<?xml version="1.0"?>
-<fingerprints>
-  <fingerprint pattern="^-{10} Welcome to Pure-FTPd (.*)-{10}$">
-    <example pureftpd.config="">---------- Welcome to Pure-FTPd ----------</example>
-    <description>Pure-FTPd</description>
-    <param pos="1" name="pureftpd.config"/>
-    <param pos="0" name="service.family" value="Pure-FTPd"/>
-    <param pos="0" name="service.product" value="Pure-FTPd"/>
-  </fingerprint>
-  <fingerprint pattern="^-{10} Welcome to Pure-FTPd (.*)-{10}$">
-    <!-- should warn with no examples -->
-    <description>Pure-FTPd</description>
-    <param pos="1" name="pureftpd.config"/>
-    <param pos="0" name="service.family" value="Pure-FTPd"/>
-    <param pos="0" name="service.product" value="Pure-FTPd"/>
-  </fingerprint>
-</fingerprints>

data/features/match.feature

@@ -1,36 +0,0 @@
-Feature: Match
-  @no-clobber
-  Scenario: Finds matches
-    When I run `recog_match matching_banners_fingerprints.xml sample_banner.txt`
-    Then it should pass with:
-      """
-      MATCH: {"matched"=>"Pure-FTPd Config data can be zero or more of: [privsep] [TLS]", "pureftpd.config"=>"[privsep] [TLS] ", "service.family"=>"Pure-FTPd", "service.product"=>"Pure-FTPd", "service.protocol"=>"ftp", "fingerprint_db"=>"matching_banners_fingerprints", "data"=>"---------- Welcome to Pure-FTPd [privsep] [TLS] ----------"}
-      MATCH: {"matched"=>"SunOS/Solaris", "os.vendor"=>"Sun", "os.family"=>"Solaris", "os.product"=>"Solaris", "os.device"=>"General", "host.name"=>"polaris", "os.version"=>"5.8", "service.protocol"=>"ftp", "fingerprint_db"=>"matching_banners_fingerprints", "data"=>"polaris FTP server (SunOS 5.8) ready."}
-      """
-
-  @no-clobber
-  Scenario: Fails at finding matches
-    When I run `recog_match failing_banners_fingerprints.xml sample_banner.txt`
-    Then it should pass with:
-      """
-      FAIL: ---------- Welcome to Pure-FTPd [privsep] [TLS] ----------
-      FAIL: polaris FTP server (SunOS 5.8) ready
-      """
-
-  @no-clobber
-  Scenario: Finds multiple matches
-    When I run `recog_match multiple_banners_fingerprints.xml sample_banner.txt --multi-match`
-    Then it should pass with:
-      """
-      MATCHES: {"matched"=>"Generic FTP, Checks for the existence of the word FTP in the line", "service.protocol"=>"", "fingerprint_db"=>"multiple_banners_fingerprints", "data"=>"---------- Welcome to Pure-FTPd [privsep] [TLS] ----------"},{"matched"=>"Pure-FTPd Config data can be zero or more of: [privsep] [TLS]", "pureftpd.config"=>"[privsep] [TLS] ", "service.family"=>"Pure-FTPd", "service.product"=>"Pure-FTPd", "service.protocol"=>"ftp", "fingerprint_db"=>"multiple_banners_fingerprints", "data"=>"---------- Welcome to Pure-FTPd [privsep] [TLS] ----------"}
-      MATCHES: {"matched"=>"Generic FTP, Checks for the existence of the word FTP in the line", "service.protocol"=>"", "fingerprint_db"=>"multiple_banners_fingerprints", "data"=>"polaris FTP server (SunOS 5.8) ready."},{"matched"=>"SunOS/Solaris", "service.protocol"=>"ftp", "os.vendor"=>"Sun", "os.family"=>"Solaris", "os.product"=>"Solaris", "os.device"=>"General", "host.name"=>"polaris", "os.version"=>"5.8", "fingerprint_db"=>"multiple_banners_fingerprints", "data"=>"polaris FTP server (SunOS 5.8) ready."}
-      """
-
-  @no-clobber
-  Scenario: Finds first matches using no-multi-match flag
-    When I run `recog_match multiple_banners_fingerprints.xml sample_banner.txt --no-multi-match`
-    Then it should pass with:
-    """
-    MATCH: {"matched"=>"Generic FTP, Checks for the existence of the word FTP in the line", "service.protocol"=>"", "fingerprint_db"=>"multiple_banners_fingerprints", "data"=>"---------- Welcome to Pure-FTPd [privsep] [TLS] ----------"}
-    MATCH: {"matched"=>"Generic FTP, Checks for the existence of the word FTP in the line", "service.protocol"=>"", "fingerprint_db"=>"multiple_banners_fingerprints", "data"=>"polaris FTP server (SunOS 5.8) ready."}
-    """

data/features/support/aruba.rb

@@ -1,3 +0,0 @@
-Aruba.configure do |config|
-  config.working_directory = 'features/data'
-end

data/features/support/env.rb

@@ -1,6 +0,0 @@
-require 'aruba/cucumber'
-
-Before do
-  @dirs = ["features/data"]
-  @aruba_timeout_seconds = 30
-end

data/features/verify.feature

@@ -1,48 +0,0 @@
-Feature: Verify
-  @no-clobber
-  Scenario: No tests
-    When I run `recog_verify no_tests.xml`
-    Then it should pass with exactly:
-      """
-      no_tests.xml: SUMMARY: Test completed with 0 successful, 0 warnings, and 0 failures
-      """
-
-  @no-clobber
-  Scenario: Successful tests
-    When I run `recog_verify successful_tests.xml`
-    Then it should pass with exactly:
-      """
-      successful_tests.xml: SUMMARY: Test completed with 4 successful, 0 warnings, and 0 failures
-      """
-
-  @no-clobber
-  Scenario: Tests with warnings, warnings enabled
-    When I run `recog_verify tests_with_warnings.xml`
-    Then it should fail with:
-      """
-      tests_with_warnings.xml: WARN: 'Pure-FTPd' has no test cases
-      tests_with_warnings.xml: WARN: 'Pure-FTPd' is missing an example that checks for parameter 'pureftpd.config' which is derived from a capture group
-      tests_with_warnings.xml: SUMMARY: Test completed with 1 successful, 2 warnings, and 0 failures
-      """
-    And the exit status should be 2
-
-  @no-clobber
-  Scenario: Tests with warnings, warnings disabled
-    When I run `recog_verify --no-warnings tests_with_warnings.xml`
-    Then it should pass with exactly:
-      """
-      tests_with_warnings.xml: SUMMARY: Test completed with 1 successful, 0 warnings, and 0 failures
-      """
-
-  @no-clobber
-  Scenario: Tests with failures
-    When I run `recog_verify tests_with_failures.xml`
-    Then it should fail with:
-      """
-      tests_with_failures.xml: FAIL: 'foo test' failed to match "bar" with (?-mix:^foo$)'
-      tests_with_failures.xml: FAIL: '' failed to match "This almost matches" with (?-mix:^This matches$)'
-      tests_with_failures.xml: FAIL: 'bar test's os.name is a non-zero pos but specifies a value of 'Bar'
-      tests_with_failures.xml: FAIL: 'bar test' failed to find expected capture group os.version '5.0'. Result was 1.0
-      tests_with_failures.xml: SUMMARY: Test completed with 0 successful, 0 warnings, and 4 failures
-      """
-    And the exit status should be 4

data/identifiers/README.md

@@ -1,70 +0,0 @@
-# Recog: Identifiers
-
-This directory contains lists of standard identifiers for mapping Recog matches.
-The goal is define a standard set of constants to represent known software,
-hardware, vendors, and categories.
-
-This is currently incomplete and will be updated as standardization work moves
-forward.
-
-Fingerprints should use these identifiers whenever possible; if a different name
-or syntax for a given identifier is preferred, this should be implemented in the
-application through a mapping function.
-
-## Lists
-
-### Fields
-
-`fields.txt` defines the various fields (`os.vendor`, etc.) used to assert
-information about a match.
-
-### Vendors
-
-`vendor.txt` defines known vendor names, covering services, operating systems,
-and hardware.
-
-### Operating Systems
-
-`os_architecture.txt` defines known CPU types.
-
-`os_product.txt` defines known operating system names.
-
-`os_family.txt` defines known operating system families.
-
-`os_device.txt` defines known types of devices by function or purpose.
-
-### Hardware
-
-`hw_product.txt` defines known hardware product names.
-
-`hw_family.txt` defines known hardware product families.
-
-`hw_device.txt` defines known types of devices by function or purpose (overlaps
-with `os_device.txt`).
-
-### Services
-
-`service_product.txt` defines known service product names.
-
-`service_family.txt` defines known service product families.
-
-### Software
-
-`software_product.txt` defines known software product names.
-
-`software_family.txt` defines known software product families.
-
-`software_class.txt` defines known types of software by function or purpose.
-
-## Pending Work
-
-* All existing fingerprints should be correlated against these lists to
-  identify mismatches and updated accordingly.
-
-* All net new identifiers from the existing fingerprints should be merged into
-these lists.
-
-* All fingerprint assertions should be enumerated, documented, and standardized
-where possible (`host.mac`, etc).
-
-* Hardware identifiers should be enumerated, consolidated, and standardized.

data/identifiers/fields.txt

@@ -1,105 +0,0 @@
-agilent.serial
-apache.info
-apache.variant
-apache.variant.version
-aptinex.model
-chromecast.capabilities
-chromecast.generation
-cisco.imc_model
-cisco.model
-cookie
-dell.service_tag
-digi.serial_number
-extron.model
-host.domain
-host.ip
-host.mac
-host.mac_eui64
-host.mac_local
-host.name
-host.time
-hw.certainty
-hw.cpe23
-hw.device
-hw.family
-hw.model
-hw.product
-hw.serial_number
-hw.series
-hw.vendor
-hw.version
-imail.eval
-jetty.info
-junction.cookie
-junction.name
-lantronix.serial_number
-lenovo.machine_model
-lenovo.machine_type
-linux.kernel.version
-loadbalancer.poolname
-mdaemon.unregistered
-mercur.os.info
-metainfo.version
-metainfo.version.version
-ms.nttp.version
-notes.build.version
-ntmail.id
-openssh.comment
-openssh.cvepatch
-os.arch
-os.build
-os.certainty
-os.cpe23
-os.device
-os.edition
-os.family
-os.model
-os.product
-os.rev
-os.vendor
-os.version
-os.version.version
-os.version.version.version
-postfix.os.info
-postoffice.build
-postoffice.id
-procurve.model
-proftpd.server.name
-pureftpd.config
-python.version
-qpopper.version
-securetransport.build
-sendmail.config.version
-sendmail.hpux.phne.version
-sendmail.vendor.version
-service.certainty
-service.component.cpe23
-service.component.family
-service.component.product
-service.component.vendor
-service.component.version
-service.cpe23
-service.device
-service.edition
-service.family
-service.node
-service.product
-service.protocol
-service.vendor
-service.version
-service.version.version
-service.version.version.version
-service.version.version.version.version
-siemens.model
-snmp.fpmib.oid.1
-snmp.fpmib.oid.2
-system.time
-system.time.format
-system.time.micros
-system.time.millis
-tandberg.model
-thttpd.mx-patch
-tomcat.info
-unify.model
-wd2go.device_id
-zmailer.ident

data/identifiers/hw_device.txt

@@ -1,84 +0,0 @@
-ADSL Modem
-AV Receiver
-Access Control
-Alarm Panel
-Appliance
-Audio Encoder
-Broadband Router
-Building Automation
-Cable Modem
-Check Scanner
-DOCSIS Cable Modem
-DSL Modem
-DVR
-Data Terminal
-Desktop
-Device
-Device Hub
-Device Server
-Display Controller
-Environment Control
-Ethernet Adapter
-Firewall
-HMI Controller
-Handheld Scanner
-Hypervisor
-IP Camera
-IPS
-Industrial Control
-JTAG Adapter
-KVM
-Laptop
-Light Bulb
-Lights Out Management
-Media Player
-Media Receiver
-Media Server
-Mobile Phone
-Monitoring
-Multifunction Device
-NAS
-Network Appliance
-Network Audio
-Network Management Device
-PLC
-Power Device
-Power Meter
-Power Relay
-Powerline
-Print Server
-Printer
-Relay Controller
-Router
-SD-WAN Appliance
-SIP Device
-SIP Gateway
-Scanner
-Security Appliance
-Sensor
-Smart TV
-Storage
-Storage Appliance
-Support Appliance
-Switch
-Tablet
-Tape Library
-Telecom
-Test Instrument
-Thin Client
-UPS
-VPN
-Video Conference
-Video Conferencing
-Video Decoder
-Video Encoder
-VoIP
-VoIP Server
-VoIP Switch
-Voice Appliance
-WAP
-WLAN Repeater
-Web Cam
-Whiteboard
-Wireless Controller
-Wireless Presenter

data/identifiers/hw_family.txt

@@ -1,121 +0,0 @@
-AR Series
-Adaptive Security Appliance
-Aficio
-AirPort
-Apple TV
-Communication Manager
-DVR
-Data ONTAP
-DiskStation
-Document Centre
-EDR
-Eurotherm
-Extended Systems ExtendNet
-FRITZ!Box
-FRITZ!Fon
-FRITZ!Powerline
-FRITZ!WLAN Repeater
-FS
-Firewall-1
-Forms Printer
-FortiGate
-FortiVoice
-GW25
-GXV
-GXW
-HDX
-HandyTone
-HomePod
-Honeywell
-ILOM
-IMDVR
-ION
-JetDirect
-LX Series
-LaserJet
-LinkCom Xpress
-MGate
-MPEG4 DVR
-MT
-MX Series
-Mac mini
-MacBook
-MacBook Pro
-MegaRAC
-MiiNePort
-Multifunction
-My Book
-NE
-NPort
-NetScaler
-NetVanta
-Netscaler
-Network Audio
-Network Security Appliance
-Network Video Door Station
-OpenScape Desk Phone
-Optra
-Orbi
-POWER System
-Phaser
-Primergy
-Pro Series
-RMX
-ReadyNAS
-RealPresence
-RealPresence Group
-Router
-S500 Range
-SIP Device
-SIP Gateway
-SL2100
-Service Access Switch
-Service Router
-Simatic HMI
-Simatic NET
-Simatic S7
-Simatic Sinumerik
-SoundPoint
-SoundTouch
-SpeedTouch
-Speedport
-Storage
-Sun Fire
-Sunny
-Switch
-System X
-TASKalfa
-TelePresence
-Time Capsule
-TippingPoint
-Turbo Station
-UNIVERGE
-UniFi
-Unified Security Gateway
-VDX
-VSX
-VVX
-Vigor
-VoIP
-WD2GO
-WiMax
-Wide Format
-Wide Format Printer
-WorkCentre
-WorkCentre Pro
-Xserve
-ZXDSL
-ZXHN
-ZXV
-airMAX
-iLO
-iMac
-iPad
-iPad Air
-iPad Pro
-iPad mini
-iPhone
-iPod
-iSTAR Door Controllers
-imageClass
-imageRunner