Clarify about how BES uses os_flavor

We don't. We don't use os_flavor anymore because it is no longer
implemented. We get the information from os_name instead.

Author: wchen-r7

lib/msf/core/exploit/remote/browser_exploit_server.rb

@@ -48,7 +48,7 @@ module Exploit::Remote::BrowserExploitServer
       :ua_name,      # Example: MSIE
       :ua_ver,       # Example: 8.0, 9.0
       :os_name,      # Example: Windows 7, Linux
-      :os_flavor,    # Example: Home, Enterprise
+      #:os_flavor,    # Example: Home, Enterprise: (currently not implemented in os detection)
       :os_device,    # Example: iPad, iPhone, etc
       :os_vendor,    # Example: Microsoft, Ubuntu, Apple, etc
       :os_sp,        # Example: SP2
@@ -215,14 +215,14 @@ def get_bad_requirements(profile)
     # 'cookie_name' =>
     # {
     #   :os_name   => 'Windows 7',
-    #   :os_flavor => 'Enterprise',
+    #   :os_flavor => 'Enterprise', # os_flavor is currently not implemented in os detection
     #   ...... etc ......
     # }
     # A profile should at least have info about the following:
     # :source    : The data source. Either from 'script', or 'headers'. The 'script' source
     #              should be more accurate in some scenarios like browser compatibility mode
     # :ua_name   : The name of the browser
-    # :ua_ver    : The version of the browser
+    # :ua_ver    : The version of the browser (not yet implemented)
     # :os_name   : The name of the OS ("Windows XP")
     # :os_flavor : The edition of the OS ("Home")
     # :language  : The system's language
@@ -383,7 +383,6 @@ def get_detection_html(user_agent)
         var osInfo = os_detect.getVersion();
         var d = {
           "os_name"     : osInfo.os_name,
-          "os_flavor"   : osInfo.os_flavor,
           "os_vendor"   : osInfo.os_vendor,
           "os_device"   : osInfo.os_device,
           "ua_name"     : osInfo.ua_name,