Since there are no replies yet I will take a stab that I hope will help get you closer and not send you off on a wild goose chase because of me being an idiot or something.
You may also know all of the following, if so sorry.
I run into Undefined symbol errors usually when some software is trying to call a function it expects to be in a library but the function isn’t because I have the wrong version of the library.
So yeah I think it may be a dependency issue.
The next thing is to figure out which package holds libharfbuzz so you can determine what version of that package you have vs what version is required by Davinci Resolve.
Something I learned about Nobara is that updating software has to either be done in the Nobara package manager or with a specific set of commands on the command line or you might break stuff (like I just did). It seems plausible that if you updated with a simple dnf update on the command line it may have caused issues.
Also… Are you installing Resolve from a Flatpak or …?
I would then go look for it in Nobara package manager and see if it needs updating or not and see what version it is running.
Another thing I would check is what version is standard in the supported distros. I’m guessing that list includes Fedora and Ubuntu and/or Debian. If the version they expect is different from what you have then we need a way to make the right version available. I’m not sure what is the best answer but I have a few ideas that I would try if it were me.
Man I tell you, apps that have one off install approaches like this are so annoying. I’ve run into this a few times. It just leaves me feeling dirty. Why can’t they just distribute an AppImage or rpm for Pete’s sake?
I just checked on Pop!_OS to see what version I’m running there because I know everything works fine. harfbuzz isn’t even installed…
When I’m finished work later today I’ll have a look on Nobara for the version installed cs expected etc.
EDIT: I solved the issue.I came across a similar issue on the GitHub repo for harfbuzz and while reading the log file again I had an ah-ha moment. More details in the post.
Since he doesn't mention it in his 'fantastic' reporting, OpenSSH 9.6 was released Monday that will patch this attack. Also, since he doesn't mention it, if on the Internet, the MITM would have to be installed at both end points (client side and server side) to be effective without the patch.
Since he doesn’t mention it in his ‘fantastic’ reporting, OpenSSH 9.6 was released Monday that will patch this attack.
I am tempted to delete this post just for the article’s stupid clickbait headline, but it still will probably cause some people to go update their OpenSSH installs, so… meh.
Anyone who actually wants to know details of the vulnerability should read the website about it which is obviously much better than this article.
Also, since he doesn’t mention it, if on the Internet, the MITM would have to be installed at both end points (client side and server side) to be effective without the patch.
Huh? No. The attacker doesn’t need to be in two places or even near either end per se, they could be located at any fully on-path position between the client and server.
No other company will contribute to LXD now. This is 100% a Canonical tool. Were the big clouds looking at deploying LXD so Canonical tried to block them?
So you need an MitM situation to even be able to perfom the attack, and the the attack on works on two ciphers? The article says those ciphers are commonly enabled, but are they default or used in relatively modern distributed versions of openssh?
A scan performed by the researchers found that 77 percent of SSH servers exposed to the Internet support at least one of the vulnerable encryption modes, while 57 percent of them list a vulnerable encryption mode as the preferred choice.
That means a client could negotiate one or the other on more than half of all internets exposed openssh daemons.
I haven’t got too whizzed up over this, yet, because I have no ssh daemons exposed without a VPN outer wrapper. However it does look nasty.
linux
Newest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.