| Commit message (Collapse) | Author | Age | Files | Lines | 
| | 
| 
| 
|  | 
suggested by jsing
 | 
| | 
| 
| 
|  | 
ok jsing
 | 
| | 
| 
| 
|  | 
ok jsing
 | 
| | 
| 
| 
|  | 
ok jsing
 | 
| | 
| 
| 
| 
| 
| 
| 
|  | 
These are two functions that will help streamlining various functions
in the TLSv1.3 code that do not need to know about the interna of this
struct.
input/ok jsing
 | 
| | 
| 
| 
| 
| 
| 
| 
| 
|  | 
This implements the key material exporter for TLSv1.3, as defined in
RFC8446 section 7.5.
Issue reported by nmathewson on github.
ok inoguchi@ tb@
 | 
| | 
| 
| 
| 
| 
|  | 
rather than the hash of an empty context
ok jsing@
 | 
| | 
| 
| 
|  | 
Spotted by maestre@, ok tb@
 | 
| | 
| 
| 
|  | 
Reported by Ben L <bobsayshilol at live dot co dot uk>
 | 
| | 
| 
| 
|  | 
ok jsing@
 | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
|  | 
When the RFC refers to ("") for key derivation, it is referring to the
transcript hash of an empty string, not an empty string. Rename
tls13_secrets_new() to tls13_secrets_create(), make it take an EVP_MD *
and calculate the hash of an empty string so that we have it available
for the "derived" and other steps. Merge tls13_secrets_init() into
the same function, remove the EVP_MD * from other functions and use the
empty string hash at the appropriate places.
ok beck@ tb@
 | 
| |  | 
 | 
| | 
| 
| 
|  | 
discussed with beck and jsing
 | 
|   
  
  
   | 
ok jsing@ tb@
 |