You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
on the logs. The packet data could potentially be a security vulnerability. It also provides little use when printed to the logs. We should instead update these logs to only print that a packet is being sent with a certain sequence on a certain source port/channel. Destination port/channel are optional as they can always be queried since every source port/channel is associated with a destination port/channel. It might be useful to log the timeouts as well, the packet data can be left off
Applications such as transfer, may then log state changes triggered by packet send, such as escrowing/burning tokens
We should audit all our logs to ensure we aren't dumping unnecessary information
For Admin Use
Not duplicate issue
Appropriate labels applied
Appropriate contributors tagged/assigned
The text was updated successfully, but these errors were encountered:
Summary
Currently in
SendPacket
we log the entire packet being sent, this might look like:on the logs. The packet data could potentially be a security vulnerability. It also provides little use when printed to the logs. We should instead update these logs to only print that a packet is being sent with a certain sequence on a certain source port/channel. Destination port/channel are optional as they can always be queried since every source port/channel is associated with a destination port/channel. It might be useful to log the timeouts as well, the packet data can be left off
Applications such as transfer, may then log state changes triggered by packet send, such as escrowing/burning tokens
We should audit all our logs to ensure we aren't dumping unnecessary information
For Admin Use
The text was updated successfully, but these errors were encountered: