Creating importer: Failed to invoke skopeo proxy method OpenImage: remote error: cryptographic signature verification failed: invalid signature when validating ASN.1 encoded signature ___
I was banging my head against my keyboard for an hour thinking that I broke my system until I saw this.
Wow! Another reason to keep supporting uBlue. That’s how leadership is supposed to be. He did something wrong and instantly apologizes deeply and gives us a simple solution. I’m very proud and my trust is strengthened, thanks!
I would like to share the fixing script here, but don’t feel comfortable anyone executing something I copy-pasted because of security. Go and read the letter yourself, it will take literally one minute.
Yeah. Makes me love jorge and team maintaining ublue even more.
If you dont want to miss future announcements:
- With an Account on the forums you can get notifications if you turn them on for the “Announcement“ tag
- You can add https://universal-blue.discourse.group/tag/announcements.rss to your RSS reader
Thanks! Really helpful!
This is a good tip but is there not a more reliable way for the issue to be communicated to users? I suspect many people are going to be stuck on the pre-error version of Bluefin, unaware that updating is broken.
It has been asked on the forum. Idk if they will consider implementing some type of notification for critical issues on the OS itself. Edit: they are working on a solution
I don’t blame the guy for being human and it’s free software etc, but this is reality bad optics for immutable distros. If my nephew and grandma are going to need manual interventions like this one, then might as well use a less restrictive system. The promise of seamless and easy updates are the main draw for me.
It would be much appreciated if UniBlue made the update process more robust and more resistant to such mistakes.
(also curl piped into sudo bash is way more common than it should be)
They messed up the signing on the server side.
They are using all non-stable technology. The Github action and cosign may be normal, but Fedora doesnt release their container images (even though they are the ones that uBlue consumes).
The updating mechanism is fine, this is a security measurement. If the signing failed, it shouldnt update as this could mean malware.
To be fair, the blog post details how they plan on avoiding such an issue in the future
The fix is dead simple, no worries.
Bluefin-DX is great! I’m still figuring out how everything works - there are a lot of tools included that are new to me, despite being a cloud-oriented developer.
It’s a very different way to use Linux, from how the OS is constructed, to the container-first nature of the default applications and intended workflow. But I’m really enjoying learning how to use it.
there are a lot of tools included that are new to me, despite being a cloud-oriented developer.
Interesting! What tools do you commonly use?
At work, we’re a Windows shop. So mostly Docker (desktop) via WSL2. But it depends on the project. Sometimes it’s just NodeJS in Windows itself!
At home, mostly tools like nvm and Python venvs to handle multiple projects with potentially overlapping/problematic dependencies that I want to isolate from the base system.
Either way, initial testing happens locally with Docker compose, sometimes minikube depending on the project.
With Bluefin-DX it’s a lot of the same concepts but the included tools get you there a different, and honestly easier and more convenient way. But I have learn how to use those tools!
Thanks for spreading the word!
I installed Bazzite on a Dell latitude just to check it out… The son of a bitch booted once, let me install updates then never booted again.
Finally got updated 😄👍
Logout still hangs on both X and Wayland sessions (KDE) 😫👎
I need to send this to myself in the AM as a reminder
Lol
