recog 2.0.24 → 2.1.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (53) hide show
  1. checksums.yaml +4 -4
  2. data/README.md +1 -1
  3. data/features/data/matching_banners_fingerprints.xml +2 -1
  4. data/features/data/multiple_banners_fingerprints.xml +2 -0
  5. data/features/match.feature +6 -6
  6. data/lib/recog/db.rb +33 -11
  7. data/lib/recog/db_manager.rb +6 -2
  8. data/lib/recog/fingerprint.rb +39 -2
  9. data/lib/recog/nizer.rb +93 -20
  10. data/lib/recog/version.rb +1 -1
  11. data/spec/lib/fingerprint_self_test_spec.rb +7 -0
  12. data/spec/lib/recog/nizer_spec.rb +165 -3
  13. data/xml/apache_os.xml +1 -1
  14. data/xml/architecture.xml +1 -1
  15. data/xml/fingerprints.xsd +91 -0
  16. data/xml/ftp_banners.xml +456 -74
  17. data/xml/h323_callresp.xml +1 -1
  18. data/xml/hp_pjl_id.xml +4 -1
  19. data/xml/http_cookies.xml +1 -1
  20. data/xml/http_servers.xml +1 -1
  21. data/xml/http_wwwauth.xml +1 -1
  22. data/xml/imap_banners.xml +1 -1
  23. data/xml/ldap_searchresult.xml +1 -1
  24. data/xml/mdns_device-info_txt.xml +1 -1
  25. data/xml/mdns_workstation_txt.xml +1 -1
  26. data/xml/mysql_banners.xml +1 -1
  27. data/xml/mysql_error.xml +1 -1
  28. data/xml/nntp_banners.xml +1 -1
  29. data/xml/ntp_banners.xml +1 -1
  30. data/xml/operating_system.xml +1 -1
  31. data/xml/pop_banners.xml +1 -1
  32. data/xml/rsh_resp.xml +1 -1
  33. data/xml/sip_banners.xml +1 -1
  34. data/xml/sip_user_agents.xml +1 -1
  35. data/xml/smb_native_lm.xml +1 -1
  36. data/xml/smb_native_os.xml +1 -1
  37. data/xml/smtp_banners.xml +5 -1
  38. data/xml/smtp_debug.xml +4 -1
  39. data/xml/smtp_ehlo.xml +4 -1
  40. data/xml/smtp_expn.xml +4 -1
  41. data/xml/smtp_help.xml +4 -1
  42. data/xml/smtp_mailfrom.xml +1 -1
  43. data/xml/smtp_noop.xml +4 -1
  44. data/xml/smtp_quit.xml +4 -1
  45. data/xml/smtp_rcptto.xml +1 -1
  46. data/xml/smtp_rset.xml +4 -1
  47. data/xml/smtp_turn.xml +4 -1
  48. data/xml/smtp_vrfy.xml +4 -1
  49. data/xml/snmp_sysdescr.xml +1 -1
  50. data/xml/snmp_sysobjid.xml +1 -1
  51. data/xml/ssh_banners.xml +1 -1
  52. data/xml/upnp_banners.xml +1 -1
  53. metadata +4 -3
@@ -3,7 +3,7 @@
3
3
  Responses to H.323 call SETUP messages are matched against these patterns
4
4
  to fingerprint H.323 servers.
5
5
  -->
6
- <fingerprints>
6
+ <fingerprints protocol="h.323" database_type="service" preference="0.80">
7
7
  <fingerprint pattern="^0x000b2d00\:(.*)\:.*?(\d*\.*\d*\.*\d*).*$" flags="REG_ICASE">
8
8
  <description>Sony H.323 Server</description>
9
9
  <param pos="0" name="service.vendor" value="Sony"/>
@@ -3,8 +3,11 @@
3
3
  For printers running the PJL protocol (usually on 9100/tcp), their type can be requested
