On Wed, Aug 25, 2010 at 11:28 PM, <[email protected]> wrote:

> Someone in this group said that he/she has a recipe to build native ssh
> for windows. Can that solve the problem on Windows?
>
> Having ssh in PATH is sufficient or the functionality should be built
> in fossil?


Having ssh in PATH is sufficient.




> I'm asking this because I wonder how will ssh and fossil
> share public/private keys, known_hosts, etc.
>
> - Altu
>
>
> -----Original Message-----
> From: Nathaniel R. Reindl <[email protected]>
> To: [email protected]
> Sent: Thu, Aug 26, 2010 2:44 am
> Subject: Re: [fossil-users] Enhancement: ssh:// sync method
>
>
> On Wed, Aug 25, 2010 at 3:46 PM, Brian Smith <[email protected]>
> wrote:> I'd vote for changing this notation to a more standard scp
> style reference.> I.e.: "[email protected]:local/path" or
> "[email protected]:/full/path".> I've got no strong opinions as to
> whether or not ssh:// is at the> front of those.While I largely agree
> with this, I think it would probably be wisestto peruse the available
> documentation on adopting a scheme for SSHURIs.  The IETF seems to have
> a draft on this particular subject
> at<http://tools.ietf.org/html/draft-ietf-secsh-scp-sftp-ssh-uri-04>.>
> Putty provides a command line tool for doing such operations. Also,
> both> cygwin and mingw provide ssh builds. Windows users desiring SSH
> functionality> are probably used to having to jump through some hoops.
> Having someI'd say that, as a Windows user, I'm reasonably used to
> having to snaga few things to get SSH working, albeit in a completely
> non-performantfashion.Some days I do wish I were still on something
> UNIX-like, but alas! ;)> default lookups> for Putty, cygwin, and mingw
> with an option to specify a custom path> should be sufficient.Anyone
> sane will ensure that these extra tools reside somewhere intheir %Path%
> at the appropriate time, so I wouldn't worry about it.If it's a really
> thorny issue, just allow the user to specify his orher own SSH
> implementation by way of a global configuration parameteror by a shell
> variable.> While I don't personally use Windows, I think having near
> identical feature sets> on all platforms is important.This is probably
> the biggest reason for my draw to Fossil.  I'ddefinitely find SSH
> functionality a huge boon there.That said, in response to drh's
> previous mail, when I get a sparemoment, I'll look at how to emulate
> bi-directional popen()functionality on Win32.  If memory serves, Win32
> natively supportsthis functionality (or something very much like it) in
> some form oranother, but I'll have to go sifting through documentation
> to makesure.;; -*- author-initials: nrr
> -*-_______________________________________________fossil-users mailing
> [email protected]http://lists.fossil-scm.org:8080/cgi
> -bin/mailman/listinfo/fossil-users
>
> _______________________________________________
> fossil-users mailing list
> [email protected]
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>



-- 
D. Richard Hipp
[email protected]
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to