Alert logging shows Alert(null,null) in Sending messages (client) INFO

[sajualways]

17:16:09 [main] INFO : CommonSendAction - Sending messages (client): (MESSAGE) Send:Alert(null,null) (RECORD) Not configured (TCP) Not configured
17:16:14 [main] INFO : CommonReceiveAction - Received Messages (client): LayerType: MESSAGE As Planned: false Containers: UnreadBytes: 0
LayerType: RECORD As Planned: true Containers: UnreadBytes: 0
LayerType: TCP As Planned: true Containers: TCP{0 Bytes}, TCP{0 Bytes}, TCP{0 Bytes}, TCP{0 Bytes}, TCP{0 Bytes} UnreadBytes: 0

test workflow used to send Bad record mac alert and it is going on wire but log output shows

<Send> <configuredMessages> <Alert> <completeResultingMessage> <modifications> <byteArrayExplicitValueModification> <explicitValue>01 14</explicitValue> </byteArrayExplicitValueModification> </modifications> </completeResultingMessage> </Alert> </configuredMessages> </Send>

[ic0ns]

what is the issue?

[sajualways]

Issue is it shows (null, null) while sending Alert message
17:16:09 [main] INFO : CommonSendAction - Sending messages (client): (MESSAGE) Send:Alert(null,null)

[ic0ns]

Jeah this is on purpose - this just means that you did not preconfigure a Config value for this alert so TLS-Attacker should fallback to the default values

[sajualways]

Jeah this is on purpose - this just means that you did not preconfigure a Config value for this alert so TLS-Attacker should fallback to the default values

But I had set this explicit value and modified the alert to be sent and it is going in real wire packet as well
<Send> <configuredMessages> <Alert> <completeResultingMessage> <modifications> <byteArrayExplicitValueModification> <explicitValue>01 14</explicitValue> </byteArrayExplicitValueModification> </modifications> </completeResultingMessage> </Alert> </configuredMessages> </Send>

[ic0ns]

yes that is a different way of how you can configure an Alert. You are doing runtime modifications, an alternative way is to plan the message by setting <config>0114</config> in the message.

[sajualways]

0114

Can I use this way ?
<Alert> <level>1</level> <description>20</description> </Alert>

[ic0ns]

no

[sajualways]

no

I did try with config as well but it was still showing null,null
` cat tls12.config

0114`

06:58:27 [main] INFO : CommonSendAction - Sending messages (client): (MESSAGE) Send:Alert(null,null) (RECORD) Not configured (TCP) Not configured

[ic0ns]

hm okay - i checked - its a discrepancy between "toString" and "toCompactString" - we can adjust it - in any case - its only a logger issue

[sajualways]

we use the send message to grep and compare the alert sent so it was showing null

[sajualways]

@ic0ns is this fix available in 7.5.1 version ?