4
4
  by the INFO ID command. The printer types (strings surrounded by double quotes) are
5
5
  matched against these patterns to fingerprint the printer.
6
+
7
+ 'preference' notes: The value has been explicitly set to 0.10 due to the very loose
8
+ regex that is used here.
6
9
  -->
7
- <fingerprints>
10
+ <fingerprints protocol="pjl" database_type="service" preference="0.10">
8
11
  <!--
9
12
  LaserJet and Designjet are registered trademarks of HP. Therefore matching for the keywords
10
13
  is sufficient for asserting all relevant information
@@ -3,7 +3,7 @@
3
3
  Set-Cookie HTTP header values are matched against these patterns to fingerprint HTTP
4
4
  servers.
5
5
  -->
6
- <fingerprints matches="http_header.cookie">
6
+ <fingerprints matches="http_header.cookie" protocol="http" database_type="service">
7
7
  <fingerprint pattern="^(CFCLIENT_[^=]+|CFGLOBALS|CFID|CFTOKEN)=.*">
8
8
  <description>
9
9
  Adobe (Macromedia) ColdFusion uses various cookies.
@@ -1,6 +1,6 @@
1
1
  <?xml version="1.0" encoding="UTF-8"?>
2
2
  <!-- HTTP Server headers are matched against these patterns to fingerprint HTTP servers. -->
3
- <fingerprints matches="http_header.server">
3
+ <fingerprints matches="http_header.server" protocol="http" database_type="service" preference="0.90">
4
4
  <fingerprint pattern="^Stronghold/(\d\.\d) Apache/([012][\d.]*)\s*(.*)$">
5
5
  <description>Red Hat Stronghold Enterprise Apache</description>
6
6
  <example>Stronghold/3.0 Apache/1.3.19 RedHat/3014c</example>
@@ -1,6 +1,6 @@
1
1
  <?xml version="1.0" encoding="UTF-8"?>
2
2
  <!-- HTTP WWW-Authenticate headers are matched against these patterns to fingerprint HTTP servers. -->
3
- <fingerprints matches="http_header.wwwauth">
3
+ <fingerprints matches="http_header.wwwauth" protocol="http" database_type="service" preference="0.85">
4
4
  <fingerprint pattern="^(?:Basic|Digest) realm=.[iI]RMC(?:@(IRMC[0-9a-fA-F]{6}))?..*$">
5
5
  <description>Fujitsu Siemens Primergy with BMC RemoteView on an iRMC card</description>
6
6
  <param pos="0" name="service.vendor" value="Fujitsu Siemens"/>
@@ -1,6 +1,6 @@
1
1
  <?xml version="1.0" encoding="UTF-8"?>
2
2
  <!-- IMAP banners are matched against these patterns to fingerprint IMAP servers. -->
3
- <fingerprints matches="imap4.banner">
3
+ <fingerprints matches="imap4.banner" protocol="imap" database_type="service" preference="0.90">
4
4
  <fingerprint pattern="^Microsoft Exchange IMAP4rev1 server version (5\.5\.\d{4}\.\d+) \((.*)\) ready$">
5
5
  <description>Microsoft Exchange Server 5.5</description>
6
6
  <param pos="0" name="service.vendor" value="Microsoft"/>
@@ -3,7 +3,7 @@
3
3
  Notes: Ruby will fail to build the RegExp if it contains \x84 which is a standard
4
4
  byte in ASN.1 Sequence length fields.
5
5
  -->
6
- <fingerprints matches="ldap.search_result">
6
+ <fingerprints matches="ldap.search_result" protocol="ldap" database_type="service" preference=".80">
7
7
 
8
8
  <!--
9
9
  Samba - position prior to Windows entries due to regex. When testing new
@@ -6,7 +6,7 @@
6
6
  to the domain name for a server to respond with the record:
7
7
  e.g. 'host-name._device-info._tcp.local'.
8
8
  -->
