[jira] [Updated] (VCL-611) Windows Images may be registered with the wrong KMS host

["Josh Thompson (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/VCL-611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Josh Thompson updated VCL-611:
------------------------------
    Fix Version/s: 2.6

> Windows Images may be registered with the wrong KMS host
> --------------------------------------------------------
>
>                 Key: VCL-611
>                 URL: https://issues.apache.org/jira/browse/VCL-611
>             Project: VCL
>          Issue Type: Bug
>          Components: vcld (backend)
>    Affects Versions: 2.3
>            Reporter: Aaron Coburn
>            Priority: Major
>             Fix For: 2.6
>
>
> In the Windows::Version_6.pm:activate() subroutine, the function returns TRUE if the windows image has already been activated. This will result in an activated windows OS, but it will be registered with the incorrect KMS host under the following conditions:
> If there are multiple affiliations using a common infrastructure at, for instance, campus A.
> AND
> if campus A runs a KMS server on a network on which (port 1688) broadcast requests from VCL images are received and accepted
> Even though the VCL clears all activation records during the capture process, when a windows image (owned by campus B) boots up, it will still send a broadcast request on port 1688, and KMS activation happens automatically, albeit with campus A's KMS. Then, when the VCL checks the OS whether windows has been activated, it sees that it has and it proceeds no further. Thus, the image from campus B is registered under campus A's MS license agreement.
> But by putting this block:
> if($self->activate_kms || $self->activate_mak){
>   ...
> }
> before this block:
> if($license_status && $license_status =~ /licensed/i){
> ...
> }
> then everything works as it should.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)