[ 
https://issues.apache.org/jira/browse/SSHD-1230?focusedWorklogId=686643&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-686643
 ]

ASF GitHub Bot logged work on SSHD-1230:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 25/Nov/21 22:36
            Start Date: 25/Nov/21 22:36
    Worklog Time Spent: 10m 
      Work Description: tomaswolf merged pull request #210:
URL: https://github.com/apache/mina-sshd/pull/210


   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

            Worklog Id:     (was: 686643)
    Remaining Estimate: 0h
            Time Spent: 10m

> sshd-netty logs all traffic on INFO level
> -----------------------------------------
>
>                 Key: SSHD-1230
>                 URL: https://issues.apache.org/jira/browse/SSHD-1230
>             Project: MINA SSHD
>          Issue Type: Bug
>    Affects Versions: 2.7.0
>            Reporter: Robert Varga
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Enabling NettyIoServiceFactoryFactory leads to all traffic going through the 
> SSHD to be logged on INFO level:
> {noformat}
> 2021-11-25T11:31:18,911 | INFO  | nioEventLoopGroup-6-1 | LoggingHandler      
>              | 59 - io.netty.common - 4.1.69.Final | [id: 0x5ddc1968, 
> L:/127.0.0.1:32834 - R:/127.0.0.1:17840] FLUSH2021-11-25T11:31:18,912 | INFO  
> | nioEventLoopGroup-6-1 | LoggingHandler                   | 59 - 
> io.netty.common - 4.1.69.Final | [id: 0x5ddc1968, L:/127.0.0.1:32834 - 
> R:/127.0.0.1:17840] WRITE: 320B
>          +-------------------------------------------------+
>          |  0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f |
> +--------+-------------------------------------------------+----------------+
> |00000000| bb 62 7e e1 9e 66 19 fc 26 2a d5 fa 33 07 ed 3b |.b~..f..&*..3..;|
> |00000010| 75 6a 7b c5 dc 72 46 c8 75 82 12 83 35 16 11 a9 |uj{..rF.u...5...|
> |00000020| 78 f8 58 69 81 41 94 55 bb e6 5e a4 3d 25 21 b5 |x.Xi.A.U..^.=%!.|
> |00000030| 8f 00 6c 78 cd 11 dc e2 55 34 ac 51 9d e3 09 ec |..lx....U4.Q....|
> |00000040| 42 bb c8 f7 af b2 82 e7 ab a3 61 13 0a cd 54 26 |B.........a...T&|
> |00000050| 51 bb de 66 a0 5c d6 23 94 d1 0b 7c 4a 33 90 b4 |Q..f.\.#...|J3..|
> |00000060| 9e 04 26 5a a7 ba 77 4f fd 70 77 4d 73 65 de 9e |..&Z..wO.pwMse..|
> |00000070| 48 de fc 22 ca 97 5c 10 66 a7 89 14 64 24 8c e6 |H.."..\.f...d$..|
> |00000080| fe b1 ed b6 43 48 90 f8 ec 57 d8 ac 40 a5 83 35 |[email protected]|
> |00000090| af f7 a6 b3 ab 2b a8 b9 f2 b5 ec 7b ab e2 03 51 |.....+.....{...Q|
> |000000a0| 55 18 95 4f 18 0b 53 8f 7e 86 2f 3e 19 78 c5 5c |U..O..S.~./>.x.\|
> |000000b0| e7 42 8e d4 fe dc ab b5 e8 1b 30 51 e6 ff 35 aa |.B........0Q..5.|
> |000000c0| 56 25 c7 2c 8a 24 0c 1c d4 ce 5a 9a 2d 67 0b 6a |V%.,.$....Z.-g.j|
> |000000d0| af b4 38 bd 5b 75 0f 1a 1a 59 50 14 60 ff a4 68 |..8.[u...YP.`..h|
> |000000e0| 1c 6a c8 eb d6 56 9e 35 7d 74 c7 06 4b a4 50 2f |.j...V.5}t..K.P/|
> |000000f0| e7 91 ae 34 a4 60 0e 2e 2f bb a6 58 77 7f 4b 9c |...4.`../..Xw.K.|
> |00000100| d2 5a 99 ee a5 b4 c1 5c 5a c1 2a 9b b4 6c 5c e0 |.Z.....\Z.*..l\.|
> |00000110| 4b e2 04 2e b2 32 df 88 52 74 65 ef c6 a8 45 87 |K....2..Rte...E.|
> |00000120| 64 c0 0b 41 8c b7 cb 85 75 7d 3c 3c d2 57 4e 0b |d..A....u}<<.WN.|
> |00000130| 98 f0 cb e3 2d ae b1 aa d1 b2 75 14 43 6d 46 8f 
> |....-.....u.CmF.|{noformat}
> This is caused by NettyIoConnector explicitly setting the log level to info, 
> overriding the netty-default level (debug). Also the identity of the class 
> responsible for logging is squashed to LoggingHandler, which makes it 
> difficult to control through normal logger configuration.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to