9
- <fingerprints matches="mdns.device-info.txt">
9
+ <fingerprints matches="mdns.device-info.txt" protocol="mdns" database_type="util.os">
10
10
  <!--
11
11
  OS X versions:
12
12
  The number specified after osxvers= is equivalent to the major
@@ -6,7 +6,7 @@
6
6
  to the domain name for a server to respond with the record:
7
7
  e.g. 'host-name._workstation._tcp.local'.
8
8
  -->
9
- <fingerprints matches="mdns.workstation.txt">
9
+ <fingerprints matches="mdns.workstation.txt" protocol="mdns" database_type="service">
10
10
  <fingerprint pattern="^org\.freedesktop\.Avahi\.cookie=\S+$">
11
11
  <description>Avahi</description>
12
12
  <example>org.freedesktop.Avahi.cookie=1023312927</example>
@@ -10,7 +10,7 @@
10
10
  the TCP payload and the fingerprints below are used to match and extract
11
11
  from this version.
12
12
  -->
13
- <fingerprints matches="mysql.banners">
13
+ <fingerprints matches="mysql.banners" protocol="mysql" database_type="service" preference="0.75">
14
14
  <fingerprint pattern="^(\d{1,2}\.\d{1,3}\.[a-f\d]{1,3}(?:[.-]\d{1,2})?(?:[.-]\d{1})?)(?:-m\d{1,2})?(?:-rc)?(?:-alpha)?(?:-beta)?(?:-gamma)?(?:-?max)?(?:-rs)?(?:-modified)?(?:-debug)?(?:-log)?$" flags="REG_ICASE">
15
15
  <description>Oracle MySQL (common)</description>
16
16
  <example service.version="4.1.20">4.1.20</example>
@@ -23,7 +23,7 @@
23
23
  http://osxr.org/mysql/source/sql/share/errmsg-utf8.txt or
24
24
  https://github.com/twitter/mysql/blob/master/sql/share/errmsg-utf8.txt
25
25
  -->
26
- <fingerprints matches="mysql.error">
26
+ <fingerprints matches="mysql.error" protocol="mysql" database_type="service" preference=".80">
27
27
  <!-- ER_HOST_NOT_PRIVILEGED -->
28
28
  <fingerprint pattern="^Stroj '[^']+' nemá povoleno se k tomuto MySQL serveru připojit$">
29
29
  <description>Oracle MySQL error ER_HOST_NOT_PRIVILEGED (cze)</description>
@@ -3,7 +3,7 @@
3
3
  NNTP greeting messages (part of the banner after the response code) are matched
4
4
  against these patterns to fingerprint NNTP servers.
5
5
  -->
6
- <fingerprints matches="nntp.banner">
6
+ <fingerprints matches="nntp.banner" protocol="nntp" database_type="service">
7
7
  <fingerprint pattern="^NNTP Service (?:.*) Version: (5.0.2195.[0-9]+) .*$">
8
8
  <description>Microsoft IIS NNTP Server on Windows 2000</description>
9
9
  <example>NNTP Service 5.00.0984 Version: 5.0.2195.7034 Posting Allowed</example>
@@ -2,7 +2,7 @@
2
2
  <!--
3
3
  NTP "banners", taken from a readvar response
4
4
  -->
5
- <fingerprints matches="ntp.readvar">
5
+ <fingerprints matches="ntp.readvar" protocol="ntp" database_type="service" preference="0.80">
6
6
  <fingerprint pattern="^.*version=Domain Time II (\S+),hostname=([^,]+),.*system=Win2003.*,processor=(\S+)" flags="REG_DOT_NEWLINE,REG_ICASE">
7
7
  <description>Greyware Automation Products, Inc. Domain Time II on Windows Server 2003</description>
8
8
  <example service.version="5.1.b.20100331R" os.arch="x64" host.name="blah">
@@ -2,7 +2,7 @@
2
2
  <!--
