Wouter Verhelst

Oh, hm. The validation of the signature is different between macOS and Windows, so it might be that there is a bug in one of the two. If you are...

Sorry, I didn't mean for you to put that data in the issue :laughing: You can send it to my email address. It's on a number of commits in this...

Ping. Haven't received any emails with the requested files (unless I missed it; if so my apologies). I don't mind if you don't want to share, but without the files...

We communicated privately for a bit, but no information was sent in the end. Closing this ticket, as it makes no sense to keep something like that open.

Which version of nbd-server was this with? I believe we fixed a bug very similar to this one not that long ago.

> There's an AUR package but it tracks the git repo on sourceforge. Is it still syncing over there? https://aur.archlinux.org/packages/nbd-git No, we stopped syncing to sourceforge a while back. >...

One more thing here: If a file is not writable by the nbd-server process, it will mark the expor tas read-only (since any write will fail). What are the permissions...

When specifying an export on the command line, the syntax is "host@port", not "host:port". Note that specifying exports on the command line is deprecated though.

`nbd-server` uses glib's [GThreadPool](https://developer-old.gnome.org/glib/2.68/glib-Thread-Pools.html) to implement async handling of requests. That has a function [to set the maximum number of threads](https://developer-old.gnome.org/glib/2.68/glib-Thread-Pools.html#g-thread-pool-set-max-threads), which is what we use when you set `max_threads`....

However, the issue still exists, and I do still want to keep it on my radar, so reopening.