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

Noisy logging output #21

Closed
GoogleCodeExporter opened this issue Feb 24, 2016 · 1 comment
Closed

Noisy logging output #21

GoogleCodeExporter opened this issue Feb 24, 2016 · 1 comment

Comments

@GoogleCodeExporter
Copy link

Using build260.

Calling connect() method on Connection, produces the following noisy output:

Feb 14, 2013 7:12:32 PM ch.ethz.ssh2.log.Logger info
INFO: kex_algo=diffie-hellman-group14-sha1
Feb 14, 2013 7:12:32 PM ch.ethz.ssh2.log.Logger info
INFO: server_host_key_algo=ssh-dss
Feb 14, 2013 7:12:32 PM ch.ethz.ssh2.log.Logger info
INFO: enc_algo_client_to_server=aes128-ctr
Feb 14, 2013 7:12:32 PM ch.ethz.ssh2.log.Logger info
INFO: enc_algo_server_to_client=aes128-ctr
Feb 14, 2013 7:12:32 PM ch.ethz.ssh2.log.Logger info
INFO: mac_algo_client_to_server=hmac-sha1-96
Feb 14, 2013 7:12:32 PM ch.ethz.ssh2.log.Logger info
INFO: mac_algo_server_to_client=hmac-sha1-96
Feb 14, 2013 7:12:32 PM ch.ethz.ssh2.log.Logger info
INFO: comp_algo_client_to_server=none
Feb 14, 2013 7:12:32 PM ch.ethz.ssh2.log.Logger info
INFO: comp_algo_server_to_client=none


Similarly calling close() on the connection produces:

WARNING: Receive thread: error in receiveLoop: Socket closed

Original issue reported on code.google.com by andrzej....@gmail.com on 15 Feb 2013 at 2:17

@GoogleCodeExporter
Copy link
Author

Fixed in SVN

Original comment by cleondris on 1 Aug 2013 at 12:42

  • Changed state: Fixed

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

1 participant