From www@isc.org Sat Apr 29 21:10:38 2017 MIME-Version: 1.0 X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,RP_MATCHES_RCVD,UNPARSEABLE_RELAY autolearn=ham autolearn_force=no version=3.4.0 X-Mailer: PHPMailer 5.2.22 (https://github.com/PHPMailer/PHPMailer) content-type: text/plain; charset="utf-8" Message-ID: Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by bugs.isc.org (Postfix) with ESMTP id A3A1071B5A8 for ; Sat, 29 Apr 2017 21:10:38 +0000 (UTC) Received: from iscwebprod.isc.org (iscwebprod.isc.org [IPv6:2001:4f8:1:d::16]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 3445F349315 for ; Sat, 29 Apr 2017 21:10:36 +0000 (UTC) Received: from www (uid 80) (envelope-from www@iscwebprod.isc.org) id 7b7d08 by iscwebprod.isc.org (DragonFly Mail Agent v0.11); Sat, 29 Apr 2017 21:10:35 +0000 Delivered-To: bind-suggest@bugs.isc.org Subject: BIND 9.11.1 - windows version detection/identification Return-Path: X-Original-To: bind-suggest@bugs.isc.org Date: Sat, 29 Apr 2017 21:10:35 +0000 X-Wpcf7-Content-Type: text/plain X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on mx.pao1.isc.org X-PHP-Originating-Script: 20001:class-phpmailer.php To: bind-suggest@isc.org From: "Tony Marques" X-RT-Original-Encoding: utf-8 X-RT-Interface: Email Content-Length: 2069 Bug Report from www.isc.org: Name: Tony Marques Email: tm_iscbind@10am.com Software Version: BIND 9.11.1 OS: Microsoft Windows Subject:windows version detection/identification Bug Detail =========== / [issue.1: -v output does not use STDOUT] -v commands don't output version information via STDOUT or whatever but use ERROUT? so "dig -v 2>nul:" will produce no output and can't be read via a "for /F %a in ('[cmd]')" batch command and "dig -v >file.txt" produces an empty file while normal commands like 'dig +x ics.org 2>nul:' do output to console and can be used via "for /F" batch commands or can be piped to a file or other command so -v is considered internal perfunctory/procedural output like a banner header rather than the objective/target data. this should be fixed and produce output via STDOUT to the console or wherever. / [issue.2: no windows file properties] Executables (and .dll files) are not stamped with the versions so you can't view the version via in the properties tab in Explorer nor utilize vbscript CreateObject("Scripting.FileSystemObject").GetFileVersion( ... ) scripting and powershell commands also produce no results gci dig.exe | % { "{1}`t{2}`t{0}" -f $_.Name, [System.Diagnostics.FileVersionInfo]::GetVersionInfo($_).FileVersion, [System.Diagnostics.FileVersionInfo]::GetVersionInfo($_).ProductVersion } as would "filever.exe dig.exe" Microsoft support command as would "sigcheck.exe -q -n dig.exe" sysinternals command BINDInstall.exe (presumably because it is a Windows GUI program) is the only executable stamped with version information (except for vcredist_x64.exe from microsoft-- and libeay32.dll from openssl which are also stamped), but even the latest version is FileVersion: 3.0.0 (the main version info and also ProductVersion 9.10.0 -- not usually viewed) ... so this is not current or up-to-date and has remained the same for the multitude of releases over the past several years -- presumably since 2014 (per the copyright) and release 9.10.0. --- This email was received through isc.org Bug Submission Form