I am not able to install balena-etcher in OpenSuse Tembleweed via terminal or via yast.
The error message appears that the header of the application is not signed, see image below.
The problem occurs in any version of balena-etcher
Error: INVALID:balena-etcher-1.18.4-1.x86_64 (file-60781681): Signature verification failed [6-The file is not signed]
Header SHA256 digest: OK
Header SHA1 digest: OK
Payload SHA256 digest: OK
MD5 digestion: OK
The packet header is not signed!
Note: On the VM it installed normally. On HD this application does not install.
I tested the last 5 versions of balena-etcher and I think it must be another problem.
As you did not follow the instructions how to install it correctly with the repo, you didnāt import the signing key. By following the procedure, you will add the repo, import the signing key and it installs just fine.
leap@leaptest:~/Downloads> curl -1sLf \
> 'https://dl.cloudsmith.io/public/balena/etcher/setup.rpm.sh' \
> | sudo -E bash
Executing the setup script for the 'balena/etcher' repository ...
OK: Checking for required executable 'curl' ...
OK: Checking for required executable 'rpm' ...
OK: Detecting your OS distribution and release using system methods ...
^^^^: ... Detected/provided for your OS/distribution, version and architecture:
>>>>:
>>>>: ... distro=opensuse-leap version=15.4 codename=15.4 arch=x86_64
>>>>:
OK: Importing 'balena/etcher' repository GPG keys into rpm ...
OK: Checking for available package manager (DNF/Microdnf/YUM/Zypper) ...
^^^^: ... Detected package manager as 'zypper'
OK: Checking if upstream install config is OK ...
OK: Fetching 'balena/etcher' repository configuration ...
OK: Installing 'balena/etcher' repository via zypper ...
OK: Updating the zypper cache to fetch the new repository metadata ...
OK: The repository has been installed successfully - You're ready to rock!
leap@leaptest:~/Downloads> sudo zypper up
Metadaten von Repository 'balena-etcher-noarch' abrufen .............................................................................................................................................................................................................[fertig]
Cache fĆ¼r Repository 'balena-etcher-noarch' erzeugen ................................................................................................................................................................................................................[fertig]
Repository-Daten werden geladen...
Installierte Pakete werden gelesen...
Die folgenden 10 Paketaktualisierungen werden NICHT installiert:
ffmpeg-4 libavcodec58_134 libavdevice58_13 libavfilter7_110 libavformat58_76 libavresample4_0 libavutil56_70 libpostproc55_9 libswresample3_9 libswscale5_9
Keine auszufĆ¼hrenden Aktionen.
leap@leaptest:~/Downloads> sudo zypper install balena-etcher
Repository-Daten werden geladen...
Installierte Pakete werden gelesen...
PaketabhƤngigkeiten werden aufgelƶst...
Das folgende NEUE Paket wird installiert:
balena-etcher
1 neues Paket zu installieren.
GesamtgrƶĆe des Downloads: 64,5 MiB. Bereits im Cache gespeichert: 0 B. Nach der Operation werden zusƤtzlich 215,7 MiB belegt.
Fortfahren? [j/n/v/...? zeigt alle Optionen] (j): j
Paket balena-etcher-1.14.3-1.x86_64 abrufen (1/1), 64,5 MiB (215,7 MiB entpackt)
Abrufen: balena-etcher-1.14.3.x86_64.rpm ................................................................................................................................................................................................................[fertig (5,9 MiB/s)]
ĆberprĆ¼fung auf Dateikonflikte lƤuft: ...............................................................................................................................................................................................................................[fertig]
(1/1) Installieren: balena-etcher-1.14.3-1.x86_64 ...................................................................................................................................................................................................................[fertig]
leap@leaptest:~/Downloads>
No. You need an additional signing key to verify that the package is untinkerd. If the package would ship the signing key with it, the complete sense behind checking the validity of a package would be broken. That means a malicius (tinkered) package would ship the signing key and would install without problemsā¦dāoh!
OK: Checking for required executable ācurlā ā¦
OK: Checking for required executable ārpmā ā¦
OK: Detecting your OS distribution and release using system methods ā¦
^^^^: ā¦ Detected/provided for your OS/distribution, version and architecture:
:
: ā¦ distro=opensuse-tumbleweed version=20230313 codename= arch=x86_64
:
OK: Importing ābalena/etcherā repository GPG keys into rpm ā¦
OK: Checking for available package manager (DNF/Microdnf/YUM/Zypper) ā¦
^^^^: ā¦ Detected package manager as āzypperā
NOPE: Checking if upstream install config is OK ā¦
^^^^: ā¦ Failed to fetch configuration for your OS distribution release/version.
:
: It looks like we donāt currently support your distribution release and
: version. This is something that we can fix by adding it to our list of
: supported versions (see contact us below), or you can manually override
: the values below to an equivalent distribution that we do support:
:
: ā¦ distro=opensuse-tumbleweed version=20230313 codename= arch=x86_64
:
: You can force this script to use a particular value by specifying distro,
: version, or codename via environment variable. E.g., to specify a distro
: such as SUSE Linux Enterprise Server 12, use the following:
:
: | distro=sles version=12.1 codename= sudo -E bash
:
!!!: Oh no, your setup failed! ā¦ But we might be able to help.
!!!:
!!!: You can contact balena for further assistance.
!!!:
!!!: URL: https://github.com/balena-io/etcher
!!!:
!!!: Last 20 log lines from .csm_setup_85Su5f5dv (might not be errors, nor even relevant):
!!!:
edson@localhost:~> sudo zypper up
Loading data from repositoryā¦
Reading installed packagesā¦
The following package update will NOT be installed:
librist4
Nothing to do.
edson@localhost:~> sudo zypper install balena-etcher
Loading data from repositoryā¦
Reading installed packagesā¦
ābalena-etcherā not found in package names. Trying to locate in resources.
No supplier of ābalena-etcherā found.
Resolving package dependenciesā¦
Nothing to do.
edson@localhost:~> sudo zypper install balena-etcher-electron
Loading data from repositoryā¦
Reading installed packagesā¦
ābalena-etcher-electronā not found in package names. Trying to locate in resources.
No providers of ābalena-etcher-electronā found.
Resolving package dependenciesā¦
Nothing to do.
edson@localhost:~>
I tried to install manually and also the same error occurs:
sudo zypper balena-etcher-1.18.5.x86_64.rpm
[sudo] password for root:
Unknown command ābalena-etcher-1.18.5.x86_64.rpmā
Type āzypper helpā to display a list of global options and commands.
If ābalena-etcher-1.18.5.x86_64.rpmā is not a typo, it is probably not a built-in command, but provided as a subcommand or plug-in (see āzypper help subcommandā).
In this case, a specific package that provides the subcommand needs to be installed first. These packages are often called āzypper-balena-etcher-1.18.5.x86_64.rpmā or āzypper-balena-etcher-1.18.5.x86_64.rpm-pluginā.
edson@localhost:~/Downloads> sudo zypper in balena-etcher-1.18.5.x86_64.rpm
Loading data from repositoryā¦
Reading installed packagesā¦
Resolving package dependenciesā¦
The following NEW package will be installed:
balena-etcher
1 new package to be installed.
Total download size: 67.2 MiB. Already cached: 0 B. After the operation, 229.2
Additional MiB will be used.
Continue? y/n/v/ā¦? displays all options: s
Downloading: balena-etcher-1.18.5-1.x86_64 (Single RPM File Cache)
(1/1), 67.2 MiB
balena-etcher-1.18.5.x86_64.rpm:
The packet header is not signed!
balena-etcher-1.18.5-1.x86_64 (Simple RPM file cache): Signature verification failed [6-The file is not signed]
Cancel, retry or skip? [c/r/i] (c):
OK: Checking for required executable ācurlā ā¦
OK: Checking for required executable ārpmā ā¦
OK: Detecting your OS distribution and release using system methods ā¦
^^^^: ā¦ Detected/provided for your OS/distribution, version and architecture:
:
: ā¦ distro=opensuse-tumbleweed version=20230313 codename=tumbleweed arch=x86_64
:
OK: Importing ābalena/etcherā GPG repository keys into rpm ā¦
OK: Checking for available package manager (DNF/Microdnf/YUM/Zypper) ā¦
^^^^: ā¦ Detected package manager as āzypperā
OK: Checking if upstream install config is OK ā¦
OK: Fetching ābalena/etcherā repository configuration ā¦
OK: Installing ābalena/etcherā repository via zypper ā¦
OK: Updating the zypper cache to fetch the new repository metadata ā¦
OK: The repository has been installed successfully - Youāre ready to rock!
edson@localhost:~> sudo zypper up
Downloading the ābalena-etcher-noarchā repository metadata ā¦[completed]
Building the ābalena-etcher-noarchā repository cache ā¦[completed]
Loading repository dataā¦
Reading the installed packagesā¦
The following package update will NOT be installed:
librist4
Nothing to do.
edson@localhost:~> sudo zypper install balena-etcher
Loading repository dataā¦
Reading installed packagesā¦
Resolving package dependenciesā¦
The following NEW package will be installedā¦:
balena-etcher
1 new package to be installed.
Total download size: 64.5 MiB. Already cached: 0 B. After operation, additional 215.7
MiB will be used.
Continue? [s/n/v/ā¦? display all options] (s): s
Downloading: balena-etcher-1.14.3-1.x86_64 (balena-etcher) (1/1), 64.5 MiB
Downloading: balena-etcher-1.14.3.x86_64.rpm ā¦[completed (9.2 MiB/s)]
Checking for file conflict: ā¦[completed]
(1/1) Installing: balena-etcher-1.14.3-1.x86_64 ā¦[completed]
edson@localhost:~>
I was only able to post the answer today because Iām a newbie and the forum system has blocked me for too many recent posts on yesterdayās date
balena-etcher-1.14.3 is from January 2023. Version 1.18.4 was released only 2 weeks ago on github. All versions in between are only pre-releases. As the developers use an external cloudservice to host their build-repository it takes some time until the repo catches up. You need to ask the developers when this will happenā¦
Btw is there a reason why you need balener-etcher and donāt use openSUSE standard tools like imagewriter which is available in the standard OSS repo?
Because Iām a recent user new to OpenSuse, I didnāt know about the āimagewriterā tool and, every time I needed to burn an ISO, Balena-etcher never failed me.
Iām going to test your suggestion and see if I adapt with the tool that is already installed and seems very simple and functional to use.
Yes! And for this reason I removed his repositories and manually installed the latest version that is already available in the installation, the application icons in the menu: (show applications).