Page 1 of 2 12 LastLast
Results 1 to 10 of 12

Thread: Signature verification failed for microsoft teams repository

  1. #1
    Join Date
    Oct 2009
    Location
    Germany
    Posts
    543

    Default Signature verification failed for microsoft teams repository

    For a few days i get a "signature verification failed" error for the microsoft teams repository. I checked the url: https://packages.microsoft.com/yumrepos/ms-teams/ and everything seemed fine. But the error is annoying. Is there a way to trust the signature again? I tried
    Code:
    zypper clean -a
    and then
    Code:
    zypper refresh
    but that did not help.

  2. #2

    Default Re: Signature verification failed for microsoft teams repository

    Remove the signature and add it again. https://learn.microsoft.com/de-de/wi...osoft-software

  3. #3

    Default Re: Signature verification failed for microsoft teams repository

    Quote Originally Posted by hui View Post
    Remove the signature and add it again. https://learn.microsoft.com/de-de/wi...osoft-software
    How do you remove the signature? That link goes to a German language page general description of how to install microsoft's key and repository, but doesn't say anything about how to actually remove the signature.

    I tried to identify where the signature file is by checking the specific rpm that I have installed from that repository, but I could not figure it out. Here is what I did:

    Code:
    > rpm -qa | grep teams
    teams-1.5.00.10453-1.x86_64
    teams-insiders-1.5.00.23861-1.x86_64
    
    > rpm -K --nosignature teams-1.5.00.10453-1.x86_64
    error: teams-1.5.00.10453-1.x86_64: open failed: No such file or directory
    
    
    I could not find where to delete the key for the repository and install it again. So I tried to unintall the repository and install it again, and I still get the same "signature verification failed" error as the OP.

  4. #4

    Default Re: Signature verification failed for microsoft teams repository

    Quote Originally Posted by techtribe View Post
    How do you remove the signature?

    I could not find where to delete the key for the repository and install it again.
    yast-software -> configuration -> repositorys -> gpg keys

    And i posted the german link as the TO is from germany (even if we are here in the german forum).

  5. #5

    Default Re: Signature verification failed for microsoft teams repository

    Quote Originally Posted by hui View Post
    (even if we are here in the german forum).
    Sorry, i meant even if we are in the english forum.

  6. #6

    Default Re: Signature verification failed for microsoft teams repository

    To show the key with which the package "teams" is signed:

    Code:
    rpm -qa --qf '%{NAME}-%{VERSION}-%{RELEASE} %{SIGPGP:pgpsig} %{SIGGPG:pgpsig}\n' teams
    
    To show the keys available on your system:
    Code:
    rpm -q gpg-pubkey --qf '%{NAME}-%{VERSION}-%{RELEASE}\t%{SUMMARY}\n'
    
    To remove a specific key (as root):
    Code:
    rpm -e gpg-pubkey-abcdefgh-52ae6884

  7. #7

    Default Re: Signature verification failed for microsoft teams repository

    Thank you, those I are the instructions I needed.

    Unfortunately, after deleting microsoft's rpm key and then re-installing it, the "signature verification failed" error is still there. I guess we will have to wait to see what the bug is from microsoft, and since they are not open-source, who knows how long it will take.

  8. #8

    Default Re: Signature verification failed for microsoft teams repository

    Quote Originally Posted by hui View Post
    yast-software -> configuration -> repositorys -> gpg keys

    And i posted the german link as the TO is from germany (even if we are here in the german forum).
    Yes, didn't mean to complain. Thank you for the help.

  9. #9
    Join Date
    Sep 2012
    Posts
    8,221

    Default Re: Signature verification failed for microsoft teams repository

    Quote Originally Posted by hui View Post
    Remove the signature and add it again.
    How exactly is it going to fix bad signature?
    Code:
    bor@bor-Latitude-E5450:~/tmp$ curl -LO https://packages.microsoft.com/yumrepos/ms-teams/repodata/repomd.xml
      % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                     Dload  Upload   Total   Spent    Left  Speed
    100  3085  100  3085    0     0   7894      0 --:--:-- --:--:-- --:--:--  7910
    bor@bor-Latitude-E5450:~/tmp$ curl -LO https://packages.microsoft.com/yumrepos/ms-teams/repodata/repomd.xml.asc
      % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                     Dload  Upload   Total   Spent    Left  Speed
    100   492  100   492    0     0   1418      0 --:--:-- --:--:-- --:--:--  1421
    bor@bor-Latitude-E5450:~/tmp$ mkdir gpg
    bor@bor-Latitude-E5450:~/tmp$ LC_ALL=C gpg --homedir $PWD/gpg --keyserver hkps://keyserver.ubuntu.com/  --receive-keys EB3E94ADBE1229CF
    gpg: WARNING: unsafe permissions on homedir '/home/bor/tmp/gpg'
    gpg: keybox '/home/bor/tmp/gpg/pubring.kbx' created
    gpg: /home/bor/tmp/gpg/trustdb.gpg: trustdb created
    gpg: key EB3E94ADBE1229CF: public key "Microsoft (Release signing) <gpgsecurity@microsoft.com>" imported
    gpg: Total number processed: 1
    gpg:               imported: 1
    bor@bor-Latitude-E5450:~/tmp$ LC_ALL=C gpg --homedir $PWD/gpg repomd.xml.asc 
    gpg: WARNING: unsafe permissions on homedir '/home/bor/tmp/gpg'
    gpg: WARNING: no command supplied.  Trying to guess what you mean ...
    gpg: assuming signed data in 'repomd.xml'
    gpg: Signature made Mon Sep 19 14:43:14 2022 MSK
    gpg:                using RSA key EB3E94ADBE1229CF
    gpg: BAD signature from "Microsoft (Release signing) <gpgsecurity@microsoft.com>" [unknown]
    bor@bor-Latitude-E5450:~/tmp$
    Someone needs to report it to Microsoft.

  10. #10

    Default Re: Signature verification failed for microsoft teams repository

    Quote Originally Posted by arvidjaar View Post
    How exactly is it going to fix bad signature?
    We had this topic already several times here in the forum with the Google Chrome repo where it helped to remove the gpg-pubkey and re-add it. This can help when the key was exchanged upstream but your local copy is still an old one.
    It is possible that this is not the case here.

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •