Teams rpm signature issue

Question

Teams rpm signature issue

Miller, Steven 1

I am using Team on Linux, specifically Fedora.

It appears that the way that the rpm is being signed has an issue with Fedora. I have been able to work with other Microsoft rpms without issue, for example the PowerShell rpms.

rpm --delsign teams-1.3.00.16851-1.x86_64.rpm ⇄
teams-1.3.00.16851-1.x86_64.rpm:
error: teams-1.3.00.16851-1.x86_64.rpm: rpmReadSignature failed: signature region 62: tag number mismatch il 9 ril 7 dl 4852 rdl 4852

I should be able to remove signatures from the rpm.

I found this issue when trying to work with the rpm, however, this is the easiest reproducible way to find the problem.

Any ideas?

JimmyYang-MSFT 58,646 Reputation points Microsoft External Staff

2020-07-17T07:34:12.3+00:00

Hi MillerSteven-5729!

Do you mean you cannot delete the signature in Teams rpm package?

What is the meaning of signature?

Can you install the teams-1.3.00.16851-1.x86_64.rpm and login teams normally?

To reproduce the issue, can you provide the detailed steps about this issue?

If you cannot install teams-1.3.00.16851-1.x86_64.rpm, you can find it in the following link to install it:
https://packages.microsoft.com/yumrepos/ms-teams/
Miller, Steven 1 Reputation point

2020-07-18T03:08:37.267+00:00

Thank you \[@\](/users/na/?userId=e352da47-1440-4fd3-815e-208f17ca6577) for responding.

I should of mentioned that I am not having any problem installing or using Teams. The rpm will install following the instructions.

I simply am trying to find a way to work with the rpm within my package manager. The rpm will not work because of the corrupt signature. What I really want to do is ADD a signature to the rpm, but I cannot do that due to the rpm being "nonconforming"

The issue can be reproduced at the command line, running the following:

rpm --delsign teams-1.3.00.16851-1.x86_64.rpm

Result:
teams-1.3.00.16851-1.x86_64.rpm:
error: teams-1.3.00.16851-1.x86_64.rpm: rpmReadSignature failed: signature region 62: tag number mismatch il 9 ril 7 dl 4852 rdl 4852

It happens on all versions of teams, not just the one above. The interesting thing is that this not a Microsoft wide rpm building issue, since other microsoft rpms work just fine.
Miller, Steven 1 Reputation point

2020-08-14T01:41:28.93+00:00

Apologies for the bump.

I also created a RedHat bugzilla for this issue as well. They have come to the conclusion that the teams rpm are "slightly corrupted." So the question is, how are the team rpms being built?

Here is the bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=1851508

Your answer

JimmyYang-MSFT 58,646 Reputation points Microsoft External Staff

2020-07-17T07:34:12.3+00:00

Hi MillerSteven-5729!

Do you mean you cannot delete the signature in Teams rpm package?

What is the meaning of signature?

Can you install the teams-1.3.00.16851-1.x86_64.rpm and login teams normally?

To reproduce the issue, can you provide the detailed steps about this issue?

If you cannot install teams-1.3.00.16851-1.x86_64.rpm, you can find it in the following link to install it:
https://packages.microsoft.com/yumrepos/ms-teams/
Miller, Steven 1 Reputation point

2020-07-18T03:08:37.267+00:00

Thank you \[@\](/users/na/?userId=e352da47-1440-4fd3-815e-208f17ca6577) for responding.

I should of mentioned that I am not having any problem installing or using Teams. The rpm will install following the instructions.

I simply am trying to find a way to work with the rpm within my package manager. The rpm will not work because of the corrupt signature. What I really want to do is ADD a signature to the rpm, but I cannot do that due to the rpm being "nonconforming"

The issue can be reproduced at the command line, running the following:

rpm --delsign teams-1.3.00.16851-1.x86_64.rpm

Result:
teams-1.3.00.16851-1.x86_64.rpm:
error: teams-1.3.00.16851-1.x86_64.rpm: rpmReadSignature failed: signature region 62: tag number mismatch il 9 ril 7 dl 4852 rdl 4852

It happens on all versions of teams, not just the one above. The interesting thing is that this not a Microsoft wide rpm building issue, since other microsoft rpms work just fine.
Miller, Steven 1 Reputation point

2020-08-14T01:41:28.93+00:00

Apologies for the bump.

I also created a RedHat bugzilla for this issue as well. They have come to the conclusion that the teams rpm are "slightly corrupted." So the question is, how are the team rpms being built?

Here is the bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=1851508

Share via

Teams rpm signature issue

Your answer