3
3
  Patterns for common names of various operating systems.
4
4
  -->
5
- <fingerprints matches="operating_system.name">
5
+ <fingerprints matches="operating_system.name" database_type="util.os" preference="0.80">
6
6
  <!-- Windows begin -->
7
7
  <fingerprint pattern="^(?i:(?:Microsoft )?(Windows (?:[a-z]+\s[a-z]+\s|[a-z]+\s)?Server (?:\d{4} R2|\d{4}))(?:,\s|\s)?([a-z]+)?(?: Edition)?(?:\s)?(SP\d|SP \d|Service Pack \d)?)$">
8
8
  <description>Windows Server 2003 and later</description>
@@ -3,7 +3,7 @@
3
3
  POP3 greeting messages (part of the banner after the status indicator +OK or -ERR) are
4
4
  matched against these patterns to fingerprint POP3 servers.
5
5
  -->
6
- <fingerprints matches="pop3.banner">
6
+ <fingerprints matches="pop3.banner" protocol="pop3" database_type="service" preference="0.90">
7
7
  <fingerprint pattern="^([^ ]+) +Cyrus POP3 v(\d+\.\d+.*)-OS X(?: Server)? ([\d\.]+).* server ready">
8
8
  <description>OSX Cyrus POP</description>
9
9
  <example host.domain="8.8.8.8" service.version="2.3.8" os.version="10.5">8.8.8.8 Cyrus POP3 v2.3.8-OS X Server 10.5: 9A562 server ready &lt;1999107648.1324502155@8.8.8.8&gt;</example>
@@ -2,7 +2,7 @@
2
2
  <!--
3
3
  Rservices responses to requests are matched against these patterns to fingerprint the OSes of servers.
4
4
  -->
5
- <fingerprints>
5
+ <fingerprints protocol="rsh" database_type="service">
6
6
  <fingerprint pattern="^.Permission denied: Error 0$">
7
7
  <description>Digital Unix rlogind</description>
8
8
  <example>xPermission denied: Error 0</example>
@@ -2,7 +2,7 @@
2
2
  <!--
3
3
  SIP Server header values are matched against these patterns to fingerprint SIP devices.
4
4
  -->
5
- <fingerprints matches="sip_header.server">
5
+ <fingerprints matches="sip_header.server" protocol="sip" database_type="service">
6
6
  <fingerprint pattern="^Cisco-SIPGateway/IOS-([\d\.x]+)$">
7
7
  <description>Cisco SIPGateway</description>
8
8
  <example>Cisco-SIPGateway/IOS-12.x</example>
@@ -2,7 +2,7 @@
2
2
  <!--
3
3
  SIP User Agent header values are matched against these patterns to fingerprint SIP devices.
4
4
  -->
5
- <fingerprints matches="sip_header.user_agent">
5
+ <fingerprints matches="sip_header.user_agent" protocol="sip" database_type="service">
6
6
  <!-- Cisco Devices -->
7
7
  <fingerprint pattern="^Cisco-SIPGateway/IOS-([\d\.x]+)$">
8
8
  <description>Cisco SIPGateway</description>
@@ -3,7 +3,7 @@
3
3
  SMB fingerprints obtained from the Native LM (LAN manager) field of SMB
4
4
  negotations
5
5
  -->
6
- <fingerprints matches="smb.native_lm">
6
+ <fingerprints matches="smb.native_lm" protocol="smb" database_type="service">
7
7
  <!-- Mac OS X -->
8
8
  <fingerprint pattern="^Samba (3\.0\.28a-apple)$">
9
9
  <description>Samba on OS X 10.6</description>
@@ -2,7 +2,7 @@
2
2
  <!--
3
3
  SMB fingerprints obtained from the Native OS field of SMB negotations
4
4
  -->
5
- <fingerprints matches="smb.native_os">
5
+ <fingerprints matches="smb.native_os" protocol="smb" database_type="util.os">
6
6
  <fingerprint pattern="^(Windows NT \d\.\d+)$">
