nant / nantcontrib

NAntContrib is the project for tasks and tools that haven't made it into the main NAnt distribution yet or for whatever reason don't belong there.
nantcontrib.sourceforge.net
GNU Lesser General Public License v2.1
51 stars 35 forks source link

Add Ssh/Scp Tasks #17

Open rmboggs opened 12 years ago

rmboggs commented 12 years ago

I would like to add tasks for ssh and scp commands to the nant/nantcontrib project. This would definitely be helpful during the nant release process as well.

Ant Examples: SshExec Scp

Possible .NET/Mono Lib references: Ssh.net SharpSsh

Otherwise, if there are encryption restrictions/concerns, then it may be best to use exernalprogrambase class and just call the command line programs.

drieseng commented 12 years ago

Hey Ryan,

That would definitely be useful. I think an scp task even existed at some point, but could be mistaken.

For me, it's ok to just wrap the scp/ssh commandline tools. This of course does have its limitations (eg. you can't pass it through a filterchain while uploading files), but at least these tools are stable and "just work".

I'll review your move/copy changes today, I promise (I think :p).

Regards, Gert

----- Oorspronkelijk e-mail ----- Van: "Ryan Boggs" reply@reply.github.com Aan: "Gert Driesen" gert.driesen@telenet.be Verzonden: Zaterdag 31 maart 2012 06:13:22 Onderwerp: [nantcontrib] Add Ssh/Scp Tasks (#17)

I would like to add tasks for ssh and scp commands to the nant/nantcontrib project. This would definitely be helpful during the nant release process as well.

Ant Examples: SshExec Scp

Possible .NET/Mono Lib references: Ssh.net SharpSsh

Otherwise, if there are encryption restrictions/concerns, then it may be best to use exernalprogrambase class and just call the command line programs.


Reply to this email directly or view it on GitHub: https://github.com/nant/nantcontrib/issues/17

rmboggs commented 12 years ago

Your correct. The command line tools are time tested and reliable. Some of these .NET libs didn't seem as stable when I was looking.

The other thing to think about also is possible encryption export laws. By using existing command line tools instead of bundling libs, we probably won't need to worry about this. However, I am not a lawyer so I am not sure how accurate this statement is.