WinRM HTTPS listener

[hh]

I'd like to be able to update the Vagrant box for WinRb/WinRM#151
I started working on a stake at #24

Do you plum yours using the atlas builds? Mine seemed to dye at around 5 hours:

@mwrock I gave you read permissions on https://atlas.hashicorp.com/vulk/build-configurations/win2k12r2/builds/4

[mwrock]

Hey @hh, yeah 6 hours is the Atlas timeout which is about how long it takes for me to build on local bare metal. I publish the builds to https://atlas.hashicorp.com/mwrock/boxes/Windows2012R2 which is public. I also convert it to Hyper-V. Would be awesome if I could run the builds on atlas but I understand having a reasonable timeout for a public service. It would probably work if you removed the windows update step but its kinda nice to have a patched box.

[hh]

@sethvargo we'd like to get these Windows 2012 images to build on Atlas w/ updates included. However it takes longer that the current build timeout. Do you have any suggestions or alternatives that would help?

[hh]

It looks like @hashicorp cashes the isos (makes sense), I wonder we could setup a local windows update server or use something like a caching squid proxy in another build?

[hh]

It does look like it's http traffic and not https. I'm going to try an http caching approach locally, see if I can speed up those builds. On a side note, it looks like MS uses Akamai, I wonder if there's a way to influence their caching to get it closer to Atlas.