7
7
  <description>Windows NT</description>
8
8
  <example os.product="Windows NT 4.0">Windows NT 4.0</example>
@@ -17,8 +17,12 @@ These XML files are used in this order:
17
17
  smtp_quit.xml
18
18
 
19
19
  The system or service fingerprint with the highest certainty overwrites the others.
20
+
21
+ 'preference' notes: This value has been impacted by the poor quality of the 'Cisco PIX' match.
22
+ Additionally, the 'preference' value for the other databases mentioned above has been set so
23
+ as to implement their preference as described.
20
24
  -->
21
- <fingerprints matches="smtp.banner">
25
+ <fingerprints matches="smtp.banner" protocol="smtp" database_type="service" preference="0.20">
22
26
  <fingerprint pattern="^X1 NT-ESMTP Server ([^ ]+) \(IMail (\d+\.[^ ]+) EVAL \d+-\d+\)$">
23
27
  <description>IMail EVAL version</description>
24
28
  <param pos="0" name="service.vendor" value="Ipswitch"/>
@@ -4,8 +4,11 @@ SMTP response lines to the DEBUG command are matched against these patterns
4
4
  (1 line at a time) to fingerprint SMTP servers.
5
5
 
6
6
  See comment at the top of smtp_banners.xml for additional info.
7
+
8
+ 'preference' note: This value has been set so as to implement the ordering
9
+ of SMTP related fingerprint databases as described in 'smtp_banners.xml'.
7
10
  -->
8
- <fingerprints>
11
+ <fingerprints protocol="smtp" database_type="service" preference="0.14">
9
12
  <fingerprint pattern="^500 No way!$">
10
13
  <description>
11
14
  Exim
@@ -4,8 +4,11 @@ SMTP response lines to the EHLO command are matched against these patterns
4
4
  (1 line at a time) to fingerprint SMTP servers.
5
5
 
6
6
  See comment at the top of smtp_banners.xml for additional info.
7
+
8
+ 'preference' note: This value has been set so as to implement the ordering
9
+ of SMTP related fingerprint databases as described in 'smtp_banners.xml'.
7
10
  -->
8
- <fingerprints>
11
+ <fingerprints protocol="smtp" database_type="service" preference='0.19'>
9
12
  <fingerprint pattern="^500[ -]Syntax error, command &quot;XXXX&quot; unrecognized$">
10
13
  <description>
11
14
  Cisco PIX changes the command letters to 'X' before passing
@@ -4,8 +4,11 @@ SMTP response lines to the EXPN command are matched against these patterns
4
4
  (1 line at a time) to fingerprint SMTP servers.
5
5
 
6
6
  See comment at the top of smtp_banners.xml for additional info.
7
+
8
+ 'preference' note: This value has been set so as to implement the ordering
9
+ of SMTP related fingerprint databases as described in 'smtp_banners.xml'.
7
10
  -->
8
- <fingerprints>
11
+ <fingerprints protocol="smtp" database_type="service" preference="0.16">
9
12
  <fingerprint pattern="^500[ -]Syntax error, command &quot;XXXX.*&quot; unrecognized$">
10
13
  <description>
11
14
  Cisco PIX changes the command letters to 'X' before passing
@@ -4,8 +4,11 @@ SMTP response lines to the HELP command are matched against these patterns
4
4
  (1 line at a time) to fingerprint SMTP servers.
5
5
 
6
6
  See comment at the top of smtp_banners.xml for additional info.
7
+
8
+ 'preference' note: This value has been set so as to implement the ordering
9
+ of SMTP related fingerprint databases as described in 'smtp_banners.xml'.
7
10
  -->
8
- <fingerprints>
11
+ <fingerprints protocol="smtp" database_type="service" preference="0.18">
9
12
  <fingerprint pattern="^214[ -]This is ArGoSoft Mail Server, Version [^ ]+ \(([^ ]+\.[^ ]+\.[^ ]+\.[^ ]+)\) *$">
