Closed birbilis closed 1 year ago
It probably won't change the result, but 1.3.0 is the latest release.
It seems it may be a fault with the ZeroMQ library. Has it happened only the once?
Just once, had forgotten Mosco running. Wonder if it's related to known ZeroMQ exploits: https://www.cvedetails.com/vulnerability-list/vendor_id-14186/Zeromq.html (read some older ZeroMQ versions went down via some assertion on malformed packages)
I'll keep the issue open for now in case there's a recurrence
Mosco 1.4.0 Beta 2 has ZeroMQ removed, so if it is related to that, it should disappear :-) Beta is here
Without using Mosco I see some errors occured (two days after last use), wonder if someone was trying to hack at the port it was listening on (does it allow to set some password? - I'm using a cloud-based Mac):
I'm using a beta you had recently provided when diagnosing another issue
the 2nd error occured when I tried to Stop it from the menu. Eventually I did Quit from the menu and launched it again