TeamViewer update was rejected due to its SHA1 signature

Virtuoso · 2024-09-27T14:31:38+00:00

There was an error rendering this rich post.

Today I ran dnf update on RHEL9 and TeamViewer update was rejected due to its SHA1 signature:

warning: Signature not supported. Hash algorithm SHA1 not available.

I had no installing and updating TeamViewer previously, so my question is whether TV has gone back from SHA2? That would not make sense.

I noticed RHEL9 is formally not supported but CentOS9 is,. CentOS should have the same security algorithm defaults as RHEL9, so I'm confused.

I do not want to lower my system settings and I don't want to disable the keycheck.

Any ideas?

Thanks.

Find more posts tagged with

group sharing

RHEL

Accepted answers

bmdennis

Sadly this has been a problem for at least two years, as TeamViewer has never bothered to get around to moving off SHA1 for their repo keys- see below.

https://community.teamviewer.com/English/discussion/126283/sha1-gpg-key-depreciated-on-rhel-9-derivatives

All comments

bmdennis

Sadly this has been a problem for at least two years, as TeamViewer has never bothered to get around to moving off SHA1 for their repo keys- see below.

https://community.teamviewer.com/English/discussion/126283/sha1-gpg-key-depreciated-on-rhel-9-derivatives

Virtuoso

Thanks, bmdennis. That's rather unexpected and really affects the image of being a professional company.

I may try **Third Party Product** then. The nice thing about TV was TVQS, which is great for non-technical people like my mother in law, but she still needs the 32 bit version which needs updating but is not available anymore either.

Thanks again for responding.