10
13
  <description>
11
14
  ArgoSoft mail server HELP response
@@ -2,7 +2,7 @@
2
2
  <!--
3
3
  This file is currently unused.
4
4
  -->
5
- <fingerprints>
5
+ <fingerprints protocol="smtp" database_type="service">
6
6
  <fingerprint pattern="250 .* is syntactically correct *">
7
7
  <description>exim</description>
8
8
  <example>250 &lt;nosuchuser@rapid7.com&gt; is syntactically correct</example>
@@ -4,8 +4,11 @@ SMTP response lines to the NOOP command are matched against these patterns
4
4
  (1 line at a time) to fingerprint SMTP servers.
5
5
 
6
6
  See comment at the top of smtp_banners.xml for additional info.
7
+
8
+ 'preference' note: This value has been set so as to implement the ordering
9
+ of SMTP related fingerprint databases as described in 'smtp_banners.xml'.
7
10
  -->
8
- <fingerprints>
11
+ <fingerprints protocol="smtp" database_type="service" preference="0.17">
9
12
  <fingerprint pattern="^220 OK.*$">
10
13
  <description>
11
14
  CheckPoint FireWall-1 returns code 220 for NOOP command (instead of 250)
@@ -4,8 +4,11 @@ SMTP response lines to the QUIT command are matched against these patterns
4
4
  (1 line at a time) to fingerprint SMTP servers.
5
5
 
6
6
  See comment at the top of smtp_banners.xml for additional info.
7
+
8
+ 'preference' note: This value has been set so as to implement the ordering
9
+ of SMTP related fingerprint databases as described in 'smtp_banners.xml'.
7
10
  -->
8
- <fingerprints>
11
+ <fingerprints protocol="smtp" database_type="service" preference="0.11">
9
12
  <fingerprint pattern="^221[ -]See ya in cyberspace$">
10
13
  <description>
11
14
  221 See ya in cyberspace
@@ -2,7 +2,7 @@
2
2
  <!--
3
3
  This file is currently unused.
4
4
  -->
5
- <fingerprints>
5
+ <fingerprints protocol="smtp" database_type="service">
6
6
  <!--
7
7
  <fingerprint pattern="501[ -]Invalid domain *">
8
8
  <description>
@@ -4,8 +4,11 @@ SMTP response lines to the RSET command are matched against these patterns
4
4
  (1 line at a time) to fingerprint SMTP servers.
5
5
 
6
6
  See comment at the top of smtp_banners.xml for additional info.
7
+
8
+ 'preference' note: This value has been set so as to implement the ordering
9
+ of SMTP related fingerprint databases as described in 'smtp_banners.xml'.
7
10
  -->
8
- <fingerprints>
11
+ <fingerprints protocol="smtp" database_type="service" preference="0.12">
9
12
  <fingerprint pattern="^250[ -]RSET\? Well, OK\.$">
10
13
  <description>
11
14
  500 What? I don't understand that.
@@ -4,8 +4,11 @@ SMTP response lines to the TURN command are matched against these patterns
4
4
  (1 line at a time) to fingerprint SMTP servers.
5
5
 
6
6
  See comment at the top of smtp_banners.xml for additional info.
7
+
8
+ 'preference' note: This value has been set so as to implement the ordering
9
+ of SMTP related fingerprint databases as described in 'smtp_banners.xml'.
7
10
  -->
8
- <fingerprints>
11
+ <fingerprints protocol="smtp" database_type="service" preference="0.13">
9
12
  <fingerprint pattern="^502[ -]Hey! I don't let remote systems TURN on me\.$">
10
13
  <description>
11
14
  502 Hey! I don't let remote systems TURN on me.
