Now setting environment variable nodosfilewarning to True for
Windows / Cygwin, otherwise we get annoying warnings like this:

DOS>ssh-keygen -yl -f "C:\Documents and Settings\Administrator\.ssh\MassiveLauncherKey"
cygwin warning:
  MS-DOS style path detected: C:\Documents and Settings\Administrator\.ssh\Massi
veLauncherKey
  Preferred POSIX equivalent is: /cygdrive/c/Documents and Settings/Administrato
r/.ssh/MassiveLauncherKey
  CYGWIN environment variable option "nodosfilewarning" turns off this warning.
  Consult the user's guide for more details about POSIX paths:
    http://cygwin.com/cygwin-ug-net/using.html#using-pathnames
2048 65:e6:2a:62:48:27:2a:21:42:6b:78:3f:b6:8c:fa:37   MassiveLauncherKey (RSA)
Nasty hack to run OpenSSH binaries from a user-writable location on Windows - required if the user is not an Administator.
Merge branch 'CVLFAB-545-two-part-ui' of github.com:CVL-dev/cvl-fabric-launcher into CVLFAB-545-two-part-ui
double-quote some Windows paths
Merge pull request #18 from l1ll1/CVLFAB-545-two-part-ui

fix the checkprojects command for cvl
os.environ['nodosfilewarning'] = "True" should have been:
os.environ['CYGWIN'] = "nodosfilewarning"
Now fixed.
Merge pull request #19 from l1ll1/CVLFAB-545-two-part-ui

beter testing on the getProjects code to determine if we really need the...
Removing double_quote(...) from paths to Windows SSH binaries
because this resulted in a lack of automagic escaping of
backslashes in Windows file paths.
On Windows, I was getting "Could not open a connection to your
authentication agent" when I tried to add the key to the agent,
but this message was just being logged silently.  Now it is
displayed to the user, but of course, I'm hoping that we can
avoid it happening in the first place!
Disabling dirty hack for now which copied OpenSSH for Windows
binaries into user's home directory, so that they had write
access to the "tmp" directory.  Given how many places
sshKeyDist.sshpaths.ssh_binaries is now called in, copying
the OpenSSH binaries every time is too slow.  I would like
to try modifying the InnoSetup script to give the user
write access to the tmp directory within the Launcher's
installation directory.
Re-added Carlo's double_quote(...)'s for the Windows SSH binaries.

Where I'm using subprocess.Popen with shell=False, I'm now using
sshBinary.strip('"').  Quoting requirements are different
depending on whether shell=True or False, e.g. see:
http://stackoverflow.com/questions/804995/how-to-use-subprocess-when-multiple-arguments-contain-spaces

I see that Chris is starting to use my new classes and
methods in sshKeyDist, e.g. KeyModel.addKeyToAgent(...)
I recently added a new callback for an error I was seeing on
Windows: "Could not open a connection to your authentication agent."
(see CVLFAB-600), so I added the new callback into Chris's code.
Message dialog reporting success on changing passphrase is
now done within onOK of ChangeKeyPassphraseDialog, which
helps with consistency betwen calling ChangeKeyPassphraseDialog
from menu versus calling it from InspectKeyDialog.
Fixed up some Windows-specific issues with the key-updating
and key-generating methods in KeyModel.
Fixed minor issue with panel sizing on ChangePassphraseDialog.
Fixed issue where ssh-add failed silently when an empty
passphrase was used for a key locked by a non-empty passphrase.
ssh-add was just exiting silently, not giving "Bad passphrase".
Added passphraseIncorrectCallback() for case where ssh-add
fails silently on Windows, because it is most likely because
an empty passphrase was supplied for a passphrase-locked key.
merge