[opensuse] two upgraded 11.3 system - but one reports wrong digest??
I have two newly updated 11.3 systems, they should be virtually the same. However, the most recent one, updated this morning, has begun reporting : Wrong Digest The expected checksum of ile /var/cache/zypp/raw/openSUSE-11.3_11.3-1.82lmjU0A/suse/setup/descr/dvd-11.3-22.1.i586.pat.gz is dfa703cc40751d8237205ef666c88254b8213c78, but the current checksum is . This means that the file has been changed by accident or by an attacker since the repository creator signed it. Using it is a big risk for the integrity and security of your system. I have just now removed all repositories and attempted to add: download.opensuse.org/distrobution/11.3/repo/oss And got the message above. What does it mean? -- Per Jessen, Zürich (21.6°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 20/07/10 11:56, Per Jessen wrote:
I have two newly updated 11.3 systems, they should be virtually the same. However, the most recent one, updated this morning, has begun reporting :
Wrong Digest The expected checksum of ile /var/cache/zypp/raw/openSUSE-11.3_11.3-1.82lmjU0A/suse/setup/descr/dvd-11.3-22.1.i586.pat.gz is dfa703cc40751d8237205ef666c88254b8213c78, but the current checksum is . This means that the file has been changed by accident or by an attacker since the repository creator signed it. Using it is a big risk for the integrity and security of your system.
I have just now removed all repositories and attempted to add:
download.opensuse.org/distrobution/11.3/repo/oss
distribution or really "distrobution"? Greetings pistazienfresser -- - openSUSE 11.2 with GNOME 2.28.2 (or KDE 4.3.5) and Kernel Linux 2.6.31.12-0.2-default (or pae, Ubuntu 10.4 LTS 'lucid' 2.6.33-22-genetic, MS Win XP) - Samsung X20 (SX20S) with Pentium M 740 (1730 MHz), Intel graphic 915GM, 1400x1050 - openSUSE profile: https://users.opensuse.org/show/pistazienfresser -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
pistazienfresser wrote:
On 20/07/10 11:56, Per Jessen wrote:
I have two newly updated 11.3 systems, they should be virtually the same. However, the most recent one, updated this morning, has begun reporting :
Wrong Digest The expected checksum of ile /var/cache/zypp/raw/openSUSE-11.3_11.3-1.82lmjU0A/suse/setup/descr/dvd-11.3-22.1.i586.pat.gz is dfa703cc40751d8237205ef666c88254b8213c78, but the current checksum is . This means that the file has been changed by accident or by an attacker since the repository creator signed it. Using it is a big risk for the integrity and security of your system.
I have just now removed all repositories and attempted to add:
download.opensuse.org/distrobution/11.3/repo/oss
distribution or really "distrobution"?
Haha, no I got it right in YaST - distribution. -- Per Jessen, Zürich (24.0°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Per Jessen wrote:
I have two newly updated 11.3 systems, they should be virtually the same. However, the most recent one, updated this morning, has begun reporting :
Wrong Digest The expected checksum of ile /var/cache/zypp/raw/openSUSE-11.3_11.3-1.82lmjU0A/suse/setup/descr/dvd-11.3-22.1.i586.pat.gz is dfa703cc40751d8237205ef666c88254b8213c78, but the current checksum is .
Does anyone have a suggestion (apart from reinstalling) on how to get this working again? I have removed all repositories, and try to add download.opensuse.org/distribution/11.3/repo/oss When I get the error above. What does it mean? -- Per Jessen, Zürich (23.9°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, Jul 21, 2010 at 09:47:03AM +0200, Per Jessen wrote:
Per Jessen wrote:
I have two newly updated 11.3 systems, they should be virtually the same. However, the most recent one, updated this morning, has begun reporting :
Wrong Digest The expected checksum of ile /var/cache/zypp/raw/openSUSE-11.3_11.3-1.82lmjU0A/suse/setup/descr/dvd-11.3-22.1.i586.pat.gz is dfa703cc40751d8237205ef666c88254b8213c78, but the current checksum is .
Does anyone have a suggestion (apart from reinstalling) on how to get this working again? I have removed all repositories, and try to add
download.opensuse.org/distribution/11.3/repo/oss
When I get the error above. What does it mean?
Did you rm the file above and refreshed again? any error in the zypper.log file regarding it? Ciao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Marcus Meissner wrote:
On Wed, Jul 21, 2010 at 09:47:03AM +0200, Per Jessen wrote:
Per Jessen wrote:
I have two newly updated 11.3 systems, they should be virtually the same. However, the most recent one, updated this morning, has begun reporting :
Wrong Digest The expected checksum of ile
/var/cache/zypp/raw/openSUSE-11.3_11.3-1.82lmjU0A/suse/setup/descr/dvd-11.3-22.1.i586.pat.gz
is dfa703cc40751d8237205ef666c88254b8213c78, but the current checksum is .
Does anyone have a suggestion (apart from reinstalling) on how to get this working again? I have removed all repositories, and try to add
download.opensuse.org/distribution/11.3/repo/oss
When I get the error above. What does it mean?
Did you rm the file above and refreshed again?
No, but it happens to lots of files: /var/tmp/TmpDir.WfzKR4/license.tar.gz /var/cache/zypp/raw/openSUSE-11.3_11.3-1.82gGVVqh/suse/setup/descr/dvd-11.3-22.1.i586.pat.gz /var/cache/zypp/raw/openSUSE-11.3_11.3-1.82gGVVqh/suse/setup/descr/ftp-11.3-22.1.i586.pat.gz /var/cache/zypp/raw/openSUSE-11.3_11.3-1.82gGVVqh/suse/setup/descr/non_oss-11.3-22.1.i586.pat.gz /var/cache/zypp/raw/openSUSE-11.3_11.3-1.82gGVVqh/suse/setup/descr/packages.DU.gz /var/cache/zypp/raw/openSUSE-11.3_11.3-1.82gGVVqh/suse/setup/descr/packages.en.gz /var/cache/zypp/raw/openSUSE-11.3_11.3-1.82gGVVqh/suse/setup/descr/packages.gz /var/cache/zypp/raw/openSUSE-11.3_11.3-1.82gGVVqh/suse/setup/descr/patterns /var/cache/zypp/raw/openSUSE-11.3_11.3-1.82gGVVqh/license.tar.gz /var/cache/zypp/raw/openSUSE-11.3_11.3-1.82gGVVqh/gpg-pubkey-0dfb3188-41ed929b.asc /var/cache/zypp/raw/openSUSE-11.3_11.3-1.82gGVVqh/gpg-pubkey-307e3d54-4be01a65.asc /var/cache/zypp/raw/openSUSE-11.3_11.3-1.82GH6lUz/suse/setup/descr/dvd-11.3-22.1.i586.pat.gz [lots more]
any error in the zypper.log file regarding it?
Nope, nothing to be seen. -- Per Jessen, Zürich (24.5°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 07/20/2010 04:56 AM, Per Jessen wrote:
Wrong Digest The expected checksum of ile /var/cache/zypp/raw/openSUSE-11.3_11.3-1.82lmjU0A/suse/setup/descr/dvd-11.3-22.1.i586.pat.gz is dfa703cc40751d8237205ef666c88254b8213c78, but the current checksum is . This means that the file has been changed by accident or by an attacker since the repository creator signed it. Using it is a big risk for the integrity and security of your system.
Per, this is part of the checksum fiasco that got scattered all across the opensuse redirector system. I have 50-100 packages do that to me and worst of all, I have the kernel and mkinitrd report as corrupt. You can usually just answer: Use anyway? -> No Retry? -> Yes and yast will pull a package from another mirror that is clean. However, on the kernel and mkinitrd, I downloaded them 7 times -- all corrupt, so finally I gave up and decided to just see what would happen when upgrading without a kernel or mkinitrd?? Worked out fine. The install completed and then booted into the old 2.6.32 kernel from 11.2 and I was able to install the new kernel and mkinitrd that I had manually downloaded. It was creepy to see a corrupt kernel during the install, but with an 'Upgrade' the fallback to the existing kernel saved the day. ... But just think about all those poor S.O.B.'s doing 'installs'..... -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
David C. Rankin wrote:
On 07/20/2010 04:56 AM, Per Jessen wrote:
Wrong Digest The expected checksum of ile /var/cache/zypp/raw/openSUSE-11.3_11.3-1.82lmjU0A/suse/setup/descr/dvd-11.3-22.1.i586.pat.gz is dfa703cc40751d8237205ef666c88254b8213c78, but the current checksum is . This means that the file has been changed by accident or by an attacker since the repository creator signed it. Using it is a big risk for the integrity and security of your system.
Per, this is part of the checksum fiasco that got scattered all across the opensuse redirector system. I have 50-100 packages do that to me and worst of all, I have the kernel and mkinitrd report as corrupt. You can usually just answer:
Use anyway? -> No Retry? -> Yes
and yast will pull a package from another mirror that is clean.
Hmm, I don't get no option to retry. What I really don't understand is why it works on one system, but not on another. -- Per Jessen, Zürich (30.2°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 07/21/2010 09:32 AM, Per Jessen wrote:
Hmm, I don't get no option to retry.
What I really don't understand is why it works on one system, but not on another.
I suspect it is just the roll-of-the-dice on which mirror you are pulling packages from. One box is just the lucky one, and the other -- the black sheep. There isn't anything a box can do. The problem is with the actual digest/checksum mismatch caused by whatever/whoever screwed up the 11.3 mirror system by letting a bunch of botched packages go. If you get a good package it installs, if you get one with a problem --> you get the error. The 'Retry?' is on the second dialog. After you click, 'Use Anyway?: No', then you fall back to the dialog with the 'Abort, Ignore, Retry' options. Try and figure out which mirror is giving you good packages, then if you should have to stop/re-start the install, you can at least use a good mirror next time :p -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
David C. Rankin wrote:
On 07/21/2010 09:32 AM, Per Jessen wrote:
Hmm, I don't get no option to retry.
What I really don't understand is why it works on one system, but not on another.
I suspect it is just the roll-of-the-dice on which mirror you are pulling packages from. One box is just the lucky one, and the other -- the black sheep.
There isn't anything a box can do. The problem is with the actual digest/checksum mismatch caused by whatever/whoever screwed up the 11.3 mirror system by letting a bunch of botched packages go. If you get a good package it installs, if you get one with a problem --> you get the error.
The 'Retry?' is on the second dialog. After you click, 'Use Anyway?: No', then you fall back to the dialog with the 'Abort, Ignore, Retry' options.
Uh, no - when I say 'no', I keep getting lots of other files with checksum problems. If I say 'no' on the second window (there is no retry option), yast reverts to the list of repositories.
Try and figure out which mirror is giving you good packages, then if you should have to stop/re-start the install, you can at least use a good mirror next time :p
The installations are both complete - I ran zypper dup (to 11.3) a couple of days ago. Then I was doing some cleanups, and suddenly I started getting these errors. Isn't there a way for me to clear everything out and start again - without having to reinstall? -- Per Jessen, Zürich (30.9°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Per Jessen wrote:
David C. Rankin wrote:
On 07/21/2010 09:32 AM, Per Jessen wrote:
Hmm, I don't get no option to retry.
What I really don't understand is why it works on one system, but not on another.
I suspect it is just the roll-of-the-dice on which mirror you are pulling packages from. One box is just the lucky one, and the other -- the black sheep.
There isn't anything a box can do. The problem is with the actual digest/checksum mismatch caused by whatever/whoever screwed up the 11.3 mirror system by letting a bunch of botched packages go. If you get a good package it installs, if you get one with a problem --> you get the error.
The 'Retry?' is on the second dialog. After you click, 'Use Anyway?: No', then you fall back to the dialog with the 'Abort, Ignore, Retry' options.
Uh, no - when I say 'no', I keep getting lots of other files with checksum problems. If I say 'no' on the second window (there is no retry option), yast reverts to the list of repositories.
Try and figure out which mirror is giving you good packages, then if you should have to stop/re-start the install, you can at least use a good mirror next time :p
The installations are both complete - I ran zypper dup (to 11.3) a couple of days ago. Then I was doing some cleanups, and suddenly I started getting these errors. Isn't there a way for me to clear everything out and start again - without having to reinstall?
It's not the mirror system that is causing this - I've just tried using mirror.switch.ch on both systems; one A it works, on B it doesn't (Wrong digest). Back to my earlier question - isn't there a way for me to clear everything out and start again - without having to reinstall? -- Per Jessen, Zürich (31.1°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Per Jessen wrote:
Per Jessen wrote:
It's not the mirror system that is causing this -
I've just tried using mirror.switch.ch on both systems; one A it works, on B it doesn't (Wrong digest).
Back to my earlier question - isn't there a way for me to clear everything out and start again - without having to reinstall?
What I find really odd is that of the two checksums that yast complains about, one is _empty_: Wrong Digest: The expected checksum of file /var/tmp/TmpDir.3dKqrq/license.tar.gz is f9b8e7e5c6af23ab500a0c907f2518bc236c89be, but the current checksum is . -- Per Jessen, Zürich (18.0°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 07/23/2010 06:25 AM, Per Jessen wrote:
Per Jessen wrote:
Per Jessen wrote:
It's not the mirror system that is causing this -
I've just tried using mirror.switch.ch on both systems; one A it works, on B it doesn't (Wrong digest).
Back to my earlier question - isn't there a way for me to clear everything out and start again - without having to reinstall?
What I find really odd is that of the two checksums that yast complains about, one is _empty_:
Wrong Digest: The expected checksum of file /var/tmp/TmpDir.3dKqrq/license.tar.gz is f9b8e7e5c6af23ab500a0c907f2518bc236c89be, but the current checksum is .
That is just strange. I don't suppose that you can just move whatever digest/checksum file from goodbox->bad box can you? I don't know the answer, but what the devs need to disclose is if the packages that failed the digest check are (1) good but with a bad digest; or (2) bad digest = bad package, expect unpredictable results. Earlier Context:
The 'Retry?' is on the second dialog. After you click, 'Use Anyway?:
No', then you fall back to the dialog with the 'Abort, Ignore, Retry' options.
Uh, no - when I say 'no', I keep getting lots of other files with checksum problems. If I say 'no' on the second window (there is no retry option), yast reverts to the list of repositories. I figured out what the disconnect in our thinking was, I was talking about the wrong digest/checksum errors received 'during' install -- if I understand now, you are talking about after install. If so, the only thing I could guess at is to try and identify the packages with a bad checksum stepping though the installed rpms with something like: for i in $(rpm -qa); do rpm -qi $i >/dev/null; done or rpm -qa $(rpm -qa) >/dev/null which ever one of those will work. I know I can catch bad packages with 'repoview' which must do something like that to get the information to populate the html pages. Worth a try... -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
David C. Rankin wrote:
On 07/23/2010 06:25 AM, Per Jessen wrote:
Per Jessen wrote:
What I find really odd is that of the two checksums that yast complains about, one is _empty_:
Wrong Digest: The expected checksum of file /var/tmp/TmpDir.3dKqrq/license.tar.gz is f9b8e7e5c6af23ab500a0c907f2518bc236c89be, but the current checksum is .
That is just strange. I don't suppose that you can just move whatever digest/checksum file from goodbox->bad box can you? I don't know the answer, but what the devs need to disclose is if the packages that failed the digest check are (1) good but with a bad digest; or (2) bad digest = bad package, expect unpredictable results.
Hi David I've cleared out all repositories on the bad box, so I had expected to get a clean start, but it's not working. I don't think there is a checksum file anywhere. I completely appreciate "bad digest" = "bad package", no question about that, but "no digest" = "bad package" is different. I just don't understand why I get this "no digest" situation. You wouldn't happen to know how the digests are built (locally) ?
Earlier Context:
The 'Retry?' is on the second dialog. After you click, 'Use Anyway?: No', then you fall back to the dialog with the 'Abort, Ignore, Retry' options.
Uh, no - when I say 'no', I keep getting lots of other files with checksum problems. If I say 'no' on the second window (there is no retry option), yast reverts to the list of repositories.
I figured out what the disconnect in our thinking was, I was talking about the wrong digest/checksum errors received 'during' install -- if I understand now, you are talking about after install.
Yup. I basically have a new system that I zypper dup'ed to 11.3 - then I added my own customizations (snmp, hp proliant software, ntp etc), and somehow ended up in this weird situation.
If so, the only thing I could guess at is to try and identify the packages with a bad checksum stepping though the installed rpms with something like:
for i in $(rpm -qa); do rpm -qi $i >/dev/null; done
I'll try that, but isn't it pretty weird that I also get this problem on license.tar.gz ?? thanks for taking an interest :-) /Per -- Per Jessen, Zürich (14.1°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Per Jessen wrote:
Hi David
I've cleared out all repositories on the bad box, so I had expected to get a clean start, but it's not working.
And this afternoon I did a clean install of 11.3 which obviously worked without a single hitch (well, the usual ones only). My situation here was clearly unique, so maybe something got screwed up when I zypper dup'ed from 11.2RC1 to 11.3GM, who knows. Thanks David, having a sounding board is always helpful! -- Per Jessen, Zürich (16.1°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (4)
-
David C. Rankin -
Marcus Meissner -
Per Jessen -
pistazienfresser