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

qlog tokens in NEW_TOKEN frames, Retry packets and Initial packets #2863

Merged
merged 1 commit into from
Dec 6, 2020

Conversation

marten-seemann
Copy link
Member

No description provided.

@codecov
Copy link

codecov bot commented Nov 6, 2020

Codecov Report

Merging #2863 (b83e156) into master (b623a10) will increase coverage by 0.01%.
The diff coverage is 100.00%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #2863      +/-   ##
==========================================
+ Coverage   86.22%   86.23%   +0.01%     
==========================================
  Files         133      133              
  Lines        9127     9133       +6     
==========================================
+ Hits         7869     7875       +6     
  Misses        909      909              
  Partials      349      349              
Impacted Files Coverage Δ
qlog/frame.go 98.26% <100.00%> (-0.01%) ⬇️
qlog/packet_header.go 95.65% <100.00%> (+0.78%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b623a10...b83e156. Read the comment docs.

@marten-seemann marten-seemann changed the title log tokens in NEW_TOKEN frames, Retry packets and Initial packets qlog tokens in NEW_TOKEN frames, Retry packets and Initial packets Nov 7, 2020
@@ -130,8 +130,7 @@ func marshalCryptoFrame(enc *gojay.Encoder, f *logging.CryptoFrame) {

func marshalNewTokenFrame(enc *gojay.Encoder, f *logging.NewTokenFrame) {
enc.StringKey("frame_type", "new_token")
enc.IntKey("length", len(f.Token))
enc.StringKey("token", fmt.Sprintf("%x", f.Token))
enc.ObjectKey("token", &token{Raw: f.Token})
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

how sensitive is the token, should it appear in logs?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not very sensitive. All you can do with is initiate a new connection with a lower risk of receiving a Retry.
Also, you could correlate two connections.

@marten-seemann marten-seemann merged commit 2a52a9f into master Dec 6, 2020
@marten-seemann marten-seemann deleted the qlog-token-logging branch December 6, 2020 05:15
@aschmahmann aschmahmann mentioned this pull request May 14, 2021
71 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants