Skip to content

Issues: tls-n/nss-tlsn

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.

Sign up for GitHub

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

19 Open 0 Closed
19 Open 0 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

I couldn't test it, but I think this is never freed
#20 opened Apr 13, 2018 by FDeRubeis
should it be renamed into num_normal_chunks?
#19 opened Apr 12, 2018 by FDeRubeis
shouldn't a non existing chunk be considered non-sensitive?
#18 opened Mar 6, 2018 by FDeRubeis
Padding computation must not be done anymore
#17 opened Mar 6, 2018 by FDeRubeis
I think the size of this array must be set with realloc. If two consecutive nodes are hidden, in fact, one does not need to store both their hases, they can directly store the root hash of the subtree.
#16 opened Feb 21, 2018 by FDeRubeis
Can this function be cancelled?
#15 opened Feb 20, 2018 by FDeRubeis
How does this thing work? You have a struct ProofNode. It contains an enum called TLSProofNodeType, but its length is not specified. You copy its first byte on the proof string. How does the program know that the enum must be only one byte?
#14 opened Feb 19, 2018 by FDeRubeis
3
Since the evidence size can exceed the one of the packet, it might be sent in multiple packets. In that case, all the packet data must be put together, and then the handling function called.
#13 opened Feb 16, 2018 by FDeRubeis
Extend ordering_vector_len to 32 bits.
#12 opened Feb 15, 2018 by FDeRubeis
2
Implement stricter controls for the incoming messages. Also in the handle message request and handle message response functions.
#11 opened Feb 15, 2018 by FDeRubeis
Rename it to add message to evidence
#10 opened Feb 15, 2018 by FDeRubeis
Rename it to request the evidence
#9 opened Feb 15, 2018 by FDeRubeis
Should we return 0 here?
#8 opened Feb 14, 2018 by FDeRubeis
As far as I can understand, this structure qill be sent to the peer, but it uses a variable type which is typical of NSS. This might make it not compatible with other applications.
#7 opened Feb 13, 2018 by FDeRubeis
1
The OrderingVectorLenIs reduced to 16 bytes, is it accidental or on purpose?
#6 opened Feb 13, 2018 by FDeRubeis
1
Resizing allocation
#5 opened Feb 6, 2018 by FDeRubeis
We saw that the function only works if the hash_size is exactly twice the salt_size. This is a note to remember to modify this function.
#4 opened Feb 5, 2018 by FDeRubeis
No Network-Byte Order
#3 opened Jan 31, 2018 by ritzdorf
6
Clarification requested: must server-side of an HTTPS session use specific TLS-N code?
#2 opened Oct 27, 2017 by gojomo
2
ProTip! Adding no:label will show everything without a label.