Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
needed for body-hashing
|
|
defer=pass mode
|
|
|
|
Broken-by: 02b41d7106
|
|
|
|
|
|
|
|
|
|
Broken-by: 9e70917d0a
|
|
|
|
|
|
|
|
|
|
notes to docs
|
|
|
|
|
|
|
|
* `/usr/local` is fair, on Linux, but I deliberately picked something
specific to OpenSSL to make the context clear and limit bad
interactions with other locally-installed software.
* `RPATH` and `RUNPATH` are not the same and are deeply twisty in their
interactions.
<https://blog.qt.io/blog/2011/10/28/rpath-and-runpath/> is a decent
summary.
|
|
|
|
|
|
Broken-by: 328c5688db
|
|
last header line being hashed.
|
|
|
|
|
|
indicating guess
|
|
|
|
|
|
|
|
|
|
Broken-by: 42055a3385
|
|
|
|
|
|
Extremely basic; we have no control of the DNS use of the dmarc library
|
|
Previously "skipped" was added; that is no only done for an actual
call which could not be completed
|
|
Broken-by: c780096c29
|
|
|
|
|
|
OpenSSL 1.1.1 is not released yet, but operation has been checked against the current source
|
|
per-message loop
|
|
|
|
Using `LDFLAGS=` instead of `LDFLAGS+=` will stomp over an earlier
setting of LDFLAGS, and the DMARC support is now further up in
`src/EDITME`, thus likely to get stomped upon.
Rather than continue to document using `PKG_CONFIG_PATH` via env, the
in-Local/Makefile support has been around for a little while now, so go
ahead and make that the only way we suggest here.
Add a mention of _why_ we use both `USE_OPENSSL_PC` and `LDFLAGS`.
|
|
|
|
|
|
|
|
message loop
|
|
|
|
|