hurzhurz

I would like to know the proper way to do this, too. But if it helps anyone, I was able to build the docker image after modifying the dockerfile. Here...

@wez You can simply manually download and place the files in the right location like I did: static-device-names.config to /etc/config/static-device-names static-device-names.init to /etc/init.d/static-device-names (probably needs chmod +x) static-device-names.hotplug to /etc/hotplug.d/net/static-device-names...

I don't know if that is helpful, but I had pretty much the same issue and somehow got it working now. Though, first isql wasn't working, too. But after I...

> What was the one additional library package that you installed? isql isn't working for me too. I'm not sure anymore, but I think in my case it was one...

I thought about that but wasn't sure if I should touch the function. Hope it is ok how I have done it now...

Got the same issue. Pretty sure it is caused by this change in roots.py from 3006.6: [e0cdb80](https://github.com/saltstack/salt/commit/e0cdb80b55123f4a024759ffcf2b3f0e0788e7ab#diff-1f96c1bf1efb4edbad6f6ea24768d127521489e238b3e5ff466a1c56323257d6) I have not checked this in depth, but probably `salt.utils.verify.clean_path()` doesn't like symlink,...

@alan-cugler I'm pretty sure it was not intended to disallow symlinks, it is just a side effect of the fix for a critical CVE: https://saltproject.io/security-announcements/2024-01-31-advisory/index.html And by the way, there...

For a temporary workaround (until there will hopefully be a solution), maybe try what I already suggested in #66133: > Quick workaround would be to take the roots.py from 3006.5...

@jtlarson I have not tried to modify the verify.py as a workaround. I'm not sure if that is easily possible. It might depend on the installation method or package type...

@dwoz ok, I gave it a try and wrote some tests. please have a look