- This topic has 2 replies, 2 voices, and was last updated 1 month, 1 week ago by
.
-
Posts
-
Hi NoMachiners,
we’ve just released 8.14. This is an important update because it includes the new OpenSSL libraries v. 3.0.15, fixing CVE-2024-6119 and CVE-2024-5535 (see https://openssl-library.org/news/openssl-3.0-notes/index.html for more details). We’ve also imported fixes for CVE-2024-7264 (libnxht) and CVE-2023-49582 (apache)
This release also implements a solution for macOS 15 client installations which solves a problem of local network permissions being ignored. Sequoia users are invited to update their installations and follow the instructions that we have published in the knowledge base: https://www.nomachine.com/AR09V01251.
The full announcement and complete list of fixes is available here: https://kb.nomachine.com/SU10V00261
As a MacOS user, thank you for this much anticipated upgrade. Very happy to not have to invoke Terminal each time I want to use NM. So we’ve gone now from having to use a workaround each time we start NM to a workaround each time we start MacOS. Really hope also this last hurdle will be tackled in a future update.
From a communication standpoint, please allow me to say that it would have been a lot more effective if NM had simply acknowledged and embraced the problem from the start. Instead it sounded like the problem was waved away and users were blamed for using beta releases. If so many users come up with the exact same issue, something is wrong. The fact that it comes up in beta-releases is a good thing. That’s what beta’s are for. Just say: “We’re aware of the problem and are working on a solution and plan to have it fixed by the time the final version of MacOS is released or shortly thereafter.”
Because in the end that is exactly what NM seemed to have done, again, for which many users will be very grateful.
Thanks for the feedback and we’ll take it on board to improve communications 🙂
So we’ve gone now from having to use a workaround each time we start NM to a workaround each time we start MacOS. Really hope also this last hurdle will be tackled in a future update.
About this, it seems we are not the only application affected. We are currently awaiting feedback from the Apple developers to understand better why this happens and how we can mitigate it. In the meantime, we made the decision to release the fix we have, with the additional workarounds.
You must be logged in to reply to this topic. Please login here.