skypeforlinux - Failed on BLAKE2B verification

hackmack · n00b Joined: 17 Apr 2023 Posts: 4

Hello,

is there a problem with the black2b algorithm? Does anyone else got this problem? Any hints for investigation?

I don't assume that NSA has changed the bin on the repo server

emerge log:

>>> Downloading 'https://repo.skype.com/rpm/stable/skypeforlinux_8.96.0.408-1.x86_64.rpm'
--2023-04-17 14:22:30-- https://repo.skype.com/rpm/stable/skypeforlinux_8.96.0.408-1.x86_64.rpm
Resolving repo.skype.com... 2.19.244.163, 2a02:26f0:e600:584::1263, 2a02:26f0:e600:58a::1263
Connecting to repo.skype.com|2.19.244.163|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 124598879 (119M) [application/x-redhat-package-manager]
Saving to: ‘/var/cache/distfiles/skypeforlinux_8.96.0.408-1.x86_64.rpm.__download__’

/var/cache/distfile 100%[===================>] 118,83M 6,00MB/s in 20s

2023-04-17 14:22:51 (5,83 MB/s) - ‘/var/cache/distfiles/skypeforlinux_8.96.0.408-1.x86_64.rpm.__download__’ saved [124598879/124598879]

!!! Fetched file: skypeforlinux_8.96.0.408-1.x86_64.rpm VERIFY FAILED!
!!! Reason: Failed on BLAKE2B verification
!!! Got: 5228dcf5ce264cdcb0c98b53113ddbcb013d328f615fe0641a84741de6ce26e698f4b6fce2c8d4aa0a3e60d9cc840005f84a7978b455f3945fcfa9b3bae84540
!!! Expected: 22dabd44f7465a777d15ddfd9b234df331e381c84dda60b44c6f6681c455cd7c1a8244b7b7b521d8ca43938d5ba68378232c983b2aae4efe1561927060009192
Refetching... File renamed to '/var/cache/distfiles/skypeforlinux_8.96.0.408-1.x86_64.rpm._checksum_failure_.aeyx1sv9'

!!! Couldn't download 'skypeforlinux_8.96.0.408-1.x86_64.rpm'. Aborting.
* Fetch failed for 'net-im/skypeforlinux-8.96.0.408', Log file:
* '/var/tmp/portage/net-im/skypeforlinux-8.96.0.408/temp/build.log'

my Kernel blake is enabled:

│ Symbol: CRYPTO_BLAKE2S_X86 [=y] │
│ Type : bool │
│ Defined at arch/x86/crypto/Kconfig:354 │
│ Prompt: Hash functions: BLAKE2s (SSSE3/AVX-512) │
│ Depends on: CRYPTO [=y] && !KMSAN [=n] && X86 [=y] && 64BIT [=y] │
│ Location: │
│ -> Cryptographic API (CRYPTO [=y]) │
│ -> Accelerated Cryptographic Algorithms for CPU (x86) │
│ (4) -> Hash functions: BLAKE2s (SSSE3/AVX-512) (CRYPTO_BLAKE2S_X86 [=y]) │
│ Selects: CRYPTO_LIB_BLAKE2S_GENERIC [=y] && CRYPTO_ARCH_HAVE_LIB_BLAKE2S [=y] │
│ Selected by [n]: │
│ - WIREGUARD [=n] && NETDEVICES [=y] && NET_CORE [=y] && NET [=y] && INET [=y] && (IPV6 [=y] || !IPV6 [=y]) && !KMSAN [=n] && X86 [=y] && 64BIT [=y] │
│ │
│ │
│ Symbol: CRYPTO_LIB_BLAKE2S_GENERIC [=y] │
│ Type : bool │
│ Defined at lib/crypto/Kconfig:30 │
│ Selected by [y]: │
│ - CRYPTO_BLAKE2S_X86 [=y] && CRYPTO [=y] && !KMSAN [=n] && X86 [=y] && 64BIT [=y]

fedeliallalinea · Posted: Mon Apr 17, 2023 1:24 pm Post subject:

It's a know bug.
_________________
Questions are guaranteed in life; Answers aren't.

rab0171610 · Apprentice Joined: 24 Dec 2022 Posts: 298

I had the same error just now.
It seems like a corrupted or incorrect checksum in the Manifest. What I did that worked (as root):

fedeliallalinea · Posted: Mon Apr 17, 2023 1:38 pm Post subject:

Change the manifest without a check its not a good idea.
A manifest that has a different checksum can mean, if it is not a developer error, that the code base has been modified.
This can sometimes happen and is nothing serious, but it could also have been compromise.
I remember a few years ago with the transmission program for OSX.
_________________
Questions are guaranteed in life; Answers aren't.

rab0171610 · Apprentice Joined: 24 Dec 2022 Posts: 298

fedeliallalinea · Posted: Mon Apr 17, 2023 2:00 pm Post subject:

hackmack · n00b Joined: 17 Apr 2023 Posts: 4