Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Ssh/Scp Tasks #17

Open
rmboggs opened this issue Mar 31, 2012 · 2 comments
Open

Add Ssh/Scp Tasks #17

rmboggs opened this issue Mar 31, 2012 · 2 comments

Comments

@rmboggs
Copy link
Member

rmboggs commented Mar 31, 2012

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
Copy link
Member

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" [email protected]
Aan: "Gert Driesen" [email protected]
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:
#17

@rmboggs
Copy link
Member Author

rmboggs commented Mar 31, 2012

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants