opensuse15.5 without errors installed, but it ends in a disaster

Manfred Neubauer

25 Jun 2023 25 Jun '23

18:02

Hallo Peter, please excuse me. It lasts some time to overcome my internal resistence to send an email to Comunity. First of all during installation I got on screen an information: 'violation of signature'. I installed opensuse.15.5 dispite a warning. With version 15.3 everything was perfect. I could create a virtuell space. Pushing buttons 'escape and start' I started an other Linux from an USB-stick. The more I tried to realise to start my USB stick, the more I drifted into a disaster. In the meantime announsments poppt up: 'security Violation'. Booting an other version of Suse, I succided to install 'Tumpleweed'. I was still in hope to start from zero my USB-stick. Never the less in Leap15.5 there was something configured with 'ssh'. The part'settings' -----> Remote log in' was the reason why everyting went wrong. there was an encrypted connection all the time open to SuseLinux. But I got no information to resolve encryotion. Tumpleweed was installed anew downloading 500 packages from 1200, after 500 packages all the screen became red. I could not overcome the ssh encryption. Finally I have send my ZenBook to Asus to repair it. Thats the whole story. Its clear that a ' KI ' was responsable for the situation. kindly Dr. Neubauer PS: My user name has changed from ' eller ' to 'kro'

Show replies by date

Carlos E. R.

25 Jun 25 Jun

18:13

On 2023-06-25 20:02, Manfred Neubauer wrote:

...

Hallo Peter, please excuse me. It lasts some time to overcome my internal resistence to send an email to Comunity. First of all during installation I got on screen an information: 'violation of signature'. I installed opensuse.15.5 dispite a warning. With version 15.3 everything was perfect. I could create a virtuell space. Pushing buttons 'escape and start' I started an other Linux from an USB-stick. The more I tried to realise to start my USB stick, the more I drifted into a disaster. In the meantime announsments poppt up: 'security Violation'. Booting an other version of Suse, I succided to install 'Tumpleweed'. I was still in hope to start from zero my USB-stick. Never the less in Leap15.5 there was something configured with 'ssh'. The part'settings' -----> Remote log in' was the reason why everyting went wrong. there was an encrypted connection all the time open to SuseLinux. But I got no information to resolve encryotion. Tumpleweed was installed anew downloading 500 packages from 1200, after 500 packages all the screen became red. I could not overcome the ssh encryption. Finally I have send my ZenBook to Asus to repair it. Thats the whole story. Its clear that a ' KI ' was responsable for the situation.

kindly Dr. Neubauer

PS: My user name has changed from ' eller ' to 'kro'

Your mail is undecipherable, sorry. I don't understand a word. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)

Axel Braun

26 Jun 26 Jun

08:16

Hello Manfred, Am Sonntag, 25. Juni 2023, 20:02:46 CEST schrieb Manfred Neubauer:

...

please excuse me. It lasts some time to overcome my internal resistence to send an email to Comunity. First of all during installation I got on screen an information: 'violation of signature'. I installed opensuse.15.5 dispite a warning.

you can check the md5 sum of the installation media to verify media is correct. Does that match?

...

With version 15.3 everything was perfect. I could create a virtuell space.

What is a 'virtuell space'? I never came around this so far, so I doubt that this is an openSUSE feature (but I'm happy to learn if it is different)

...

Pushing buttons 'escape and start' I started an other Linux from an USB-stick. The more I tried to realise to start my USB stick, the more I drifted into a disaster.

So what did you really do? - start openSUSE USB-stick? - start any other Linux-based distri from an USB stick?

...

In the meantime announsments poppt up: 'security Violation'. Booting an other version of Suse, I succided to install 'Tumpleweed'.

Tum*b*lewee is an openSUSE product, not SUSE (os Suse). So back to start, you booted your laptop with an USB stick containing a Tumbleweed installation image?

...

I was still in hope to start from zero my USB-stick. Never the less in Leap15.5 there was something configured with 'ssh'. The part'settings' -----> Remote log in' was the reason why everyting went wrong.

I doubt that..... In the installation summary of a standard Leap 15.5 you find that - ssh service is enabled - ssh port is open If you are scared, close them. 'Problem' solved

...

there was an encrypted connection all the time open to SuseLinux.

Please explain what SuseLinux should be

...

But I got no information to resolve encryotion. Tumpleweed was installed anew downloading 500 packages from 1200, after 500 packages all the screen became red.

Its the nature of a rolling release that it has a lot of new software arriving each day. Thats normal. If you feel that the download broke your system, boot into the last known good snapshot and activate it. Problem solved. Next thing could be to analyze the potential issue, collect hardware and log information and create a proper, structured bug report

...

I could not overcome the ssh encryption.

And thats a good thing. ssh w/o encryption would be an open connection. You dont really want that.....

...

Finally I have send my ZenBook to Asus to repair it. Thats the whole story. Its clear that a ' KI ' was responsable for the situation.

I doubt that.

...

kindly Dr. Neubauer

Except spreading conspiracy theories a more structured appraoch to problem solving would be the way to go. Maybe you had a hardware problem with your Zen book, but I doubt it was related to Tumbleweed. Cheers Axel -- Dr. Axel Braun Member of the openSUSE Community

Carlos E. R.

08:56

On 2023-06-26 10:16, Axel Braun wrote:

...

Hello Manfred,

Am Sonntag, 25. Juni 2023, 20:02:46 CEST schrieb Manfred Neubauer:

...
please excuse me. It lasts some time to overcome my internal resistence to send an email to Comunity. First of all during installation I got on screen an information: 'violation of signature'. I installed opensuse.15.5 dispite a warning.

you can check the md5 sum of the installation media to verify media is correct. Does that match?

Only the DVD can be verified on boot. AFAIK, the USB can not be verified, and last time I tried it will say that the verification failed. The correct result would be that the boot option should refuse to do the verification unless it is an actual DVD, it confuses users. I have not tried this in recent years, though. Another possible verification at boot is the UEFI key. An enterprise laptop could refuse to boot the openSUSE media until the proper key is enrolled in the UEFI aka BIOS. It is unclear what Manfred is talking about. ...

...

Except spreading conspiracy theories a more structured appraoch to problem solving would be the way to go. Maybe you had a hardware problem with your Zen book, but I doubt it was related to Tumbleweed.

Indeed. Thank you for your effort at deciphering his post :-) -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)

