#3740 Invalid sigs on compose fedmsg messages
Closed: Fixed None Opened 11 years ago by ralph.

Messages from the compose process typically come across with an invalid signature.

The only one that bears a valid signature right now is rawhide for primary arch.

Those with invalid signatures are:

  • branched for primary arch
  • rawhide for secondary arch
  • branched for secondary arch

Like the other tracking tickets created here, this is probably due to an oversight in the routing_policy, but it could also be due (in the secondary arch case) to M2Crypto producing different signatures on different architectures.


This should be fixed as of puppet commit ea2362255876af3ca4d2e4b9f87af3b9001ad076

I'll close the ticket once I've been able to verify.

Login to comment on this ticket.

Metadata