paramiko is too noisy

[Andrew Bennetts]

Juanma Barranquero asked on the mailing list:

> Another question. Is there a way to make paramiko be somewhat quieter?
> In the following:
>
> C:\emacs\trunk> bzr up
> Connected (version 2.0, client OpenSSH_5.1p1)
> Authentication (publickey) successful!
> Secsh channel 1 opened.
> [chan 1] Opened sftp connection (server version 3)
> Tree is up to date at revision 99249.
>
> all but the last line are irrelevant unless an error happens.

They're right, we that is mostly useless noise that we should suppress.
Presumably those messages are emitted via the logging module, so we
should be able to something about this.

A glance at the code suggests that we already set paramiko's log level
to WARNING during auth, so either paramiko is emitting messages like
"Authentication (publickey) successful!" with unreasonably urgent levels,
or we're not doing a good enough job of configuring the logging.

[John A Meinel (jameinel)]

It logs quite a bit of stuff at INFO level. I think Robey said he would decrease Auth...successful to DEBUG in the "next" release. (So the WARNING dance shouldn't be necessary for that part anymore.)

I do find paramiko to be overly verbose, though I often find it useful to know if I actually get a connect or not.

Anyway, we could just set it to WARNING and be done with it, if we really wanted.

[Maciej Katafiasz (mathrick)]

> A glance at the code suggests that we already set paramiko's log level
> to WARNING during auth, so either paramiko is emitting messages like
> "Authentication (publickey) successful!" with unreasonably urgent levels,
> or we're not doing a good enough job of configuring the logging.

Actually, it's only set to WARNING during a single check for auth_none, and for the rest it's at the default setting. A very simple fix is to move that bit of code to the beginning/end of _paramiko_auth().