Axel Braun

09:34

Am 26. Juni 2023 10:56:21 MESZ schrieb "Carlos E. R." :

...

On 2023-06-26 10:16, Axel Braun wrote:

...
Hello Manfred,

Am Sonntag, 25. Juni 2023, 20:02:46 CEST schrieb Manfred Neubauer:

...
please excuse me. It lasts some time to overcome my internal resistence to send an email to Comunity. First of all during installation I got on screen an information: 'violation of signature'. I installed opensuse.15.5 dispite a warning.

you can check the md5 sum of the installation media to verify media is correct. Does that match?

Only the DVD can be verified on boot. AFAIK, the USB can not be verified, and last time I tried it will say that the verification failed. The correct result would be that the boot option should refuse to do the verification unless it is an actual DVD, it confuses users. I have not tried this in recent years, though.

With installation media check I meant the downloaded ISO. For sure the checksum will be different *after* burned to the DVD / USB stick

...

Another possible verification at boot is the UEFI key. An enterprise laptop could refuse to boot the openSUSE media until the proper key is enrolled in the UEFI aka BIOS.

switch secure boot off?

...

It is unclear what Manfred is talking about.

yes

...

...

...
Except spreading conspiracy theories a more structured appraoch to problem solving would be the way to go. Maybe you had a hardware problem with your Zen book, but I doubt it was related to Tumbleweed.

Indeed.

Thank you for your effort at deciphering his post :-)

welcome :-) Viele Grüße Axel -- Diese Nachricht wurde von meinem Android-Tablet mit K-9 Mail gesendet

Robert Webb

28 Jun 28 Jun

11:14

On Mon, 26 Jun 2023 11:34:45 +0200, Axel Braun wrote:

...

Am 26. Juni 2023 10:56:21 MESZ schrieb "Carlos E. R." :

...
Only the DVD can be verified on boot. AFAIK, the USB can not be verified, and last time I tried it will say that the verification failed. The correct result would be that the boot option should refuse to do the verification unless it is an actual DVD, it confuses users. I have not tried this in recent years, though.

With installation media check I meant the downloaded ISO. For sure the checksum will be different *after* burned to the DVD / USB stick

But, if you only read the number of bytes that were written, the size of the ISO file, everything will match, and DVDs and thumbdrives can be verified. This will verify the checksum of a USB stick: #!/bin/bash limited_read() { # usage: limited_read <device> #sudo dd bs=2K count="${1:?}"B if="${2:?}" status=progress sudo pv -B 2K -S -s "${1:?}" "${2:?}" } USBSTICK_DEVICE=/dev/<sdX> ISO="openSUSE-Leap-15.5-Rescue-CD-x86_64-Media.iso" CHKFILE="$ISO".sha256 ISOSIZE="$(stat -c '%s' -- "$ISO")" # Need a separate directory to create a "fake" Iso file for 'sha256sum' mkdir check || exit ln -s -t check -- ../"$CHKFILE" ln -sT -- /dev/stdin check/"$ISO" # sudo umount "$USBSTICK_DEVICE" ( cd check || exit limited_read "$ISOSIZE" "$USBSTICK_DEVICE" \ |sha256sum -c "$CHKFILE" ) rm -r check The problem is, you need to know the size of the original iso file. If you only have a written USB stick, and a checksum file, is there a way to determine the size of the image on the USB stick? -- Robert Webb

310

Age (days ago)

313

Last active (days ago)

List overview

Download

5 comments

5 participants

participants (5)

Axel Braun
Axel Braun
Carlos E. R.
Manfred Neubauer
Robert Webb