On Thursday, January 1, 2015 3:38:31 PM UTC-6, PMario wrote:
>
> Be aware, that it should work with windows too.
>

But of course. That's one of the reasons I am looking closely at the 
various scp and rsync implementations available under node, to make sure 
they can be adapted to Windows (some assume a [ba]sh shell under the 
covers).

My thinking right now is to start with scp (because that's what I'm 
interested in for myself), and for Windows support either/both Cygwin's scp 
and PuTTY's pscp.exe, assuming no one has written a native client sshlib 
for node (and assuming it's trustworthy - I have far more trust in Cygwin 
and PuTTY).

The other thing I want to work through is credentials. At least one of the 
popular node implementations has you pass in the userid and password as 
parameters that then get passed to a sub-shell via the command line, which 
I think is $#!+ (because they would then be accessible via ps or Task 
Manager while the scp process is running, for example). I know people will 
still want that because they think their system is safely single-user and 
will never be hacked and no one will ever find those credentials stashed in 
their script files. But I would also like to support simply allowing 
scp/pscp to prompt at run-time as it already does as well as be able to use 
public/private key pairs. And again, in the case of using key pairs I'd 
have to handle both password-protected private key stores as well as ones 
that have no password, for those people who think their private keys will 
never get stolen (and seriously, for those people who want to run this 
unattended, perhaps via cron or a continuous integration process).

Hopefully all that makes sense.

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/tiddlywikidev.
For more options, visit https://groups.google.com/d/optout.

Reply via email to