(PUP-1368) Fix for segfault when using scheduled_task type in Windows.
The win32-taskscheduler gem has a number of heap corruption bugs having
to do with copying strings from the Task Scheduler API.
This fixes those heap corruptions.
Additionally, a fix to a potential crash in the win32-api gem that was
discovered during investigation is also included in this fix.
Merge remote-tracking branch 'peter/1.9.3' into 1.9.3

* peter/1.9.3:
  (PUP-1368) Fix for segfault when using scheduled_task type in Windows. The win32-taskscheduler gem has a number of heap corruption bugs having to do with copying strings from the Task Scheduler API. This fixes those heap corruptions. Additionally, a fix to a potential crash in the win32-api gem that was discovered during investigation is also included in this fix.
(RE-890) Update ruby to 1.9.3-p484 built against patched libyaml (for CVE-2013-6393)
Merge pull request #24 from haus/1.9.3

(RE-890) Update ruby to 1.9.3-p484 built against patched libyaml (for CV...
(PUP-1284) Return SID correctly for Authenticated Users

When returning the SID for authenticated users (and a couple of other users),
the SID is returned incorrectly as S-1-5-0 (should be S-1-5-11). This is due to
stripping the SID instead of shortening the SID with GetSIDLength. Certain
characters (ASCII 11) look like whitespace and the way win32-security gem works
in the current version is to strip that off, returning an incorrect SID.

This provides a fix until we upgrade win32-security gem.

Details at https://github.com/djberg96/win32-security/issues/3
Merge remote-tracking branch 'rob/ticket/1.9.3/PUP-1284_handle_authenticated_users' into 1.9.3

* rob/ticket/1.9.3/PUP-1284_handle_authenticated_users:
  (PUP-1284) Return SID correctly for Authenticated Users
(PE-3180) win32-security SID buffer size too small

 - When calling Windows::Security::SID.new('foo'), the SID of user 'foo'
   is looked up with the Win32 API call LookupAccountSid.  Unfortunately
   the win32-security gem hardcodes a fixed size buffer which is too
   small for the returned SID under certain circumstances (for domain
   SIDs for instance).  Idiomatic Win32 API states that the first API
   call should be used to determine a buffer size, a buffer should then
   be allocated, and then a subsequent call should be made to the Win32
   API with the appropriate buffer.
 - Being 'more correct' would be a larger code change, so instead the
   simplest approach here is to bump up the buffer size appropriately.
 - Note that the version of win32-security we're presently using is
   > 1 year old, and we do have plans to replace it with a safer 0.2.5+
   version that uses FFI and follows safeer practices around calling
   Win32 APIs.  However, at this time, this requires some more
   involved code changes that may be too large for a bugfix release.
(RE-1438) Rebuilt ruby against updated libyaml 0.1.6
Merge pull request #27 from haus/1.9.3

(RE-1438) Rebuilt ruby against updated libyaml 0.1.6
Merge pull request #26 from Iristyle/ticket/1.9.3/PE-3180-win32-security-sid-data-area-too-small

(PE-3180) win32-security SID buffer size too small
(PUP-1951) Allow elevate.exe to run against .NET 4

 - Various Windows editions ship with various editions of the .NET
   Framework.  This can also vary by how recently Windows Updates have
   run, and local AD policy.
 - According to Corflags.exe, elevate.exe has the following properties
   CorFlags.exe .\elevate.exe
   Microsoft (R) .NET Framework CorFlags Conversion Tool.  Version  4.0.30319.33440
   Copyright (c) Microsoft Corporation.  All rights reserved.

   Version   : v2.0.50727
   CLR Header: 2.5
   PE        : PE32
   CorFlags  : 0x9
   ILONLY    : 1
   32BITREQ  : 0
   32BITPREF : 0
   Signed    : 1
 - .NET 3.5, 3.0 and 2.0.50727 all use the .NET 2.0 CLR, so we can allow
   elevate.exe to run on any of these.
 - After some manual testing, it was determined that the .NET 4.0 CLR
   also works correctly for elevate.exe, and so we can override the .NET
   runtime selection by providing a side ar elevate.exe.config file.
Merge pull request #29 from Iristyle/ticket/master/PUP-1951-override-elevate-dotnet-runtime

(PUP-1951) Allow elevate.exe to run against .NET 4
(re-2172) Update openssl to 1.0.0m