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

introduce a type for the stateless reset key #3621

Merged
merged 1 commit into from Nov 16, 2022

Conversation

marten-seemann
Copy link
Member

Just accepting a byte slice is a dangerous API. Using a single byte (say) for a stateless reset key is not very secure - an attacker could trivially bruteforce the stateless reset token. Using a 32 byte key is arbitrary, but seems like a reasonable key size.

@codecov
Copy link

codecov bot commented Nov 15, 2022

Codecov Report

Base: 85.49% // Head: 85.49% // Increases project coverage by +0.00% 🎉

Coverage data is based on head (f9a25b0) compared to base (7b211d6).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #3621   +/-   ##
=======================================
  Coverage   85.49%   85.49%           
=======================================
  Files         142      142           
  Lines       10294    10295    +1     
=======================================
+ Hits         8800     8801    +1     
  Misses       1109     1109           
  Partials      385      385           
Impacted Files Coverage Δ
interface.go 0.00% <ø> (ø)
multiplexer.go 94.44% <100.00%> (ø)
packet_handler_map.go 72.48% <100.00%> (+0.11%) ⬆️

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

@marten-seemann marten-seemann merged commit 8d496eb into master Nov 16, 2022
@marten-seemann marten-seemann deleted the stateless-reset-key-type branch November 16, 2022 22:44
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.

None yet

2 participants