@@ -4,8 +4,11 @@ SMTP response lines to the VRFY command are matched against these patterns
4
4
  (1 line at a time) to fingerprint SMTP servers.
5
5
 
6
6
  See comment at the top of smtp_banners.xml for additional info.
7
+
8
+ 'preference' note: This value has been set so as to implement the ordering
9
+ of SMTP related fingerprint databases as described in 'smtp_banners.xml'.
7
10
  -->
8
- <fingerprints>
11
+ <fingerprints protocol="smtp" database_type="service" preference="0.15">
9
12
  <fingerprint pattern="^500[ -]Syntax error, command &quot;XXXX.*&quot; unrecognized$">
10
13
  <description>
11
14
  Cisco PIX changes the command letters to 'X' before passing
@@ -4,7 +4,7 @@
4
4
  SNMP fingerprint definitions. These are matched against the value of the
5
5
  'sysDescr' (OID 1.3.6.1.2.1.1.1) variable.
6
6
  -->
7
- <fingerprints matches="snmp.sys_description">
7
+ <fingerprints matches="snmp.sys_description" protocol="snmp" database_type="service" preference="0.20">
8
8
  <!--======================================================================
9
9
  3COM
10
10
  =======================================================================-->
@@ -3,7 +3,7 @@
3
3
  SNMP fingerprint definitions for SysObjectIDs. These are matched against the value of the
4
4
  'sysObjectID' (OID 1.3.6.1.2.1.1.2) variable.
5
5
  -->
6
- <fingerprints matches="snmp.sys_object_id">
6
+ <fingerprints matches="snmp.sys_object_id" protocol="snmp" database_type="service">
7
7
  <!--======================================================================
8
8
  MICROSOFT
9
9
  =======================================================================-->
@@ -4,7 +4,7 @@ SSH "software revision and comment" strings (official RFC nomenclature for the p
4
4
  the identification string after "SSH-x.x-") are matched against these patterns to
5
5
  fingerprint SSH servers.
6
6
  -->
7
- <fingerprints matches="ssh.banner">
7
+ <fingerprints matches="ssh.banner" protocol="ssh" database_type="service" preference="0.90">
8
8
  <!-- Honeypot SSH server banners are useless for fingerprinting -->
9
9
  <fingerprint pattern="honeypot" flags="REG_ICASE">
10
10
  <description>Honeypot SSH</description>
@@ -1,6 +1,6 @@
1
1
  <?xml version="1.0" encoding="UTF-8"?>
2
2
  <!-- UPnP Server headers are matched against these patterns to fingerprint UPnP servers. -->
3
- <fingerprints matches="ssdp_header.server">
3
+ <fingerprints matches="ssdp_header.server" protocol="ssdp" database_type="service" preference="0.70">
4
4
  <fingerprint pattern="^Linux/(\S+) UPnP/[\d\.]+ miniupnpd/([\d\.]+)$" flags="REG_ICASE">
5
5
  <description>Linux MiniUPnPd UPnP Server</description>
6
6
  <example>Linux/Cross_compiled UPnP/1.0 miniupnpd/1.0</example>
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: recog
3
3
  version: !ruby/object:Gem::Version
4
- version: 2.0.24
4
+ version: 2.1.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - Rapid7 Research
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2016-11-09 00:00:00.000000000 Z
11
+ date: 2016-11-22 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: rspec
@@ -237,7 +237,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
237
237
  version: '0'
238
238
  requirements: []
239
239
  rubyforge_project:
240
- rubygems_version: 2.2.5
240
+ rubygems_version: 2.5.2
241
241
  signing_key:
242
242
  specification_version: 4
243
243
  summary: Network service fingerprint database, classes, and utilities
@@ -268,3 +268,4 @@ test_files:
268
268
  - spec/lib/recog/nizer_spec.rb
269
269
  - spec/lib/recog/verify_reporter_spec.rb
270
270
  - spec/spec_helper.rb
271
+ has_rdoc: