test log spammed with TLS handshake
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Expired
|
Low
|
Unassigned |
Bug Description
I just had a Windows.log test failure:
http://
It is full of lines like:
2016/07/26 15:17:00 tls.serverHands
2016/07/26 15:17:00 xxxx got good cipher: &{c030 20 0 4 bbade0 d 0 0 bba160}
2016/07/26 15:17:00 exiting clienthello
2016/07/26 15:17:00 starting full handshake
2016/07/26 15:17:00 no error from serverhandshake
2016/07/26 15:17:00 Requested ciphersuites:
2016/07/26 15:17:00 c02c
2016/07/26 15:17:00 c02b
2016/07/26 15:17:00 c030
2016/07/26 15:17:00 c02f
2016/07/26 15:17:00 Server supported ciphersuites:
2016/07/26 15:17:00 c02c
2016/07/26 15:17:00 c02b
2016/07/26 15:17:00 c030
2016/07/26 15:17:00 c02f
2016/07/26 15:17:00 preference list
2016/07/26 15:17:00 c02c
2016/07/26 15:17:00 c02b
2016/07/26 15:17:00 c030
2016/07/26 15:17:00 c02f
2016/07/26 15:17:00 supported list:
2016/07/26 15:17:00 c02c
2016/07/26 15:17:00 c02b
2016/07/26 15:17:00 c030
2016/07/26 15:17:00 c02f
2016/07/26 15:17:00 vers: 771
Those look like lines coming from a debug system, but its lots of detailed output that doesn't seem actionable. (It also doesn't seem to follow our standard 'logger' syntax to include a package and a filename and line number.)
As this is a tech-debt item, I am lowering its Importance.