Read private key

[jrootham]

Having a private key hardwired into a gruntfile seems to me to be a really bad idea. I think you need an option that specifies a key file to read.

[lepture]

It does support private key file: https://github.com/spmjs/grunt-scp#more-options

[jrootham]

That would be the agent option? The documentation is not obvious.

[morrissinger]

It does support private key, which by no means has to be hard-coded into the Gruntfile. For example, I use fs.readfilesync() to load my key from a file, and then pass the contents of the file as a buffer or string to options.privateKey in the Grunt task configuration.

The issue I see here is that if you do not provide a password in options.password, the Grunt task will automatically prompt you for one, even if you want to use privateKey authentication instead of password authentication. Seems like the Grunt task should be smart enough to figure out not only whether there is a password on the options object, but also whether it needs one in the first instance.

I've made the appropriate modification to the task, which is available in this pull request: #19

[johnkawakami]

npmjs.org still has 0.1.8 up there, and the bug that morrissinger fixed is still present. (How does this get updated?)

I used grunt.file.read() to read in the file.

options: {
    privateKey: grunt.file.read('/home/johnk/.ssh/thekeyfilenere'), ...
}

[morrissinger]

@spmjs has to bump the version in package.json and npm publish the change.

[wfairclough]

@spmjs this still shows version 0.1.8 on npmjs looks like it has not been published yet even though the version has been bumped to 0.1.9

[dkurucz]

Sorry for the delay, waiting on permissions to publish to npm.

[dkurucz]

I'm not sure your if issue is fixed with 0.1.9 nor 0.1.10, but can you please verify? Current is at 0.1.10

[wfairclough]

@dkurucz v0.1.10 is working for me. Thanks!