On 8/7/20 5:00 PM, Eric Blake wrote:
Take advantage of the fact that we can now detect the type of client
during --tls=on in order to provide safe dummy content for plaintext
clients without having to rewrite plugins to do so.
Signed-off-by: Eric Blake <eblake(a)redhat.com>
---
After playing with this a bit more, I'm thinking:
nbdkit --tls=on --filter=tls-fallback PLUGIN ...
reads better than tlsdummy. Renaming the filter is not too difficult of
a search-and-replace, so I'll go ahead and make that change before
pushing this.
docs/nbdkit-plugin.pod | 4 +-
docs/nbdkit-tls.pod | 5 +-
filters/tlsdummy/nbdkit-tlsdummy-filter.pod | 72 ++++++
configure.ac | 2 +
filters/tlsdummy/Makefile.am | 63 ++++++
filters/tlsdummy/tlsdummy.c | 235 ++++++++++++++++++++
6 files changed, 379 insertions(+), 2 deletions(-)
create mode 100644 filters/tlsdummy/nbdkit-tlsdummy-filter.pod
create mode 100644 filters/tlsdummy/Makefile.am
create mode 100644 filters/tlsdummy/tlsdummy.c
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization:
qemu.org |
libvirt.org