On 2013/09/11 14:24:04, fwereade wrote:
> On 2013/09/11 02:21:17, dfc wrote:
> > On 2013/09/11 02:07:37, axw wrote:
> > > Please take a look.
> >
> > Can I suggest a different solution.
> >
> > 1. Use cmd.Output, not CombinedOutput
I want stderr still (for the error), so I need to set Stderr. So I'm
setting Stdout for consistency.
> > 2. pass "-o", "StrictHostKeyChecking no", we do that elsewhere in
cmd/juju so
> it
> > has a precident.
Okay. The stderr is getting squashed anyway, unless there's a real
error, so it's not a real security concern.
> +1. Isn't there a common set of ssh flags somewhere?
On 2013/09/11 14:24:04, fwereade wrote:
> On 2013/09/11 02:21:17, dfc wrote:
> > On 2013/09/11 02:07:37, axw wrote:
> > > Please take a look.
> >
> > Can I suggest a different solution.
> >
> > 1. Use cmd.Output, not CombinedOutput
I want stderr still (for the error), so I need to set Stderr. So I'm
setting Stdout for consistency.
> > 2. pass "-o", "StrictHostKeyC hecking no", we do that elsewhere in
cmd/juju so
> it
> > has a precident.
Okay. The stderr is getting squashed anyway, unless there's a real
error, so it's not a real security concern.
> +1. Isn't there a common set of ssh flags somewhere?
No. I'll create a tech-debt bug.
https:/ /codereview. appspot. com/13477045/