|  | Commit message (Collapse) | Author | Age | Files | Lines | 
|---|
| | |  | 
| | |  | 
| | 
| 
| 
| 
| 
| 
| 
| | These pointers will be passed to free. According to asprintf(3), "on
OpenBSD, ret will be set to the null pointer, but this behavior should
not be relied upon."
ok jsing | 
| | 
| 
| 
| | This avoids ever having a non-zero len with a NULL pointer. | 
| | |  | 
| | 
| 
| 
| 
| 
| | in multiple locations.
ok beck@ | 
| | 
| 
| 
| | No change to generated assembly. | 
| | 
| 
| 
| 
| 
| 
| | we can prevent libcrypto from going behind our back and trying to read
passwords from standard input (which we may not be permitted to do).
Found by jsg@ with httpd and password protected keys. | 
| | 
| 
| 
| 
| 
| | potentially dealing with key material. Also switch a calloc to malloc,
since we immediately copy the same amount of data to the newly allocated
buffer. | 
| | |  | 
| | 
| 
| 
| 
| 
| 
| 
| | a tls_load_file() call, ensuring that it the contents become inaccessible.
This is specifically needed on platforms where the library allocators may
be different from the application allocator.
ok beck@ | 
| | 
| 
| 
| 
| 
| 
| 
| 
| | is positive before passing it to several functions as a size_t.
Additionally, in tls_load_file() there is not much point using calloc(),
when we're immediately reading into the buffer (having an extra byte for
NUL termination seems pointless given the API).
ok beck@ miod@ | 
| | 
| 
| 
| | ok tedu@, noted by kinichiro | 
| | 
| 
| 
| | Requested by bluhm@ | 
| | 
| 
| 
| 
| 
| 
| 
| 
| | into memory.  This can be used for tls_config_set_ca_mem(),
tls_config_set_cert_mem() or tls_config_set_key_mem().
With input from jsing@, tedu@ and henning@
OK tedu@ | 
|  | distinguish between LibreSSL (the project) and libressl (the library).
Discussed with many. |