Question on Windows Build
Maritza Mendez
martitzam at gmail.com
Sat Oct 9 17:04:53 BST 2010
I'm going to set up a Winx86 build and then see if I can make it go for
Winx64.
I'm looking at doc/win32_build_setup.txt and have a couple questions and a
tip:
After following references, its not obvious to me whether this is still
relevant:
k) Patch pycrypto, so that it supports older Windows installs. (see bugs
> #248522, #272791, #497733). The direct link to the patch is:
> http://launchpadlibrarian.net/16133025/win32_clock.patch
> This may not end up necessary w/ pycrypto 2.1, especially if paramiko
> can
> be taught to use the new functionality (avoiding the warning).
>
Is that timing patch still needed for Windows? I'm guessing yes, but I'd
like a confirmation.
Also I'm guessing that the advice on downloading the prebuilt (32-bit) zlib
DLL should change for x64. Yes?
FYI, the advice about PuTTY's ssh-agent,
If you do this, you'll probably also want to install a shortcut to
> ``pageant.exe`` in Start / Programs / Startup so that it always starts
> when
> you log in (though you still have to manually add your ssh keys.)
>
can be improved by noticing that Windows shortcuts can pass arguments. If
you edit the shortcut property and change the target from "C:\Program
Files\PuTTY\pageant.exe" to "C:\Program Files\PuTTY\pageant.exe" "<full path
to your private key>" then every time you log in you will be prompted for
your passphrase (You did set a passphrase, right?) and then automatically
load and cache your private key. Obviously, if you don't have control of
the machine and need to worry about other processes sniffing memory, then do
not do this. Note that I recommend double-quotes around each of the exe
path and the key path as a best practice to deal with spaces in Windows
paths.
Thanks
~M
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/bazaar/attachments/20101009/1bb9f3cd/attachment.htm
More information about the bazaar
mailing list