Battling to setup salt on fresh install for some stuff and come across the denied popup showing bold black Qub instead of Qube during denied message, the e was missing. That happened with debian-13-xfce template.
Not sure why and if known?
Can you post a screenshot?
Just a little more information would be useful - what were you trying to
do, where were you running salt, what did your state file look like.
I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.
The plan was to learn how to deal with salt for the first time by setting up split-ssh. For unknown reason the ssh AppVM was always denied access to the ssh-vault via these little Qubes notifications. At that time i didn’t think of taking photos @rustybird since that cannot be screenshot.
@unman i gave up trying to figure out why i was getting denied and moved on and later on reminded that that Qub: is a weird thing i should post about and i also never named any template or appVM Qub but it kept popping up every time i was denied access. It’s a fresh 4.3 install and sorry i do not have more info at the time.
–
You guys think it might make sense to have something like salt scripts shipped and ready in dom0 that guide one through and help setting up various salt stuff with clear warning their be dragons if you touch this without backups?
These scripts could make the upgrading to newer templates smoother even though i understand the complications with Qubes security model not to open up new ways of malicious code to find it’s way into precious, just spit balling here, have a nice day.
Sounds like a policy issue.
In my world view a sign of success in regards of that the salt tinkering was successful.
Have a read at these docs.
I would encourage you to maintain a file where you keep you custom changes.
I fiddled with the police way to many times until i gave up and went back to my manual setup of split-ssh and adding it to newer templates.
Sounds depressing …
It’s is technology. If it is not working, destroy it.
How about you share a screenshot of the error message you get?