Commits
- Commit:
23e92df733278366c3204e9536e3785c30493f4d
- From:
- Omar Polo <op@omarpolo.com>
- Date:
- Tue Aug 29 09:39:28 2023 UTC
extend/sync .gitignore
- Commit:
1218bca611fd6b67d82104b9f21b95b81f25014e
- From:
- Omar Polo <op@omarpolo.com>
- Date:
- Tue Aug 29 09:36:36 2023 UTC
add -e to gencert usage() string
- Commit:
96515efd278ce8ad5bbc2528d8197e766674cdae
- From:
- Omar Polo <op@omarpolo.com>
- Date:
- Tue Aug 29 09:35:07 2023 UTC
tweak gemexp logs
gemexp is meant for local testing so I'm not too worried about
changing its log format if it makes sense to do so.
- Commit:
80745f04113ce73ae4f5aaba5c6a458af92590d0
- From:
- Omar Polo <op@omarpolo.com>
- Date:
- Tue Aug 29 09:30:28 2023 UTC
regress: change naming scheme for certs, add GENCERT_FLAGS knob
Call the certificates .pem and the keys .key; use contrib/gencert
to generate the certificates and provide a GENCERT_FLAGS knob so
that regress can be run with EC keys (GENCERT_FLAGS=-e). Still no
automatic way of testing with both RSA and EC keys.
- Commit:
eaca1ed4dbf841dfe709ae0d5050b0b64dc42a1f
- From:
- Omar Polo <op@omarpolo.com>
- Date:
- Tue Aug 29 09:26:55 2023 UTC
sync changelog
- Commit:
a6d07f09e008431d8c257f9432c0193351951295
- From:
- Omar Polo <op@omarpolo.com>
- Date:
- Tue Aug 29 09:26:14 2023 UTC
gemexp: save certs to $XDG_DATA_HOME/gemexp, not /gmid
- Commit:
f31289a8acc233e8a92029dcfca0eb07ac11e39b
- From:
- Omar Polo <op@omarpolo.com>
- Date:
- Tue Aug 29 09:24:14 2023 UTC
gemexp: change the naming scheme for the certificates
Using what the manpage advertised. The regress adaptations will
follow. The directory will also change (and the key type too.)
- Commit:
b894573ad9c5173af9f4a9403d54ad67e4ba0bcf
- From:
- Omar Polo <op@omarpolo.com>
- Date:
- Tue Aug 29 09:18:55 2023 UTC
fix typo; the size computation is done using len, not ret
- Commit:
c440a0ded9bef20b32c6f86b27cdf5ab52e1e16f
- From:
- Omar Polo <op@omarpolo.com>
- Date:
- Mon Aug 28 21:42:58 2023 UTC
log ip address and port when tls_handshake fails
These connection are not otherwise logged and it could be helpful
to track down the bad ip.
- Commit:
6be41efe33421ba5d24cdb5837a3c0d1cb70a471
- From:
- Omar Polo <op@omarpolo.com>
- Date:
- Mon Aug 28 21:39:59 2023 UTC
tweak log_request() comment
gg -> gemexp and better wording.
- Commit:
a6c8b8051eccbdcbaa219bf0afc97519a7d0d1a5
- From:
- Omar Polo <op@omarpolo.com>
- Date:
- Mon Aug 28 21:38:09 2023 UTC
don't let crypto_dispatch_server handle IMSG_CRYPTO_ECDSA_SIGN
in this codepath. otherwise we end up with a mismatch where we
expect a request but were sent a response.
- Commit:
3cba037a11a67b63d8684dfe7a42779931316e91
- From:
- Omar Polo <op@omarpolo.com>
- Date:
- Mon Aug 28 21:37:27 2023 UTC
pre-increment reqid
otherwise we send the request id N and expect to receive N+1
- Commit:
6c86d810fc19669cc9b970d8fef26b6375b2361f
- From:
- Omar Polo <op@omarpolo.com>
- Date:
- Mon Aug 28 21:36:58 2023 UTC
typo; was filling the wrong iov_len...
- Commit:
7bbf17a8576cb5850f42b10ff75d422c428b701b
- From:
- Omar Polo <op@omarpolo.com>
- Date:
- Fri Aug 25 12:19:49 2023 UTC
plug a leak
all other rules are freeing the value of `listen_addr'
- Commit:
c2c051f28e8934a679f5ebe8195497ce5eccc56c
- From:
- Omar Polo <op@omarpolo.com>
- Date:
- Fri Aug 25 12:19:00 2023 UTC
fix automatic guessing of `listen on'
default_host needs to be NULL for getaddrinfo(3) to listen on
everything.