# src : https://buildlogs.pld-linux.org/pld/th/x32/OK/command,71584326-f514-4189-b8c0-ac3be1ff8232.bz2 # date : 2025/02/05 00:17:48 error: Verifying a signature, but no certificate was provided: Signature 2a91 created at Sun Feb 22 11:51:35 2009 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ed66 created at Fri May 28 11:41:26 2010 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: rpmdbNextIterator: skipping h# 7 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 101101 (2d)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 8 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110000 (30)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 9 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1101110 (6e)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 12 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111110 (3e)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 6509 created at Tue May 8 20:30:39 2012 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: rpmdbNextIterator: skipping h# 17 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111001 (39)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 18 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 100000 (20)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 19 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 101010 (2a)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 20 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 11100 (1c)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 23 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 10011 (13)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 24 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110000 (30)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 25 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1101101 (6d)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 27 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1010111 (57)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 28 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110001 (71)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature ccb1 created at Wed Feb 25 11:47:12 2015 invalid: signature is not alive because: Expired on 2015-03-27T11:47:12Z error: rpmdbNextIterator: skipping h# 29 Header V4 DSA/SHA1 Signature, key ID 399a4dcf: BAD Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature b680 created at Wed Feb 25 11:47:12 2015 invalid: signature is not alive because: Expired on 2015-03-27T11:47:12Z error: rpmdbNextIterator: skipping h# 30 Header V4 DSA/SHA1 Signature, key ID 399a4dcf: BAD Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 0bcc created at Wed Feb 25 13:37:36 2015 invalid: signature is not alive because: Expired on 2015-03-27T13:37:36Z error: rpmdbNextIterator: skipping h# 31 Header V4 DSA/SHA1 Signature, key ID aec0eb07: BAD Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 8a41 created at Wed Feb 25 13:37:36 2015 invalid: signature is not alive because: Expired on 2015-03-27T13:37:36Z error: rpmdbNextIterator: skipping h# 32 Header V4 DSA/SHA1 Signature, key ID aec0eb07: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 33 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1010010 (52)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature e57c created at Wed Feb 25 13:39:03 2015 invalid: signature is not alive because: Expired on 2015-03-27T13:39:03Z error: rpmdbNextIterator: skipping h# 34 Header V4 DSA/SHA1 Signature, key ID 76bcb115: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 36 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1001000 (48)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 19a1 created at Wed Feb 25 13:50:16 2015 invalid: signature is not alive because: Expired on 2015-03-27T13:50:16Z error: rpmdbNextIterator: skipping h# 37 Header V4 DSA/SHA1 Signature, key ID 9b33b31a: BAD Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature ebc6 created at Wed Feb 25 13:40:13 2015 invalid: signature is not alive because: Expired on 2015-03-27T13:40:13Z error: rpmdbNextIterator: skipping h# 38 Header V4 DSA/SHA1 Signature, key ID 4f1f2d1c: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 39 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110 (e)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 40 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1000 (8)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 41 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110011 (73)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 42 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1101110 (6e)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 43 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 11111 (1f)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 44 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1010000 (50)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 45 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 10110 (16)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature f646 created at Wed Feb 25 14:48:46 2015 invalid: signature is not alive because: Expired on 2015-03-27T14:48:46Z error: rpmdbNextIterator: skipping h# 47 Header V4 DSA/SHA1 Signature, key ID 825bb4d0: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 48 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1100011 (63)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 49 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1000011 (43)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 50 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1010111 (57)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 55 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110011 (73)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 56 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1000110 (46)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 57 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 101 (5)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 9e41 created at Wed Feb 25 16:44:57 2015 invalid: signature is not alive because: Expired on 2015-03-27T16:44:57Z error: rpmdbNextIterator: skipping h# 58 Header V4 DSA/SHA1 Signature, key ID f5a45994: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 59 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 101010 (2a)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 62 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 11101 (1d)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 63 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1111100 (7c)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 64 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1101111 (6f)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 65 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1010000 (50)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 66 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 11101 (1d)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 67 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110 (e)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 68 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 101101 (2d)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 196e created at Wed Feb 25 21:17:55 2015 invalid: signature is not alive because: Expired on 2015-03-27T21:17:55Z error: rpmdbNextIterator: skipping h# 69 Header V4 DSA/SHA1 Signature, key ID 80110692: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 73 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 100011 (23)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 74 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1011010 (5a)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 75 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1111001 (79)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 78 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1011110 (5e)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 79 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111111 (3f)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 80 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 101000 (28)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 81 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 11 (3)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 84 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110100 (34)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 85 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1001001 (49)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 70fd created at Thu Feb 26 05:35:09 2015 invalid: signature is not alive because: Expired on 2015-03-28T05:35:09Z error: rpmdbNextIterator: skipping h# 94 Header V4 DSA/SHA1 Signature, key ID 318da52c: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 95 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 101011 (2b)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 96 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1011100 (5c)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 97 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110100 (74)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature cf4a created at Wed Feb 13 22:34:07 2008 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: rpmdbNextIterator: skipping h# 99 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1010000 (50)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 100 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110011 (33)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 101 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111110 (3e)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 104 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1010010 (52)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 105 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110101 (35)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 106 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1001 (9)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 107 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 100 (4)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 108 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 11010 (1a)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 109 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 10101 (15)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 110 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1100000 (60)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 111 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1101110 (6e)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 112 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1111100 (7c)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 114 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 11101 (1d)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 115 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1101 (d)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature a0bf created at Sun Mar 1 12:20:27 2015 invalid: signature is not alive because: Expired on 2015-03-31T12:20:27Z error: rpmdbNextIterator: skipping h# 119 Header V4 DSA/SHA1 Signature, key ID 6d44c5b1: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 120 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1111100 (7c)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 121 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111100 (3c)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 122 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 100100 (24)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 35fb created at Sun Mar 1 13:58:39 2015 invalid: signature is not alive because: Expired on 2015-03-31T13:58:39Z error: rpmdbNextIterator: skipping h# 123 Header V4 DSA/SHA1 Signature, key ID af7bfc95: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 124 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110010 (72)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 125 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 100100 (24)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 09f2 created at Sun Mar 1 12:20:08 2015 invalid: signature is not alive because: Expired on 2015-03-31T12:20:08Z error: rpmdbNextIterator: skipping h# 126 Header V4 DSA/SHA1 Signature, key ID 5f0606f9: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 128 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1100100 (64)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 129 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1111010 (7a)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 130 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111101 (3d)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 131 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111000 (38)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 132 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 101001 (29)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 133 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1011010 (5a)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature cf2c created at Thu Apr 17 17:46:00 2014 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: rpmdbNextIterator: skipping h# 136 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1100101 (65)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 137 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110111 (37)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 141 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 101 (5)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 144 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110 (6)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 145 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1111100 (7c)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 146 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1101 (d)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 147 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1010110 (56)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature d395 created at Thu Mar 5 17:30:11 2015 invalid: signature is not alive because: Expired on 2015-04-04T17:30:11Z error: rpmdbNextIterator: skipping h# 148 Header V4 DSA/SHA1 Signature, key ID 46039f57: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 149 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1001010 (4a)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 150 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1011100 (5c)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 155 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1010 (a)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 156 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1011111 (5f)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 157 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 11100 (1c)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 158 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1100001 (61)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 159 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111110 (3e)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 3f74 created at Mon Mar 9 16:24:29 2015 invalid: signature is not alive because: Expired on 2015-04-08T16:24:29Z error: rpmdbNextIterator: skipping h# 160 Header V4 DSA/SHA1 Signature, key ID 33aeec09: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 161 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111100 (3c)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 162 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 100010 (22)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 163 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 101000 (28)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 165 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1000000 (40)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 166 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 10 (2)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 167 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 11000 (18)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 168 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1011011 (5b)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 169 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 101110 (2e)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 170 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111001 (39)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 171 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 100010 (22)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 172 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111111 (3f)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 173 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1000001 (41)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 175 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1000010 (42)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 176 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1010110 (56)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 177 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1100111 (67)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 178 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1001000 (48)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 182 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 11001 (19)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 184 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1010111 (57)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 29b0 created at Thu Mar 12 09:00:27 2015 invalid: signature is not alive because: Expired on 2015-04-11T09:00:27Z error: rpmdbNextIterator: skipping h# 185 Header V4 DSA/SHA1 Signature, key ID fbcea788: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 186 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 11111 (1f)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 187 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1101101 (6d)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 188 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110 (e)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 189 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 100110 (26)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 190 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 101101 (2d)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 207 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1100000 (60)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 2e72 created at Mon Mar 9 20:28:48 2015 invalid: signature is not alive because: Expired on 2015-04-08T20:28:48Z error: rpmdbNextIterator: skipping h# 208 Header V4 DSA/SHA1 Signature, key ID 3a3385d4: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 209 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1011000 (58)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 210 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1001001 (49)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 211 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 101 (5)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 214 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110010 (32)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 215 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 101101 (2d)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature a23e created at Sat Oct 20 22:10:33 2012 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: rpmdbNextIterator: skipping h# 217 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 101010 (2a)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 218 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111 (7)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 219 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 10000 (10)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 220 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1000100 (44)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 221 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 100001 (21)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 222 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 10001 (11)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature a10a created at Sun Mar 1 12:23:46 2015 invalid: signature is not alive because: Expired on 2015-03-31T12:23:46Z error: rpmdbNextIterator: skipping h# 223 Header V4 DSA/SHA1 Signature, key ID 26832024: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 226 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 101 (5)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 5a4a created at Sun Mar 15 11:37:25 2015 invalid: signature is not alive because: Expired on 2015-04-14T11:37:25Z error: rpmdbNextIterator: skipping h# 227 Header V4 DSA/SHA1 Signature, key ID c3a4edee: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 228 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110001 (71)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 229 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111000 (38)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 230 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1000101 (45)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 231 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1100001 (61)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 232 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1000001 (41)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 233 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110010 (32)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 234 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 10110 (16)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 235 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1011111 (5f)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 236 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1101001 (69)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature ec61 created at Sun Mar 22 13:16:45 2015 invalid: signature is not alive because: Expired on 2015-04-21T13:16:45Z error: rpmdbNextIterator: skipping h# 237 Header V4 DSA/SHA1 Signature, key ID 95afa560: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 238 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1010101 (55)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 240 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110111 (37)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 241 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1000000 (40)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature a481 created at Sun Feb 22 00:06:04 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 71f7 created at Mon Jul 22 19:47:39 2013 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: rpmdbNextIterator: skipping h# 246 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 11001 (19)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 247 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111100 (3c)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 249 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1011011 (5b)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 251 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 11 (3)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 252 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 101100 (2c)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 253 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110110 (76)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 254 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 10110 (16)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature f9e3 created at Wed Mar 25 09:52:15 2015 invalid: signature is not alive because: Expired on 2015-04-24T09:52:15Z error: rpmdbNextIterator: skipping h# 255 Header V4 DSA/SHA1 Signature, key ID 3ac5e1c0: BAD Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature e5c8 created at Wed Mar 25 09:52:15 2015 invalid: signature is not alive because: Expired on 2015-04-24T09:52:15Z error: rpmdbNextIterator: skipping h# 256 Header V4 DSA/SHA1 Signature, key ID 3ac5e1c0: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 257 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110110 (36)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 258 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111 (7)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 2a2e created at Wed Mar 25 09:50:20 2015 invalid: signature is not alive because: Expired on 2015-04-24T09:50:20Z error: rpmdbNextIterator: skipping h# 259 Header V4 DSA/SHA1 Signature, key ID 62443601: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 260 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111 (7)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 261 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 100101 (25)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 262 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1010 (a)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature c0ee created at Sun Dec 19 13:07:21 2010 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: rpmdbNextIterator: skipping h# 264 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1011 (b)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 265 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1100001 (61)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 4a9a created at Sun Mar 29 09:35:37 2015 invalid: signature is not alive because: Expired on 2015-04-28T09:35:37Z error: rpmdbNextIterator: skipping h# 266 Header V4 DSA/SHA1 Signature, key ID 5eac1385: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 267 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 100110 (26)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 7b3c created at Sat Mar 28 20:38:13 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 31a3 created at Sat Mar 28 20:38:13 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: rpmdbNextIterator: skipping h# 271 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110011 (73)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature b63d created at Sat Mar 28 17:36:55 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 16ff created at Sat Mar 28 17:36:55 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: rpmdbNextIterator: skipping h# 279 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1001011 (4b)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 280 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111000 (38)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 281 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110111 (37)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 282 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110010 (32)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature be67 created at Sat Mar 28 20:45:19 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 432e created at Sat Mar 28 17:54:51 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9973 created at Sat Mar 28 19:06:06 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature c7a2 created at Sat Mar 28 19:06:08 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: rpmdbNextIterator: skipping h# 289 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110101 (75)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 290 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110001 (31)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 291 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1010100 (54)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 292 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111 (7)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 293 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1011100 (5c)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 2050 created at Wed Feb 26 18:59:28 2014 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: rpmdbNextIterator: skipping h# 297 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1111010 (7a)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 299 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111001 (39)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 300 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 10110 (16)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 8b4e created at Sat Apr 18 18:44:44 2015 invalid: signature is not alive because: Expired on 2015-05-18T18:44:44Z error: rpmdbNextIterator: skipping h# 301 Header V4 DSA/SHA1 Signature, key ID a12c1b3b: BAD Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 27f2 created at Sat Apr 18 18:53:17 2015 invalid: signature is not alive because: Expired on 2015-05-18T18:53:17Z error: rpmdbNextIterator: skipping h# 304 Header V4 DSA/SHA1 Signature, key ID 60516309: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 306 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111101 (3d)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature d8c0 created at Sun Apr 19 21:17:59 2015 invalid: signature is not alive because: Expired on 2015-05-19T21:17:59Z error: rpmdbNextIterator: skipping h# 307 Header V4 DSA/SHA1 Signature, key ID 24c0c9a7: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 308 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 100110 (26)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 310 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1011101 (5d)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 311 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1101 (d)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 0027 created at Sat Mar 28 17:55:35 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: rpmdbNextIterator: skipping h# 313 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1000010 (42)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 314 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 11011 (1b)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 2f4e created at Sat Mar 28 17:48:44 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: rpmdbNextIterator: skipping h# 317 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1001011 (4b)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 318 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 101001 (29)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 319 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110011 (73)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 320 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1010110 (56)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 966c created at Wed May 6 21:58:34 2015 invalid: signature is not alive because: Expired on 2015-06-05T21:58:34Z error: rpmdbNextIterator: skipping h# 324 Header V4 DSA/SHA1 Signature, key ID ad7be75a: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 325 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110 (6)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 326 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1111000 (78)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 327 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1101001 (69)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 328 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111 (7)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 329 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1000100 (44)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 330 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1100010 (62)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature c64c created at Sun May 10 11:35:43 2015 invalid: signature is not alive because: Expired on 2015-06-09T11:35:43Z error: rpmdbNextIterator: skipping h# 334 Header V4 DSA/SHA1 Signature, key ID 15c86b34: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 335 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111 (7)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 340 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1001111 (4f)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 341 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1010001 (51)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 342 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111010 (3a)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 343 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1000000 (40)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 344 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1111010 (7a)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 345 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1000011 (43)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 346 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1011100 (5c)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 347 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 10011 (13)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature d8a9 created at Mon Jun 1 18:53:38 2015 invalid: signature is not alive because: Expired on 2015-07-01T18:53:38Z error: rpmdbNextIterator: skipping h# 348 Header V4 DSA/SHA1 Signature, key ID e9f46c99: BAD Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 01c5 created at Mon Jun 1 18:53:38 2015 invalid: signature is not alive because: Expired on 2015-07-01T18:53:38Z error: rpmdbNextIterator: skipping h# 349 Header V4 DSA/SHA1 Signature, key ID e9f46c99: BAD Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 0683 created at Tue Jun 9 03:16:19 2015 invalid: signature is not alive because: Expired on 2015-07-09T03:16:19Z error: rpmdbNextIterator: skipping h# 350 Header V4 DSA/SHA1 Signature, key ID 56091c70: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 351 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110010 (72)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 3109 created at Sat Mar 28 18:00:05 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature c97c created at Sat Mar 28 18:00:05 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature dc6d created at Tue Jun 9 20:57:54 2015 invalid: signature is not alive because: Expired on 2015-07-09T20:57:54Z error: rpmdbNextIterator: skipping h# 354 Header V4 DSA/SHA1 Signature, key ID 16c1ec53: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 356 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1001001 (49)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 357 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 10110 (16)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 358 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1111010 (7a)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature a5e2 created at Wed Jun 10 20:10:43 2015 invalid: signature is not alive because: Expired on 2015-07-10T20:10:43Z error: rpmdbNextIterator: skipping h# 359 Header V4 DSA/SHA1 Signature, key ID 37508607: BAD Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 361e created at Thu Jun 11 19:16:12 2015 invalid: signature is not alive because: Expired on 2015-07-11T19:16:12Z error: rpmdbNextIterator: skipping h# 360 Header V4 DSA/SHA1 Signature, key ID 216deb2a: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 361 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1101001 (69)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 364 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 101011 (2b)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 365 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1101111 (6f)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 366 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 11001 (19)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 368 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110010 (32)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 369 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 11111 (1f)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature d224 created at Sat Mar 28 18:34:58 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature a166 created at Sat Mar 28 18:34:58 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: rpmdbNextIterator: skipping h# 372 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 10001 (11)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 375 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 101111 (2f)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature cb1d created at Wed Jul 8 03:43:15 2015 invalid: signature is not alive because: Expired on 2015-08-07T03:43:15Z error: rpmdbNextIterator: skipping h# 376 Header V4 DSA/SHA1 Signature, key ID d6763c30: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 377 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 101011 (2b)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 378 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1011101 (5d)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature af44 created at Sat Mar 28 20:18:42 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: rpmdbNextIterator: skipping h# 386 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1101110 (6e)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 387 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110100 (74)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 390 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1001011 (4b)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 391 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 100010 (22)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 392 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 101100 (2c)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 393 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110101 (35)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 4ac9 created at Fri Aug 7 06:33:05 2015 invalid: signature is not alive because: Expired on 2015-09-06T06:33:05Z error: rpmdbNextIterator: skipping h# 395 Header V4 DSA/SHA1 Signature, key ID bc5e9781: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 396 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111001 (39)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 397 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110110 (36)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 398 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1100011 (63)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 5f82 created at Sun Aug 9 11:43:38 2015 invalid: signature is not alive because: Expired on 2015-09-08T11:43:38Z error: rpmdbNextIterator: skipping h# 399 Header V4 DSA/SHA1 Signature, key ID 0dbf5aee: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 400 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1101010 (6a)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 401 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111001 (39)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 2c21 created at Tue Aug 18 13:28:21 2015 invalid: signature is not alive because: Expired on 2015-09-17T13:28:21Z error: rpmdbNextIterator: skipping h# 402 Header V4 DSA/SHA1 Signature, key ID 46f9fc6b: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 403 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1100 (c)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 58a2 created at Sat Mar 28 17:40:43 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: rpmdbNextIterator: skipping h# 411 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1011110 (5e)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 414 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1100011 (63)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 415 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 10 (2)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 417 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 11 (3)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 418 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1011011 (5b)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 419 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1010000 (50)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 420 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1000011 (43)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 424 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110 (e)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 425 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110000 (30)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 426 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110100 (34)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 427 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1011100 (5c)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 428 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110001 (71)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 429 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1111000 (78)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 430 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 101100 (2c)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 433 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 101 (5)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 434 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1010001 (51)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 435 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1111101 (7d)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 436 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110 (6)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 437 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110 (e)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 438 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110 (6)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 439 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1100010 (62)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 440 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1000100 (44)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 441 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1111 (f)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 442 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 11101 (1d)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 443 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110001 (31)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 444 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111110 (3e)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 445 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1010101 (55)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 52ab created at Tue Oct 6 15:29:37 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature bdd9 created at Sat Mar 28 17:41:12 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: rpmdbNextIterator: skipping h# 449 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110101 (35)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 450 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1111101 (7d)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 451 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1010010 (52)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 452 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1001111 (4f)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 453 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1100111 (67)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 455 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1001100 (4c)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 639b created at Sun Nov 29 03:39:51 2015 invalid: signature is not alive because: Expired on 2015-12-29T03:39:51Z error: rpmdbNextIterator: skipping h# 456 Header V4 DSA/SHA1 Signature, key ID 88b24510: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 457 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1100011 (63)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 461 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1101011 (6b)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature bd2e created at Thu Jan 9 21:51:22 2014 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: rpmdbNextIterator: skipping h# 466 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 10011 (13)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 467 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 100001 (21)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature c4ec created at Sun Nov 29 19:53:46 2015 invalid: signature is not alive because: Expired on 2015-12-29T19:53:46Z error: rpmdbNextIterator: skipping h# 470 Header V4 DSA/SHA1 Signature, key ID 30245061: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 471 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 10011 (13)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 472 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1000110 (46)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 473 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110100 (74)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 474 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 10 (2)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 476 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1001101 (4d)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 477 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1000101 (45)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature c277 created at Sun Dec 6 15:32:25 2015 invalid: signature is not alive because: Expired on 2016-01-05T15:32:25Z error: rpmdbNextIterator: skipping h# 480 Header V4 DSA/SHA1 Signature, key ID 6be924f1: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 481 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111100 (3c)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 488 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110000 (70)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 489 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1010101 (55)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 490 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1010110 (56)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 491 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1100111 (67)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 492 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 101010 (2a)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 493 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 10011 (13)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 498 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110111 (37)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 502 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1101101 (6d)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 503 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110010 (72)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 504 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 11100 (1c)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 505 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1010100 (54)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 506 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110111 (77)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 507 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1011101 (5d)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 508 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110100 (34)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 509 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110110 (36)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 510 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1 (1)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 511 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 11001 (19)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 40f8 created at Wed Jan 20 15:28:04 2016 invalid: signature is not alive because: Expired on 2016-02-19T15:28:04Z error: rpmdbNextIterator: skipping h# 512 Header V4 DSA/SHA1 Signature, key ID 20b45a51: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 513 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1010101 (55)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 514 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 101101 (2d)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature fc0a created at Sat Mar 28 17:42:02 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 42be created at Sat Mar 28 17:42:02 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: rpmdbNextIterator: skipping h# 518 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1100101 (65)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 519 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 11000 (18)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 522 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110101 (35)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature b22b created at Wed Mar 2 17:36:03 2016 invalid: signature is not alive because: Expired on 2016-04-01T17:36:03Z error: rpmdbNextIterator: skipping h# 523 Header V4 DSA/SHA1 Signature, key ID 9c9492de: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 524 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110010 (72)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 525 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110000 (30)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 526 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1 (1)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 527 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 101100 (2c)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 528 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 10100 (14)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 529 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1111011 (7b)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 530 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1011000 (58)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 64e6 created at Sat Mar 28 17:42:49 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 0477 created at Sat Mar 28 17:42:49 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 7d23 created at Mon Mar 28 18:27:47 2016 invalid: signature is not alive because: Expired on 2016-04-27T18:27:47Z error: rpmdbNextIterator: skipping h# 533 Header V4 DSA/SHA1 Signature, key ID 0d992dfc: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 535 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 10010 (12)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 536 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 101110 (2e)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 537 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 10010 (12)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 538 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1111110 (7e)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 539 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 11111 (1f)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 540 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110100 (34)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 541 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1011101 (5d)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 542 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1000101 (45)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 543 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1101110 (6e)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 544 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1000000 (40)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 545 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 101100 (2c)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 546 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110111 (77)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 548 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1000001 (41)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 549 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 100001 (21)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 550 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1011110 (5e)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 552 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1011110 (5e)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 53cb created at Fri Feb 26 07:39:16 2016 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 5570 created at Sun Apr 17 11:59:27 2016 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: rpmdbNextIterator: skipping h# 557 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 101000 (28)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 558 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1001101 (4d)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 5f2d created at Wed Dec 23 00:48:37 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: rpmdbNextIterator: skipping h# 566 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110100 (34)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 567 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1 (1)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 568 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1000101 (45)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 569 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 101001 (29)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature f311 created at Fri Apr 29 16:10:02 2016 invalid: signature is not alive because: Expired on 2016-05-29T16:10:02Z error: rpmdbNextIterator: skipping h# 570 Header V4 DSA/SHA1 Signature, key ID bfde51f4: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 572 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1101010 (6a)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 576 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1000011 (43)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 577 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 100100 (24)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 578 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1000 (8)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 579 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1011100 (5c)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 580 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 11001 (19)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 581 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1011101 (5d)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 582 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110100 (34)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 583 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1101110 (6e)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 585 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110101 (75)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature b50c created at Thu May 12 06:50:07 2016 invalid: signature is not alive because: Expired on 2016-06-11T06:50:07Z error: rpmdbNextIterator: skipping h# 586 Header V4 DSA/SHA1 Signature, key ID ec0a2ad1: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 593 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1101 (d)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 594 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1001 (9)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 595 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1001 (9)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 596 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110101 (75)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 597 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111010 (3a)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 598 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 100110 (26)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 601 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110 (e)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 604 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 10110 (16)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 605 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1011011 (5b)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 606 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111100 (3c)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 607 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1011101 (5d)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 608 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110101 (75)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 609 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1100100 (64)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 610 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1101100 (6c)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 611 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110 (6)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 612 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1101011 (6b)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 613 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1000011 (43)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 614 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110111 (77)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 615 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 101010 (2a)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature a65d created at Sun Jul 31 14:26:47 2016 invalid: signature is not alive because: Expired on 2016-08-30T14:26:47Z error: rpmdbNextIterator: skipping h# 618 Header V4 DSA/SHA1 Signature, key ID 9292fb99: BAD Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 5b1e created at Sun Aug 28 14:55:30 2016 invalid: signature is not alive because: Expired on 2016-09-27T14:55:30Z error: rpmdbNextIterator: skipping h# 621 Header V4 DSA/SHA1 Signature, key ID 6fdf88e9: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 622 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110000 (30)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 625 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 11100 (1c)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 626 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1000110 (46)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 627 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 10111 (17)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 628 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1000110 (46)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 629 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1101 (d)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 631 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 100110 (26)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 637 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1010100 (54)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 649 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110001 (71)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 650 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 10 (2)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 651 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110000 (70)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 652 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1111 (f)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 653 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1000011 (43)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 6ce1 created at Wed Dec 23 00:37:52 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: rpmdbNextIterator: skipping h# 655 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1001000 (48)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 656 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 100010 (22)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 657 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 11010 (1a)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 9435 created at Sat Mar 28 19:19:31 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 7d91 created at Sat Mar 28 19:19:31 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e675 created at Tue Dec 20 16:23:01 2016 invalid: signature is not alive because: Expired on 2017-01-19T16:23:01Z error: rpmdbNextIterator: skipping h# 664 Header V4 DSA/SHA1 Signature, key ID 9a60853f: BAD Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 5be3 created at Tue Dec 20 16:23:01 2016 invalid: signature is not alive because: Expired on 2017-01-19T16:23:01Z error: rpmdbNextIterator: skipping h# 665 Header V4 DSA/SHA1 Signature, key ID 9a60853f: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 670 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 11101 (1d)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 674 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1101111 (6f)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 676 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1011000 (58)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 678 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111 (7)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 1fe7 created at Sun Jan 22 16:50:20 2017 invalid: signature is not alive because: Expired on 2017-02-21T16:50:20Z error: rpmdbNextIterator: skipping h# 679 Header V4 DSA/SHA1 Signature, key ID 84716d74: BAD Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 7402 created at Sat Feb 18 20:00:13 2017 invalid: signature is not alive because: Expired on 2017-03-20T20:00:13Z error: rpmdbNextIterator: skipping h# 686 Header V4 DSA/SHA1 Signature, key ID 8c566d85: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 687 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110110 (36)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 689 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111101 (3d)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 690 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110010 (32)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 691 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110111 (77)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 694 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 100011 (23)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 695 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1100011 (63)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 698 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110111 (37)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 701 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1001100 (4c)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 702 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 10101 (15)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 703 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1001011 (4b)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 8f19 created at Sat Jan 21 19:19:05 2017 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: rpmdbNextIterator: skipping h# 714 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1001111 (4f)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 8b6a created at Wed Mar 29 19:51:18 2017 invalid: signature is not alive because: Expired on 2017-04-28T19:51:18Z error: rpmdbNextIterator: skipping h# 715 Header V4 DSA/SHA1 Signature, key ID e5e9c3e4: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 716 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 101 (5)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 0c7d created at Wed Mar 29 19:51:18 2017 invalid: signature is not alive because: Expired on 2017-04-28T19:51:18Z error: rpmdbNextIterator: skipping h# 717 Header V4 DSA/SHA1 Signature, key ID e5e9c3e4: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 736 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1111001 (79)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 737 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1011 (b)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 738 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111000 (38)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 752 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1001100 (4c)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 759 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1001111 (4f)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 762 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1101110 (6e)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 766 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111101 (3d)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 767 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1111 (f)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 768 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1011011 (5b)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature b4e1 created at Sun May 29 11:46:46 2016 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 948e created at Sun May 29 11:46:46 2016 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: rpmdbNextIterator: skipping h# 795 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110011 (73)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 805 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 101010 (2a)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 806 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110011 (73)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 3f56 created at Thu Jun 22 19:36:46 2017 invalid: signature is not alive because: Expired on 2017-07-22T19:36:46Z error: rpmdbNextIterator: skipping h# 807 Header V4 DSA/SHA1 Signature, key ID 1e72965a: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 808 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1001000 (48)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 813 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110000 (70)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 817 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 11110 (1e)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 821 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1001 (9)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 822 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110010 (72)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 824 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1010000 (50)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 825 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 100000 (20)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 826 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1001100 (4c)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 835 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110010 (72)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 836 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 100110 (26)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 851 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1111111 (7f)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature e08e created at Sun Mar 5 11:07:51 2017 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: rpmdbNextIterator: skipping h# 873 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 101111 (2f)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 874 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 100 (4)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 878 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1010001 (51)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 879 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 11111 (1f)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 886 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110001 (71)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 888 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1000101 (45)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 889 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1001010 (4a)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 890 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1011 (b)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 894 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 11010 (1a)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 897 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 11000 (18)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature f644 created at Thu Dec 14 15:49:53 2017 invalid: signature is not alive because: Expired on 2018-01-13T15:49:53Z error: rpmdbNextIterator: skipping h# 898 Header V4 DSA/SHA1 Signature, key ID 4bbcee4c: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 899 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 11 (3)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 900 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1001 (9)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 901 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1101011 (6b)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 7154 created at Sat Mar 28 18:01:00 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: rpmdbNextIterator: skipping h# 925 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1111000 (78)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 926 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1111011 (7b)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 927 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 11101 (1d)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 928 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110010 (72)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 929 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1001111 (4f)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 931 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1111100 (7c)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 932 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 100111 (27)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 43ae created at Sat Mar 28 20:41:17 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: rpmdbNextIterator: skipping h# 935 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1000000 (40)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 936 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1100111 (67)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 8b27 created at Sun Dec 17 14:01:57 2017 invalid: signature is not alive because: Expired on 2018-01-16T14:01:57Z error: rpmdbNextIterator: skipping h# 937 Header V4 DSA/SHA1 Signature, key ID 47b8ac93: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 940 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1001110 (4e)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 941 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1001000 (48)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature b2ff created at Tue Feb 17 09:46:28 2009 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 066d created at Tue Apr 20 07:06:59 2010 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature a41c created at Sat May 27 06:32:51 2017 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9fd8 created at Sat May 27 06:32:51 2017 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ff8d created at Sat Oct 15 20:40:56 2016 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 09fd created at Sat Oct 15 20:40:56 2016 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 8474 created at Sat Feb 17 10:29:54 2018 invalid: signature is not alive because: Expired on 2018-03-19T10:29:54Z error: rpmdbNextIterator: skipping h# 961 Header V4 DSA/SHA1 Signature, key ID 8baf6f72: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 962 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110110 (76)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 964 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110001 (31)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 965 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110010 (32)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 966 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 10000 (10)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature a9f3 created at Sat Mar 3 16:41:56 2018 invalid: signature is not alive because: Expired on 2018-04-02T16:41:56Z error: rpmdbNextIterator: skipping h# 974 Header V4 DSA/SHA1 Signature, key ID cb6c7ca0: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 975 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1001111 (4f)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 982 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1101010 (6a)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 983 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1 (1)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 984 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1010010 (52)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 985 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111011 (3b)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 994 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1000010 (42)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 995 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110 (6)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1001 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1000 (8)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1002 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1100111 (67)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1003 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1010011 (53)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1004 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1101110 (6e)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1005 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1010000 (50)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1009 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1000011 (43)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1011 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 101110 (2e)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1012 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 10100 (14)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1023 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1111101 (7d)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1024 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1111100 (7c)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1025 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 100100 (24)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1026 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1101 (d)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1029 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110000 (70)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1033 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110110 (36)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 4f89 created at Wed Dec 23 00:50:35 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature c4e7 created at Wed Dec 23 00:58:08 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 407b created at Mon Nov 9 21:03:48 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 204b created at Thu May 11 17:56:26 2017 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature d748 created at Thu Jul 9 20:44:13 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 1fcd created at Thu Jul 9 20:44:13 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 4ad5 created at Wed Dec 23 00:40:23 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature a54a created at Wed Dec 23 00:06:57 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 05b3 created at Wed Dec 23 00:57:40 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: rpmdbNextIterator: skipping h# 1075 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1100001 (61)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1076 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 101101 (2d)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1079 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1011011 (5b)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1083 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110 (6)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1084 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1010111 (57)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature dabe created at Fri Apr 14 16:25:57 2017 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 1c53 created at Sun Jul 29 14:35:35 2018 invalid: signature is not alive because: Expired on 2018-08-28T14:35:35Z error: rpmdbNextIterator: skipping h# 1092 Header V4 DSA/SHA1 Signature, key ID dbd8ef00: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1093 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 101111 (2f)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature cf0e created at Mon Jul 30 17:09:44 2018 invalid: signature is not alive because: Expired on 2018-08-29T17:09:44Z error: rpmdbNextIterator: skipping h# 1094 Header V4 DSA/SHA1 Signature, key ID ba86ac0c: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1095 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 11100 (1c)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1096 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110 (6)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1097 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 10101 (15)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1098 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 10111 (17)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 2462 created at Mon Nov 9 21:04:40 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9579 created at Sun Jul 16 15:05:48 2017 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 06ad created at Thu Aug 16 07:31:23 2018 invalid: signature is not alive because: Expired on 2018-09-15T07:31:23Z error: rpmdbNextIterator: skipping h# 1105 Header V4 DSA/SHA1 Signature, key ID 87a8ac9f: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1106 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1111101 (7d)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1109 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1100100 (64)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature a48c created at Tue Aug 21 21:51:04 2018 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature c5e2 created at Tue Aug 21 21:51:04 2018 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: rpmdbNextIterator: skipping h# 1133 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1010111 (57)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature b0c0 created at Sat Mar 28 18:56:37 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature cca9 created at Sat Mar 28 20:23:25 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ea17 created at Sat Mar 28 20:45:19 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: rpmdbNextIterator: skipping h# 1172 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1010101 (55)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 81bc created at Sun Feb 11 16:42:56 2018 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 66b1 created at Sat May 27 06:41:52 2017 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 5c15 created at Sat Mar 28 20:47:46 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3808 created at Sat Mar 28 20:47:46 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature cd88 created at Tue Sep 25 19:37:33 2018 invalid: signature is not alive because: Expired on 2018-10-25T19:37:33Z error: rpmdbNextIterator: skipping h# 1191 Header V4 DSA/SHA1 Signature, key ID d8dac107: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1192 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1011011 (5b)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1193 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110000 (30)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1207 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110110 (76)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1208 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1100111 (67)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1209 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110001 (31)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 09f3 created at Sun Sep 30 09:31:57 2018 invalid: signature is not alive because: Expired on 2018-10-30T09:31:57Z error: rpmdbNextIterator: skipping h# 1210 Header V4 DSA/SHA1 Signature, key ID ccd739d1: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1215 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110010 (72)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1216 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 11111 (1f)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1217 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1000111 (47)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1225 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1000011 (43)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1226 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1000000 (40)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1227 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1000001 (41)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 99bd created at Sun Apr 22 11:55:56 2018 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature eb36 created at Sun Apr 22 11:55:56 2018 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: rpmdbNextIterator: skipping h# 1236 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110100 (34)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1237 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111011 (3b)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 9aeb created at Wed Oct 17 18:59:25 2018 invalid: signature is not alive because: Expired on 2018-11-16T18:59:25Z error: rpmdbNextIterator: skipping h# 1240 Header V4 DSA/SHA1 Signature, key ID f6dfc519: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1241 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111000 (38)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1248 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111101 (3d)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1249 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1001100 (4c)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature e10d created at Mon Oct 22 21:01:58 2018 invalid: signature is not alive because: Expired on 2018-11-21T21:01:58Z error: rpmdbNextIterator: skipping h# 1250 Header V4 DSA/SHA1 Signature, key ID 202ef912: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1251 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1011001 (59)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1256 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110011 (73)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature c99d created at Thu Nov 8 09:00:14 2018 invalid: signature is not alive because: Expired on 2018-12-08T09:00:14Z error: rpmdbNextIterator: skipping h# 1261 Header V4 DSA/SHA1 Signature, key ID 85505e9a: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1272 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110111 (77)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1276 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1111110 (7e)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature f454 created at Fri Feb 26 07:31:36 2016 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: rpmdbNextIterator: skipping h# 1285 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1100101 (65)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1286 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 10 (2)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1287 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1100000 (60)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 8e68 created at Tue Aug 21 22:04:01 2018 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: rpmdbNextIterator: skipping h# 1294 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 100111 (27)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 66b6 created at Mon Dec 10 07:33:47 2018 invalid: signature is not alive because: Expired on 2019-01-09T07:33:47Z error: rpmdbNextIterator: skipping h# 1295 Header V4 DSA/SHA1 Signature, key ID 77dd2d49: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1301 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1011000 (58)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 3b68 created at Sun Dec 23 11:22:29 2018 invalid: signature is not alive because: Expired on 2019-01-22T11:22:29Z error: rpmdbNextIterator: skipping h# 1304 Header V4 DSA/SHA1 Signature, key ID 70e47f8f: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1309 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1101101 (6d)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature ff89 created at Mon Dec 24 14:14:52 2018 invalid: signature is not alive because: Expired on 2019-01-23T14:14:52Z error: rpmdbNextIterator: skipping h# 1310 Header V4 DSA/SHA1 Signature, key ID ff3b91da: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1314 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 101111 (2f)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1315 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111010 (3a)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1321 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 100 (4)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1322 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110111 (37)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1336 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 100000 (20)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1337 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 100 (4)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature a6cd created at Sat May 27 06:43:32 2017 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 00a4 created at Sat May 27 06:43:32 2017 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: rpmdbNextIterator: skipping h# 1352 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1010010 (52)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1353 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 10101 (15)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1354 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110011 (33)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1355 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1111110 (7e)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1362 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1111111 (7f)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1363 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 100000 (20)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1366 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 101101 (2d)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1371 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1100000 (60)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1374 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110100 (74)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 6f61 created at Thu Jul 9 20:49:27 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: rpmdbNextIterator: skipping h# 1387 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1100011 (63)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 6de5 created at Fri Mar 15 00:26:24 2019 invalid: signature is not alive because: Expired on 2019-04-14T00:26:24Z error: rpmdbNextIterator: skipping h# 1388 Header V4 DSA/SHA1 Signature, key ID 646f158b: BAD Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 1238 created at Fri Mar 15 00:40:28 2019 invalid: signature is not alive because: Expired on 2019-04-14T00:40:28Z error: rpmdbNextIterator: skipping h# 1389 Header V4 DSA/SHA1 Signature, key ID 81c1e5c6: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1395 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1101010 (6a)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1399 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 101010 (2a)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1415 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1101010 (6a)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1418 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1100 (c)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1419 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 11011 (1b)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1425 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111011 (3b)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 2dbe created at Sat Mar 30 20:28:46 2019 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature cc69 created at Sat Mar 30 20:25:02 2019 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e16e created at Sat Mar 30 20:29:33 2019 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: rpmdbNextIterator: skipping h# 1476 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 101101 (2d)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1477 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1011001 (59)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1478 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1101010 (6a)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1479 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1011011 (5b)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1481 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110000 (70)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 0a9d created at Fri Apr 19 20:07:12 2019 invalid: signature is not alive because: Expired on 2019-05-19T20:07:12Z error: rpmdbNextIterator: skipping h# 1482 Header V4 DSA/SHA1 Signature, key ID 8777be32: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1483 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111110 (3e)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature cff9 created at Fri Apr 19 19:56:29 2019 invalid: signature is not alive because: Expired on 2019-05-19T19:56:29Z error: rpmdbNextIterator: skipping h# 1484 Header V4 DSA/SHA1 Signature, key ID c5171619: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1485 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110 (6)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1486 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1010111 (57)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1489 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1111101 (7d)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1490 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 100001 (21)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1502 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1010010 (52)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1505 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 101010 (2a)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 8dfd created at Sun Jul 17 09:28:54 2016 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature fe54 created at Sun Jul 16 15:03:03 2017 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: rpmdbNextIterator: skipping h# 1512 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 100001 (21)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1513 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1111000 (78)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1514 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1000 (8)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1519 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110101 (75)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 603a created at Mon May 30 20:47:31 2011 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 8fc8 created at Sat Apr 27 23:02:21 2019 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: rpmdbNextIterator: skipping h# 1529 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1011110 (5e)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1532 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1100000 (60)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1534 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1101101 (6d)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature e9c3 created at Wed May 4 11:29:09 2016 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature d3de created at Sat Apr 18 17:04:29 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 7b0e created at Sat Oct 15 20:41:33 2016 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 7c95 created at Sat Mar 28 18:38:55 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: rpmdbNextIterator: skipping h# 1570 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 10110 (16)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 2253 created at Sun Jun 9 22:25:41 2019 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: rpmdbNextIterator: skipping h# 1574 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110101 (75)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1575 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1010010 (52)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1576 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1000000 (40)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1577 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 11010 (1a)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1578 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 101100 (2c)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1579 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1011111 (5f)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1586 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110010 (72)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1587 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 100110 (26)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1635 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110001 (71)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1636 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 10011 (13)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1643 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1111110 (7e)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1656 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1001111 (4f)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature ea2f created at Wed Oct 24 07:35:54 2018 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 1952 created at Wed Oct 24 07:35:54 2018 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: rpmdbNextIterator: skipping h# 1668 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1100000 (60)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1678 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 101101 (2d)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1679 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111000 (38)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1699 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111110 (3e)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1700 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 10110 (16)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 5f6d created at Sat Sep 14 04:08:54 2019 invalid: signature is not alive because: Expired on 2019-10-14T04:08:54Z error: rpmdbNextIterator: skipping h# 1705 Header V4 DSA/SHA1 Signature, key ID 366a484c: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1706 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 101110 (2e)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1707 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111101 (3d)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1713 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1001100 (4c)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1714 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1100110 (66)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 2f6e created at Wed Oct 9 18:43:58 2019 invalid: signature is not alive because: Expired on 2019-11-08T18:43:58Z error: rpmdbNextIterator: skipping h# 1727 Header V4 DSA/SHA1 Signature, key ID f1e8be84: BAD Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 7867 created at Thu Oct 17 08:45:11 2019 invalid: signature is not alive because: Expired on 2019-11-16T08:45:11Z error: rpmdbNextIterator: skipping h# 1741 Header V4 DSA/SHA1 Signature, key ID 0f6520b1: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1742 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110001 (31)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1743 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1000001 (41)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1744 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 11000 (18)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1745 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1011000 (58)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1749 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1100011 (63)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1750 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1111111 (7f)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1767 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1000001 (41)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 41d5 created at Fri Oct 18 00:01:42 2019 invalid: signature is not alive because: Expired on 2019-11-17T00:01:42Z error: rpmdbNextIterator: skipping h# 1772 Header V4 DSA/SHA1 Signature, key ID 80a4f38b: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1773 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111010 (3a)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1774 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 101010 (2a)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1777 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1100011 (63)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1778 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1111100 (7c)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1779 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 101110 (2e)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature ef23 created at Fri Feb 26 07:32:26 2016 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature a448 created at Sat Mar 28 17:59:29 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: rpmdbNextIterator: skipping h# 1788 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 10001 (11)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature d54a created at Sun Oct 20 12:20:14 2019 invalid: signature is not alive because: Expired on 2019-11-19T12:20:14Z error: rpmdbNextIterator: skipping h# 1793 Header V4 DSA/SHA1 Signature, key ID 43d667ee: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1795 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1111101 (7d)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1796 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 100100 (24)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 97a0 created at Wed Oct 23 06:46:15 2019 invalid: signature is not alive because: Expired on 2019-11-22T06:46:15Z error: rpmdbNextIterator: skipping h# 1800 Header V4 DSA/SHA1 Signature, key ID f9b86c17: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1801 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 11000 (18)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1802 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110110 (36)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1803 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110110 (36)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1806 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1001000 (48)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1807 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1100 (c)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 2530 created at Mon Oct 28 01:06:49 2019 invalid: signature is not alive because: Expired on 2019-11-27T01:06:49Z error: rpmdbNextIterator: skipping h# 1816 Header V4 DSA/SHA1 Signature, key ID b6b5e511: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1874 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1010110 (56)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1902 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1010111 (57)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1950 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1000010 (42)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1951 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1101001 (69)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1952 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1101001 (69)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 1955 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110100 (74)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 25a1 created at Wed Dec 23 00:37:50 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature f5b7 created at Wed Oct 24 07:51:14 2018 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: rpmdbNextIterator: skipping h# 2040 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1011 (b)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 2071 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1011101 (5d)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 2072 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1101110 (6e)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 2077 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 10 (2)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 2078 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1011100 (5c)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 699a created at Wed Nov 6 13:59:15 2019 invalid: signature is not alive because: Expired on 2019-12-06T13:59:15Z error: rpmdbNextIterator: skipping h# 2080 Header V4 DSA/SHA1 Signature, key ID b2597e79: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 2081 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 10111 (17)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 873c created at Sun Nov 17 18:44:20 2019 invalid: signature is not alive because: Expired on 2019-12-17T18:44:20Z error: rpmdbNextIterator: skipping h# 2096 Header V4 DSA/SHA1 Signature, key ID d683af5f: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 2110 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110 (e)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 2111 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1111101 (7d)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 2113 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1000000 (40)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 2114 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1000111 (47)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 6aca created at Sun Dec 1 08:42:28 2019 invalid: signature is not alive because: Expired on 2019-12-31T08:42:28Z error: rpmdbNextIterator: skipping h# 2115 Header V4 DSA/SHA1 Signature, key ID 97ada44d: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 2116 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1010 (a)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 2117 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1011011 (5b)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 2418 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1010111 (57)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 2575 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 11101 (1d)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 2576 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1111010 (7a)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 2577 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1001111 (4f)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 2595 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1000100 (44)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 4af8 created at Wed May 4 11:31:19 2016 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature b91e created at Tue Feb 25 12:52:35 2020 invalid: signature is not alive because: Expired on 2020-03-26T12:52:35Z error: rpmdbNextIterator: skipping h# 2658 Header V4 DSA/SHA1 Signature, key ID f6bb5dac: BAD Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature ba88 created at Tue Feb 25 12:52:44 2020 invalid: signature is not alive because: Expired on 2020-03-26T12:52:44Z error: rpmdbNextIterator: skipping h# 2659 Header V4 DSA/SHA1 Signature, key ID f6bb5dac: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 2681 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1101011 (6b)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 2682 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111 (7)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 2683 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 10011 (13)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 2684 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111000 (38)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 2685 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1001100 (4c)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 2686 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111101 (3d)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 2687 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1011000 (58)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 2689 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1001 (9)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 2690 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111 (7)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 2691 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110101 (35)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 2692 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1000000 (40)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 2705 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 10101 (15)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 2713 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111110 (3e)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 2714 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 101100 (2c)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 2715 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111110 (3e)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 2716 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110111 (37)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 2723 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 10111 (17)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 2726 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1011100 (5c)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 2731 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110111 (37)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 2761 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1100011 (63)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 2772 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1100101 (65)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 1a34 created at Sun Apr 17 11:18:24 2016 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: rpmdbNextIterator: skipping h# 2786 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110101 (75)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 2787 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 100000 (20)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 2788 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1010 (a)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 2789 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1001001 (49)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 2827 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1011011 (5b)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 7c1e created at Sun Apr 17 11:51:35 2016 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ade0 created at Sun Apr 17 11:51:35 2016 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: rpmdbNextIterator: skipping h# 2901 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 11111 (1f)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 2902 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1001111 (4f)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature e857 created at Wed Apr 1 04:31:23 2020 invalid: signature is not alive because: Expired on 2020-05-01T04:31:23Z error: rpmdbNextIterator: skipping h# 2903 Header V4 DSA/SHA1 Signature, key ID eb015b31: BAD Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 3b19 created at Fri Mar 27 00:54:01 2020 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature b6a4 created at Fri Mar 27 00:54:01 2020 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 32f3 created at Fri Mar 27 00:37:28 2020 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: rpmdbNextIterator: skipping h# 2919 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1111 (f)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 2920 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 10100 (14)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 2940 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 101001 (29)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature c659 created at Fri Sep 6 21:35:20 2019 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: rpmdbNextIterator: skipping h# 3010 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 100110 (26)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 44b9 created at Sat Mar 14 12:04:22 2020 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 8bc5 created at Sat Mar 14 12:04:21 2020 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: rpmdbNextIterator: skipping h# 3085 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111011 (3b)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 3086 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 11110 (1e)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 3101 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1010000 (50)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 3102 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1001100 (4c)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 3105 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 100101 (25)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 3106 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110001 (31)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 3107 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110110 (36)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 3118 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111000 (38)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 3119 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1100111 (67)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 3128 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1100110 (66)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 3129 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110010 (32)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 3132 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110010 (32)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 3133 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110 (e)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 3217 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1100111 (67)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 3218 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1111111 (7f)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 3219 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1010011 (53)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 3220 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1011101 (5d)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 3228 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 11100 (1c)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 3262 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1111110 (7e)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 3306 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110110 (36)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 3307 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1101100 (6c)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 3310 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111000 (38)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 3311 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 101 (5)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 3312 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1100101 (65)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 3313 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 11100 (1c)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 3317 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1000 (8)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 3318 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110000 (70)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 3330 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1001000 (48)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 3331 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1111101 (7d)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 3371 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110100 (34)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 3372 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1100100 (64)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 3373 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1100100 (64)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 3374 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 11110 (1e)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 3390 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1100 (c)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 3391 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1010111 (57)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 3426 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1100001 (61)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 3427 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110101 (35)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 3444 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 11 (3)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 3445 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1111110 (7e)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 3628 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110010 (32)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 3629 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 100000 (20)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 3646 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1101100 (6c)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 3647 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1010100 (54)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 3652 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1111001 (79)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 3653 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 101110 (2e)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 3661 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 11010 (1a)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 3662 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1111000 (78)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 3664 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1000000 (40)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 3665 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1010010 (52)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 3671 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110 (6)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 3672 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110101 (75)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 8c3d created at Mon Jun 8 19:53:27 2020 invalid: signature is not alive because: Expired on 2020-07-08T19:53:27Z error: rpmdbNextIterator: skipping h# 3696 Header V4 DSA/SHA1 Signature, key ID 71d508e7: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 3799 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1101111 (6f)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature d37c created at Fri Apr 14 16:43:05 2017 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: rpmdbNextIterator: skipping h# 3854 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 100110 (26)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 3855 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 11000 (18)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 3943 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 11000 (18)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 3944 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1111100 (7c)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 3993 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1001000 (48)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 3994 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1010 (a)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature c689 created at Sat Mar 28 19:37:23 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: rpmdbNextIterator: skipping h# 4067 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1111010 (7a)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 4111 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1001001 (49)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 4112 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 11011 (1b)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 0e54 created at Wed Aug 26 14:42:27 2020 invalid: signature is not alive because: Expired on 2020-09-25T14:42:27Z error: rpmdbNextIterator: skipping h# 4168 Header V4 DSA/SHA1 Signature, key ID 576a8a09: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 4208 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1100011 (63)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 4217 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111111 (3f)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 4220 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1101010 (6a)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 4221 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 10011 (13)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 4248 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1111100 (7c)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 4249 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 10010 (12)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 4250 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111101 (3d)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 4296 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110010 (72)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 521b created at Tue Sep 8 17:39:22 2020 invalid: signature is not alive because: Expired on 2020-10-08T17:39:22Z error: rpmdbNextIterator: skipping h# 4297 Header V4 DSA/SHA1 Signature, key ID cd74e354: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 4426 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1011000 (58)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 4428 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 100110 (26)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 4429 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110001 (71)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 4432 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1101000 (68)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 4450 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1100001 (61)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 4452 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1000101 (45)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 4502 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1101011 (6b)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 4524 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111110 (3e)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 4525 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 100101 (25)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 4560 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1011001 (59)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 4809 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110011 (33)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 4810 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1010001 (51)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 4838 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1010100 (54)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 4839 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1101101 (6d)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 4843 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1111111 (7f)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 4858 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1000111 (47)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 30e4 created at Thu Oct 22 06:58:10 2020 invalid: signature is not alive because: Expired on 2020-11-21T06:58:10Z error: rpmdbNextIterator: skipping h# 4859 Header V4 DSA/SHA1 Signature, key ID 82ff3f1a: BAD Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature d3ce created at Thu Oct 22 08:24:34 2020 invalid: signature is not alive because: Expired on 2020-11-21T08:24:34Z error: rpmdbNextIterator: skipping h# 4862 Header V4 DSA/SHA1 Signature, key ID d4fb0eb6: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 4893 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1101010 (6a)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 4898 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1000111 (47)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 4899 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 100111 (27)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 4917 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1000 (8)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 4976 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 100011 (23)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 4995 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1010001 (51)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 4996 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 10100 (14)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 4997 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1 (1)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 4998 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111110 (3e)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 5001 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 10011 (13)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 5002 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111011 (3b)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 5031 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1011010 (5a)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 5061 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110011 (73)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 5062 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1100001 (61)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 5695 created at Tue Nov 24 20:38:50 2020 invalid: signature is not alive because: Expired on 2020-12-24T20:38:50Z error: rpmdbNextIterator: skipping h# 5064 Header V4 DSA/SHA1 Signature, key ID c2704482: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 5097 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1011110 (5e)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 5211 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1011000 (58)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 5221 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1100000 (60)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 5223 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 100110 (26)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 5247 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1010010 (52)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 5355 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1101 (d)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 5356 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1010100 (54)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 2efe created at Wed Dec 30 19:24:46 2020 invalid: signature is not alive because: Expired on 2021-01-29T19:24:46Z error: rpmdbNextIterator: skipping h# 5378 Header V4 DSA/SHA1 Signature, key ID 7a3d177f: BAD Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature bbc1 created at Sat Jan 2 09:58:27 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: rpmdbNextIterator: skipping h# 5455 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 11000 (18)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 5456 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1001111 (4f)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 5460 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 11100 (1c)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 0e7f created at Sun Jan 3 16:53:22 2021 invalid: signature is not alive because: Expired on 2021-02-02T16:53:22Z error: rpmdbNextIterator: skipping h# 5461 Header V4 DSA/SHA1 Signature, key ID e88ceaff: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 5513 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111 (7)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 5618 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 10001 (11)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 5619 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 101100 (2c)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 05ff created at Sun Jan 17 10:32:46 2021 invalid: signature is not alive because: Expired on 2021-02-16T10:32:46Z error: rpmdbNextIterator: skipping h# 5620 Header V4 DSA/SHA1 Signature, key ID 6bb2f2cb: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 5621 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 101 (5)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 5622 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1101001 (69)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 5624 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111100 (3c)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 6d25 created at Sat Mar 28 18:39:08 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: rpmdbNextIterator: skipping h# 5653 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110011 (73)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 5654 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1011101 (5d)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 8cf5 created at Wed Oct 24 07:31:06 2018 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9b06 created at Wed Oct 24 07:00:27 2018 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature b8a7 created at Fri Apr 14 16:36:44 2017 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 1cf7 created at Sat Aug 1 14:32:31 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: rpmdbNextIterator: skipping h# 5795 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 101110 (2e)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 5796 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1010110 (56)) Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 5955 Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet: Failed to parse Signature Packet because: Signature appears to be created by a non-conformant OpenPGP implementation, see . because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110011 (73)) Header SHA1 digest: OK error: Verifying a signature, but no certificate was provided: Signature 5730 created at Sun Aug 27 07:54:58 2017 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 8544 created at Sun Oct 8 21:13:45 2017 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature eac2 created at Wed Dec 23 00:41:12 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature de60 created at Wed Dec 23 00:40:55 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 91ba created at Tue Dec 27 12:55:14 2016 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature f33a created at Sat Aug 1 14:41:48 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature da54 created at Tue Aug 21 22:32:38 2018 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 8374 created at Wed Jul 24 23:34:10 2013 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3071 created at Sun Feb 9 09:28:21 2014 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature c920 created at Wed Nov 24 12:03:36 2010 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e4d9 created at Wed Nov 20 19:33:54 2013 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 2185 created at Wed Nov 20 19:31:31 2013 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 68d5 created at Sun May 17 10:03:33 2020 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 8dc6 created at Sun May 17 10:03:33 2020 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ba7d created at Sun Feb 9 09:27:25 2014 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 35b1 created at Fri Sep 5 07:15:11 2014 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature dabf created at Tue Oct 28 11:09:10 2014 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ab24 created at Sun Feb 9 09:27:06 2014 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature a33b created at Fri Jan 20 10:14:33 2012 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ad74 created at Mon May 30 20:44:51 2011 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 186c created at Sun Feb 9 09:39:05 2014 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 2ea4 created at Wed Apr 28 17:46:54 2010 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 8b78 created at Fri Mar 27 00:54:53 2020 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature feec created at Fri Mar 27 00:50:48 2020 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature b080 created at Fri Mar 27 00:53:14 2020 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 7f90 created at Mon Nov 9 21:01:56 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature b423 created at Mon Nov 9 21:01:56 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 95d8 created at Thu May 7 20:28:58 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 5a70 created at Thu May 7 20:28:58 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature f60b created at Sat Jul 17 22:32:39 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature b46a created at Fri Apr 14 16:43:51 2017 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 7551 created at Sat Aug 31 07:57:20 2019 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature caaf created at Mon Oct 19 13:17:13 2020 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 49ed created at Sun May 10 12:00:28 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e3fe created at Sun Apr 17 12:30:14 2016 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 0af7 created at Tue Oct 28 11:10:17 2014 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 755b created at Fri Mar 27 00:36:10 2020 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z rpm-specdump-0.8-2.x32 error: Verifying a signature, but no certificate was provided: Signature b049 created at Sun Apr 17 12:31:27 2016 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9c87 created at Tue Apr 20 07:07:01 2010 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 1d94 created at Wed Feb 17 08:11:12 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 843c created at Wed Apr 28 17:46:56 2010 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9196 created at Sun Feb 9 09:26:53 2014 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ed1f created at Sun May 20 18:37:49 2012 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 8781 created at Sun Mar 5 11:26:54 2017 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9094 created at Tue Oct 28 11:03:45 2014 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature d7c9 created at Wed Jun 2 17:16:45 2010 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 4449 created at Sun Nov 21 15:21:01 2010 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature a750 created at Sat Jul 12 10:59:45 2014 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 59d5 created at Sat Aug 1 14:37:04 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature edff created at Sat Feb 1 08:55:45 2014 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 33c0 created at Wed Jul 24 23:38:54 2013 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 0783 created at Wed Oct 26 16:20:22 2011 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ce9a created at Sun Mar 14 20:17:57 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 6f9b created at Sun Aug 23 18:54:35 2020 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9910 created at Sat Jan 2 10:00:32 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 0d70 created at Sat Oct 30 09:44:32 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 35d5 created at Tue Sep 21 00:56:52 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature fa75 created at Tue Sep 21 00:56:49 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 62d3 created at Sun Mar 14 21:06:25 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 8114 created at Thu Apr 1 20:00:02 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 7152 created at Thu Apr 1 20:00:02 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 0270 created at Wed Dec 23 00:39:23 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e98a created at Sun Aug 23 18:53:35 2020 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 2ac6 created at Sat Oct 30 09:33:53 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature db2b created at Sat Oct 30 09:33:52 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature d62e created at Tue Dec 5 07:49:20 2017 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 885b created at Sat May 27 06:40:17 2017 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature a45d created at Sun Dec 13 23:25:51 2020 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature d36a created at Wed Oct 24 08:05:44 2018 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 871a created at Sat Mar 28 19:00:55 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e87a created at Wed Oct 24 07:48:56 2018 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 284e created at Sat Jan 2 10:11:51 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 8f99 created at Sun May 17 10:16:19 2020 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 90b9 created at Wed Oct 24 08:07:01 2018 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature b03d created at Sat Mar 28 19:02:52 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 61e8 created at Sat Jul 17 22:32:48 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 7418 created at Sun Dec 13 23:24:48 2020 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 1a9c created at Sun Dec 13 23:40:34 2020 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature c45d created at Sat Sep 28 17:55:24 2019 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 28be created at Sat Mar 28 20:44:17 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3f2f created at Thu Mar 19 21:24:55 2020 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 6c99 created at Mon May 24 10:06:49 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3c51 created at Sat Mar 28 17:42:41 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 5130 created at Sat Mar 28 18:00:44 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9d01 created at Sat Mar 28 18:38:01 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature c274 created at Mon Dec 31 18:41:11 2018 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature eb99 created at Sun Sep 18 21:06:07 2016 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 1ec9 created at Sat Mar 28 17:44:37 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature b5a6 created at Sat Mar 28 19:59:05 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3128 created at Sat May 27 06:39:03 2017 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 095d created at Sat Mar 28 18:00:40 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9ee5 created at Sat Apr 18 19:24:00 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 5bb2 created at Sun Dec 13 23:29:17 2020 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 2cf7 created at Sat Mar 28 17:42:52 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 0d04 created at Sat Mar 30 20:48:08 2019 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 7810 created at Tue Aug 21 22:17:57 2018 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature b882 created at Thu Jul 9 21:00:36 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature b266 created at Sun Jun 9 22:55:23 2019 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 4879 created at Sun Nov 26 22:23:11 2017 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature adca created at Mon Mar 26 09:44:47 2018 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 5d9f created at Sun Mar 14 21:14:20 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3810 created at Mon Nov 4 08:37:59 2019 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 1e15 created at Tue Oct 6 15:34:01 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e146 created at Thu Jul 9 20:53:56 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 7124 created at Thu May 24 11:59:33 2018 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e864 created at Thu May 24 12:30:27 2018 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature af5a created at Sun Jun 9 23:29:14 2019 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature a6ac created at Sun Jul 2 15:37:02 2017 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 8e89 created at Sun Mar 14 20:33:13 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 6376 created at Sun Mar 14 20:45:25 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 0d45 created at Tue Sep 21 00:33:30 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9b9b created at Sun May 10 11:54:13 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 2122 created at Wed Mar 2 19:20:22 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 1a17 created at Wed Mar 2 19:20:22 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 4751 created at Wed May 4 11:27:50 2016 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature efaa created at Sat Dec 11 01:06:46 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature befb created at Fri Mar 27 00:37:28 2020 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 38aa created at Sun Apr 10 01:40:14 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 79d8 created at Mon Dec 31 18:41:57 2018 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 670f created at Sun Apr 10 01:10:21 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 2e58 created at Sun Mar 5 11:02:09 2017 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 5791 created at Fri Mar 27 00:51:16 2020 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 777d created at Thu Jun 22 01:37:00 2017 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 1581 created at Fri Mar 27 00:43:58 2020 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 20d4 created at Fri Mar 27 00:37:12 2020 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 410b created at Sat Jan 2 18:33:49 2016 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature d568 created at Thu Jun 22 00:53:48 2017 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 23db created at Fri Mar 27 00:49:54 2020 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature af97 created at Fri Mar 27 00:49:02 2020 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 50ae created at Fri Mar 27 00:51:38 2020 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature dd57 created at Sun Apr 10 01:03:43 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature f89b created at Sun Apr 10 01:03:43 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 05d9 created at Mon Nov 9 21:17:32 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 8c9b created at Mon May 24 10:17:41 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 695a created at Sun Apr 10 00:30:08 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 366a created at Sun Apr 10 01:20:08 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 1040 created at Wed Mar 2 07:36:29 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature c741 created at Sun Apr 10 01:44:21 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature f0c2 created at Sun Apr 10 01:44:22 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 7722 created at Sun Apr 10 00:40:05 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature d199 created at Sun Apr 10 01:35:11 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9c7a created at Sun Apr 10 01:48:14 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 50cc created at Sat Apr 9 23:56:26 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature c79a created at Wed Oct 24 07:06:59 2018 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature c6ff created at Mon Oct 19 13:12:48 2020 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 323b created at Wed May 4 11:40:02 2016 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3399 created at Sun Feb 11 16:42:56 2018 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 7177 created at Sat Oct 30 09:14:35 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature b021 created at Sun Apr 10 00:08:43 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 6825 created at Thu Jul 9 20:49:27 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 63e3 created at Sun Apr 10 01:24:19 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature bfd3 created at Sun Apr 10 01:24:19 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature d0b1 created at Sun Jun 9 23:06:00 2019 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature c4df created at Sun Apr 10 00:38:57 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 7911 created at Sun Apr 10 00:38:57 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 8a7e created at Wed Feb 17 07:53:14 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 49d0 created at Sat Jul 25 11:20:20 2020 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 4450 created at Sun Apr 10 01:21:11 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 01c7 created at Sat Aug 1 14:38:03 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 399e created at Tue Aug 21 22:27:42 2018 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 8870 created at Tue Aug 21 22:27:41 2018 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature c69c created at Sun Apr 10 01:04:00 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 2216 created at Sat Dec 11 01:09:55 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 2706 created at Sat Dec 11 01:09:56 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 075d created at Sat Mar 28 17:55:48 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 45ca created at Mon Oct 19 12:55:10 2020 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3607 created at Mon Oct 19 12:55:10 2020 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 0188 created at Mon Oct 19 12:55:09 2020 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9ffc created at Sat Mar 28 20:18:56 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 1e7f created at Sun Jun 12 21:26:31 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 52fb created at Sun Jun 12 21:26:32 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 32cd created at Mon Jul 4 23:18:08 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 7780 created at Mon Jul 4 23:18:08 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature fca0 created at Sun May 17 10:02:22 2020 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 221f created at Sun Dec 13 23:35:17 2020 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 0edd created at Sun Dec 13 23:35:17 2020 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature f6c5 created at Sun Dec 13 23:41:39 2020 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9a27 created at Sun Aug 29 00:21:47 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3972 created at Sat Mar 28 17:46:30 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature a60e created at Sat Mar 28 17:54:51 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9ff3 created at Thu Mar 24 00:04:05 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ae39 created at Sat Mar 28 17:38:14 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3dda created at Sat Mar 28 17:38:14 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3efa created at Tue Apr 20 21:44:57 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 730a created at Tue Apr 20 21:44:57 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9b3a created at Thu Mar 24 00:04:05 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature fa89 created at Sat Oct 26 15:36:02 2019 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature aa96 created at Wed Feb 17 07:51:39 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9a24 created at Wed Feb 17 07:51:39 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ce10 created at Thu Mar 24 00:04:05 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature a144 created at Thu Mar 24 00:04:04 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature d748 created at Sat Mar 28 17:44:39 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 071f created at Sat Mar 28 17:44:39 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 8957 created at Sun Apr 10 01:11:20 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature a691 created at Fri Feb 26 07:41:23 2016 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 50df created at Fri Feb 26 07:41:23 2016 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature b149 created at Sun Apr 10 00:00:19 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 8780 created at Sun Apr 10 00:29:35 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 901b created at Sat Sep 24 09:01:01 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature b62b created at Sat Sep 24 09:01:01 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature efe5 created at Sat Sep 24 09:01:01 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature bebd created at Sun Oct 30 10:15:32 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 654d created at Sat Jul 25 11:08:01 2020 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature b6a4 created at Sun Apr 10 01:27:55 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 0e62 created at Sun Apr 10 01:04:33 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature f17f created at Sun Aug 14 12:21:43 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature b791 created at Sun Aug 14 12:21:43 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature a402 created at Sun Jun 12 21:26:32 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature af70 created at Sun Aug 14 12:06:35 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 0132 created at Sun Nov 24 18:12:40 2019 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 7e41 created at Sat Oct 30 10:47:16 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 34f9 created at Sat Oct 30 10:47:16 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9aeb created at Sun Apr 22 11:52:46 2018 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 98f6 created at Wed Dec 23 00:37:38 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature d616 created at Wed Dec 23 00:37:38 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3178 created at Tue Aug 21 22:32:37 2018 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 71ca created at Sat Apr 18 17:02:51 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 964c created at Sat Apr 18 17:02:51 2015 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 125c created at Fri Mar 27 00:53:09 2020 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature f002 created at Sun Feb 26 11:57:10 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 61c3 created at Sun Feb 26 13:37:21 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 45cf created at Sun Feb 26 14:23:10 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature c782 created at Sun Apr 10 01:38:07 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3f39 created at Sun Aug 28 21:17:07 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 8eec created at Sun Aug 28 21:17:08 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature df6f created at Wed Mar 15 20:14:40 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 0054 created at Sun Apr 10 00:40:04 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 7ab1 created at Sun May 22 16:28:04 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9061 created at Sun Apr 10 00:48:53 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e589 created at Thu Jul 14 06:52:40 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature bb2b created at Wed Mar 15 17:47:35 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 47f2 created at Wed Mar 15 20:07:29 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature d818 created at Wed Mar 15 20:18:41 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e20c created at Wed Mar 15 20:01:32 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature fceb created at Sun Feb 26 14:12:46 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 108a created at Mon Dec 19 00:42:38 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature d0ff created at Mon Dec 19 00:42:39 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 2cda created at Sun Feb 26 14:12:46 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 4b7d created at Wed Mar 15 20:28:49 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 8882 created at Wed Mar 15 20:28:49 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 1cff created at Wed Mar 15 20:23:35 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3d46 created at Wed Mar 15 20:23:34 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 1b68 created at Sun Feb 26 14:14:31 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature cedd created at Sun Feb 26 14:14:31 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 51d9 created at Thu Mar 24 00:02:14 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 89b6 created at Wed Mar 15 20:22:59 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 1127 created at Sat Sep 24 08:35:48 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 5936 created at Wed Mar 15 20:22:59 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e27c created at Sun Feb 26 13:08:08 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 6e09 created at Sun Feb 26 13:08:08 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ac3a created at Sat Sep 24 08:27:22 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 1001 created at Sat Sep 24 08:27:23 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ea83 created at Sat Apr 1 23:52:25 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 4890 created at Sat Apr 1 23:52:25 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature f2e3 created at Sun Feb 26 11:39:32 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 27ce created at Sun Feb 26 11:39:33 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 7167 created at Sun Oct 30 10:51:55 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature b789 created at Sun Oct 30 10:42:51 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 6167 created at Sun Oct 30 10:32:28 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 036b created at Sun Oct 30 10:16:38 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 7f77 created at Sun Oct 30 10:16:38 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature f902 created at Sun Oct 30 10:32:28 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 4a74 created at Sun Oct 30 10:42:51 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 59ca created at Sun Oct 30 10:51:56 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature d122 created at Wed Mar 15 20:46:08 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 8a36 created at Mon Mar 14 08:43:06 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 010a created at Wed Mar 15 20:25:50 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature c3c7 created at Wed Mar 15 20:50:23 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9fa5 created at Wed Mar 15 20:25:55 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 2d0a created at Mon May 24 11:14:47 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 6629 created at Wed Mar 15 20:46:48 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 613e created at Mon Mar 14 08:43:06 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 09dd created at Sun Oct 30 10:37:05 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 1178 created at Sun Oct 30 10:37:04 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature b7db created at Wed Mar 15 20:38:04 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 67ed created at Sun Apr 10 00:18:27 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature a7dc created at Sun Apr 10 01:13:46 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature f947 created at Sun Feb 26 13:07:33 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature cd57 created at Sat Dec 11 01:16:26 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 813e created at Sun May 22 15:39:10 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 6dd0 created at Wed Mar 15 20:30:08 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature c611 created at Wed Mar 15 20:56:12 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 673f created at Wed Mar 15 20:56:13 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 8344 created at Sat Apr 1 23:53:24 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3b70 created at Wed Mar 15 20:48:53 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature efcb created at Wed Mar 15 20:47:15 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature f113 created at Wed Mar 15 20:14:26 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature f697 created at Wed Mar 15 19:59:16 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature aa05 created at Mon Dec 19 00:15:50 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3fa0 created at Sun Aug 29 00:16:13 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 970e created at Sat Oct 30 10:56:27 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 85fd created at Sat Oct 30 10:56:27 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 4998 created at Fri Jun 9 21:02:44 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ff33 created at Wed Mar 15 20:25:09 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 0187 created at Sat Sep 24 09:22:01 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 48a5 created at Sat Jun 10 23:36:59 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 688c created at Wed Mar 15 20:34:13 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 651d created at Wed Mar 15 20:01:40 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 26c6 created at Wed Mar 15 20:14:57 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e02b created at Wed Mar 15 20:12:31 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ec8d created at Sun Feb 26 14:02:46 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 80b4 created at Sat Sep 24 08:46:55 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 8eaf created at Wed Mar 15 20:01:25 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 042a created at Sat Sep 24 08:46:54 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature a9fb created at Wed Mar 15 20:21:30 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature b155 created at Wed Mar 15 20:22:36 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature bbb6 created at Sat Sep 24 09:22:01 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 624e created at Sat Dec 11 01:18:45 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ec93 created at Sat Dec 11 01:18:46 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 4c30 created at Sun Apr 10 01:43:33 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 0ca1 created at Sat Apr 1 23:26:18 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 180f created at Sat Aug 28 23:31:44 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 76f8 created at Sat Aug 28 23:31:44 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3357 created at Wed Mar 15 20:06:02 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 28f7 created at Wed Mar 15 20:12:42 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 5f58 created at Wed Mar 15 20:20:47 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 49f8 created at Sun Feb 26 13:06:59 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature d672 created at Sun Feb 26 13:06:58 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ee3b created at Sun Apr 10 00:47:46 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature d2a6 created at Sat Sep 24 08:36:30 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature d754 created at Sat Sep 24 08:36:30 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature fd8e created at Wed Mar 15 20:46:40 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature d47c created at Wed Mar 15 20:46:18 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 1643 created at Wed Mar 15 20:45:24 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 1478 created at Wed Mar 15 20:45:24 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 8010 created at Wed Mar 15 20:26:42 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9f2e created at Sun Apr 10 01:35:19 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 483f created at Sat Aug 28 23:31:41 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 1015 created at Wed Mar 15 20:32:54 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3c51 created at Sun Apr 10 01:34:02 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ffb1 created at Wed Mar 15 20:29:38 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9486 created at Wed Mar 15 20:55:09 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature c182 created at Wed Mar 15 20:25:36 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9411 created at Mon Apr 25 21:55:41 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 926a created at Mon Apr 25 21:55:42 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 6490 created at Sun Jun 11 00:20:51 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 7313 created at Sat Jul 17 22:41:03 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 17c7 created at Wed Mar 15 20:01:28 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature aa25 created at Wed Mar 15 20:49:35 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 18bf created at Wed Mar 15 20:10:40 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature d55a created at Wed Mar 15 20:22:15 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 4b4c created at Wed Mar 15 20:02:39 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 6095 created at Wed Mar 15 20:02:38 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 8962 created at Wed Mar 15 20:37:19 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e362 created at Wed Mar 15 20:56:31 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 4851 created at Wed Mar 15 20:51:58 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature f794 created at Wed Mar 15 20:56:26 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature afd8 created at Wed Mar 15 20:05:19 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ef0b created at Wed Mar 15 20:08:02 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 5010 created at Sun Apr 10 01:21:11 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 74c9 created at Wed Mar 15 20:22:30 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e9c0 created at Mon Apr 25 21:38:18 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature db0f created at Mon Apr 25 21:38:19 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 2f5b created at Mon Apr 25 21:38:17 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature aff8 created at Sun Feb 26 12:29:09 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e8ae created at Sun Apr 10 01:26:51 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 1600 created at Sun Mar 14 20:06:20 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 520e created at Sun Mar 14 20:51:44 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 4bae created at Wed Mar 15 20:44:15 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 0102 created at Wed Mar 15 20:53:55 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 5dba created at Wed Mar 15 20:53:56 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 25f0 created at Sat Jun 10 23:35:19 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature d181 created at Sat Jun 10 23:36:59 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9822 created at Sun Apr 10 01:09:12 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 1f7c created at Sat Apr 15 20:02:07 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 855d created at Wed Mar 15 20:47:23 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature a086 created at Wed Mar 15 20:47:22 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 484a created at Sun Oct 30 10:37:08 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ce6b created at Sun Oct 30 10:37:08 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 5952 created at Wed Mar 15 20:22:17 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 180e created at Sat Jun 10 20:49:32 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9938 created at Wed Mar 15 20:22:56 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 8897 created at Sat Apr 1 23:02:39 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature a4d9 created at Sun Aug 28 21:50:45 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 5c81 created at Tue Nov 30 00:47:39 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 8936 created at Wed Mar 15 20:05:06 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 6daf created at Sun Feb 26 13:07:33 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature b2be created at Sat Apr 1 23:53:23 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ab3f created at Sat Jun 10 20:43:05 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 7bf3 created at Sat Jun 10 20:43:06 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature bcdf created at Wed Mar 15 20:25:05 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature bf68 created at Sun Jan 23 18:00:57 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e947 created at Sun Jan 23 18:00:57 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 7884 created at Sun Apr 10 00:36:07 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 1222 created at Sun Feb 26 14:05:57 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 55a7 created at Wed Mar 15 09:21:31 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e710 created at Wed Mar 15 20:14:15 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 238c created at Wed Mar 15 20:14:14 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 6cc3 created at Wed Mar 15 20:08:21 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9d0e created at Tue Aug 1 22:20:07 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 8592 created at Tue Aug 1 22:20:06 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 4766 created at Sun Apr 10 01:25:12 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 7b08 created at Mon Jul 4 23:14:16 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature b462 created at Sun Aug 3 19:41:07 2008 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 58ff created at Wed Mar 15 20:45:10 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature afc0 created at Wed Mar 15 20:49:10 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 21a5 created at Tue Aug 1 21:26:15 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 59b6 created at Fri Sep 8 10:35:58 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 2b6d created at Tue Aug 1 23:12:19 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature a869 created at Tue Aug 1 22:45:04 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature a86c created at Fri Dec 23 23:46:14 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 2010 created at Wed Mar 15 20:12:41 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 43b8 created at Sun Apr 10 00:18:53 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e758 created at Sun Feb 26 13:10:12 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 049f created at Sun Apr 10 01:32:55 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature aac6 created at Sun Apr 10 00:56:34 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 97f4 created at Sun Apr 10 00:11:38 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature d5b0 created at Sun Apr 10 01:23:14 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature d4a3 created at Sun Apr 10 01:24:41 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 2710 created at Wed Mar 15 20:18:32 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature aaf1 created at Wed Mar 15 20:00:23 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 4eb8 created at Sun Apr 10 01:43:32 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 803f created at Sat Sep 24 08:17:37 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 048d created at Sat Sep 24 08:17:37 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 8e11 created at Wed Mar 15 20:41:13 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 7793 created at Wed Mar 15 20:06:20 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature cd96 created at Wed Mar 15 20:38:22 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 5072 created at Sat Aug 13 06:04:25 2011 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 4875 created at Sun May 22 15:50:05 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 6d58 created at Sat Dec 11 01:28:23 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 59c7 created at Sun Apr 10 01:04:02 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature f82d created at Sun Feb 26 13:29:53 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature a897 created at Sun Feb 26 13:29:53 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature a1a0 created at Sat Apr 9 23:59:05 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9492 created at Sat Apr 1 23:52:23 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature eaf8 created at Sat Apr 1 23:52:09 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 1da9 created at Sun Apr 10 00:46:03 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature d99f created at Sun Apr 10 00:08:16 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 6496 created at Sun Apr 10 00:07:49 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 90aa created at Sat Apr 9 23:59:56 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 4d66 created at Sat Apr 9 23:57:09 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature db40 created at Sat Apr 9 23:59:56 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 1307 created at Wed Sep 13 13:07:58 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e150 created at Sun Oct 8 12:19:04 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ce4a created at Sun Oct 8 12:19:04 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 4e36 created at Sun Oct 8 12:19:02 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 229a created at Tue Oct 3 03:32:30 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature c0ad created at Wed Sep 13 13:07:43 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 216f created at Wed Sep 13 13:07:43 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 48a0 created at Wed Sep 13 13:07:42 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 5b9e created at Sun Apr 10 00:32:23 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 8bb4 created at Sun Mar 14 20:51:45 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 4bd4 created at Sun Feb 26 14:14:32 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 80b2 created at Sun Apr 10 01:08:49 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature fd60 created at Sun Apr 10 00:25:43 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature b935 created at Sun Apr 10 01:18:40 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e776 created at Sat Apr 9 23:56:26 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature cad7 created at Sun Apr 10 01:11:00 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 526e created at Sun Apr 10 01:33:50 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 2989 created at Fri Feb 18 00:19:08 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 013c created at Fri Feb 18 00:19:07 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature dcf6 created at Wed Mar 15 20:07:10 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature af9c created at Wed Mar 15 20:07:11 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 65be created at Wed Mar 15 20:52:55 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 4eb6 created at Wed Mar 15 20:45:49 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 0018 created at Wed Sep 13 13:09:06 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature bfed created at Wed Mar 15 20:32:40 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e49a created at Sun Jun 12 20:33:13 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 80a3 created at Sat Apr 15 20:55:24 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature df45 created at Sat Apr 15 20:55:25 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature bab4 created at Sat Oct 30 11:13:22 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature d1f3 created at Wed Mar 15 20:13:32 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 92cd created at Wed Mar 15 20:13:33 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 0fd7 created at Sat Apr 9 23:59:05 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature c47d created at Wed Sep 13 13:05:56 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 417a created at Wed Sep 13 13:05:56 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 0187 created at Sun Mar 14 20:59:44 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 6614 created at Sat Dec 11 01:00:53 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature a5d2 created at Sun Apr 10 00:41:21 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 75e5 created at Sun Apr 10 00:40:08 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature f4c9 created at Sun Apr 10 01:30:54 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature bbc1 created at Wed Nov 8 00:43:29 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature dfe5 created at Sun Feb 26 13:37:11 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 2ca9 created at Sun Apr 10 00:31:40 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature c47d created at Wed Nov 8 00:53:10 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature a96c created at Wed Nov 8 00:25:30 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature b612 created at Sat Apr 15 20:55:46 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 44e1 created at Sun Nov 19 22:31:36 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 91e0 created at Sat Sep 24 08:54:11 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 20de created at Sun Apr 10 00:42:29 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 690d created at Sun Apr 10 00:42:29 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9957 created at Sat Dec 11 01:37:11 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 21b1 created at Sat Dec 11 01:37:11 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 6b4a created at Sun Apr 10 01:32:39 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature b32a created at Sat Jun 10 20:55:54 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature d63c created at Wed Mar 15 20:50:22 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 1ccf created at Tue Aug 1 22:05:11 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 7982 created at Thu Mar 24 00:22:21 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 8b6a created at Wed Mar 15 20:01:24 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9459 created at Mon Dec 19 00:50:29 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 0c73 created at Wed Mar 15 20:46:08 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 0bf0 created at Mon May 24 11:14:49 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 79e4 created at Sat Jun 10 22:58:32 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ed9b created at Sat Jun 10 22:58:31 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 7ed5 created at Wed Mar 15 20:48:42 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature c6d1 created at Wed Mar 15 20:47:13 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature cbbf created at Tue Aug 1 21:45:30 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature b971 created at Sun Apr 10 00:18:26 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 5e36 created at Wed Mar 15 20:30:08 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 2292 created at Wed Mar 15 20:16:48 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 69cd created at Wed Mar 15 20:33:20 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 5ecb created at Sun Oct 8 12:18:29 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 340f created at Sat Apr 1 23:53:23 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature fb28 created at Sun Aug 28 21:50:45 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 6eae created at Wed Mar 15 20:22:55 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 7381 created at Sat Apr 1 23:02:39 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature c23d created at Sun Aug 29 00:16:14 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 50b9 created at Mon Dec 19 00:15:51 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 48a4 created at Sun May 22 15:33:51 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 1ec4 created at Sun May 22 15:33:51 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e514 created at Wed Mar 15 20:48:05 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature f869 created at Wed Mar 15 20:14:57 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 477a created at Sat Sep 24 09:17:02 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 4ae6 created at Sun Mar 14 20:00:37 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 665b created at Sun Apr 10 01:48:23 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature a4f0 created at Wed Mar 15 20:34:12 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 63d3 created at Sun Apr 10 00:21:06 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 0e4e created at Wed Nov 8 00:41:38 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature bcb8 created at Wed Nov 8 00:41:35 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9814 created at Sat Oct 30 11:13:25 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 0b8e created at Wed Mar 15 20:06:30 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 4a25 created at Sun Jun 11 00:22:53 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ab39 created at Wed Mar 15 20:40:27 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 86c2 created at Wed Mar 15 20:40:26 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 6ba1 created at Wed Mar 15 20:06:02 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ba08 created at Wed Dec 20 23:29:18 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature c668 created at Sun Nov 19 22:35:29 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 0101 created at Sat Aug 28 23:23:53 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 609d created at Sat Jun 10 22:58:26 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 2316 created at Sat Jun 10 22:58:26 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e0db created at Sat Apr 1 23:26:15 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3032 created at Sun Apr 10 00:30:55 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3e77 created at Sun Apr 10 01:20:57 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 765b created at Sun Oct 8 12:09:42 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 400b created at Sun Oct 8 12:09:43 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e34a created at Wed Mar 2 07:09:28 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 0cc5 created at Wed Mar 15 20:22:17 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 6f20 created at Mon Dec 19 00:49:58 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature d9d2 created at Mon Dec 19 00:49:59 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 150e created at Sun Dec 18 23:52:59 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 14f2 created at Sun Dec 18 23:53:00 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature a7e9 created at Wed Mar 15 20:24:34 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature b5c4 created at Wed Mar 15 20:24:33 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 5a1a created at Sun Apr 10 00:28:19 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9aa4 created at Sun Apr 10 00:44:53 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature c301 created at Sun Apr 10 01:44:39 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 04f2 created at Tue Aug 1 21:52:58 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 4e4a created at Tue Aug 1 21:52:58 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature a2aa created at Sun Apr 10 01:04:34 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature a309 created at Wed Mar 15 20:44:17 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature c354 created at Wed Mar 15 20:44:16 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ccce created at Fri Sep 8 10:36:25 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ea35 created at Sun Jan 23 17:59:59 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 0000 created at Mon Dec 19 00:37:36 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e952 created at Mon Dec 19 00:37:36 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature fb0c created at Sun Apr 10 01:16:07 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 61d6 created at Wed Mar 15 20:25:50 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 2ee8 created at Sun Apr 10 01:32:20 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature cc45 created at Sun Apr 10 00:20:01 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 57f9 created at Sat Dec 11 01:16:25 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature fa1c created at Wed Nov 8 00:26:50 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 05d1 created at Mon Jul 4 22:43:51 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 4792 created at Sun Apr 2 00:25:30 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 457d created at Sun Apr 2 00:25:02 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 0018 created at Sun Apr 2 00:25:22 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 5088 created at Sun Apr 2 00:25:03 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9657 created at Sun Apr 2 00:25:00 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 498f created at Sat Apr 1 23:24:57 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature d86d created at Tue Aug 1 22:46:37 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 1dbc created at Sun Apr 10 01:38:07 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 0884 created at Wed Mar 15 20:25:35 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 7d98 created at Tue Sep 21 00:08:22 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 5013 created at Tue Sep 21 00:08:23 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 0636 created at Tue Sep 21 00:08:21 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 8865 created at Tue Sep 21 00:08:21 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e7c7 created at Sun Nov 19 22:35:38 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature f8e0 created at Sun Apr 10 01:44:21 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature dee1 created at Sun Nov 19 22:35:38 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 2582 created at Wed Mar 15 20:32:54 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 94ff created at Wed Mar 15 20:25:09 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 6ef0 created at Sat Apr 15 19:59:28 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 64c0 created at Sat Apr 15 19:59:27 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 73e1 created at Sun Jan 23 18:00:00 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature b5cb created at Sun Apr 10 01:28:47 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 0d97 created at Sun Apr 10 01:45:14 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature b797 created at Sun Apr 10 01:27:36 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 98e5 created at Wed Mar 15 20:49:52 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 0f3d created at Wed Mar 15 20:49:52 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e33a created at Sun Jun 12 21:24:04 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 74f0 created at Sat Jun 10 23:08:02 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 181a created at Sat Jun 10 23:08:02 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9d85 created at Sun Nov 12 22:50:51 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 426c created at Sun Nov 12 22:50:51 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 1420 created at Wed Mar 15 20:33:52 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3d52 created at Sun Feb 26 13:38:31 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9c7f created at Sun Feb 26 12:17:19 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature a4c1 created at Sun Oct 8 12:09:35 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature f95d created at Sun Jun 11 00:06:55 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 6d8a created at Sun Jun 11 00:06:57 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 7f46 created at Wed Mar 15 20:34:14 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 6e59 created at Sat Mar 9 11:04:02 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 181b created at Sun Apr 10 00:21:06 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature f3a5 created at Sun Apr 10 00:21:04 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ace3 created at Sat Apr 1 23:53:24 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9484 created at Sat Oct 30 10:21:00 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 35f0 created at Sat Oct 30 10:21:01 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 1b1b created at Tue Oct 3 03:40:28 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e6d2 created at Sun May 22 16:33:47 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 1909 created at Sun May 22 16:40:20 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 15aa created at Wed Dec 20 23:45:31 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3015 created at Wed Mar 15 20:54:56 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature be46 created at Wed Mar 15 20:54:56 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 6b3c created at Mon Apr 25 21:38:19 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature a58c created at Sun Apr 10 01:13:46 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 5d0f created at Sat Dec 11 01:44:12 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature a472 created at Mon Apr 29 21:11:33 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 0d11 created at Mon Apr 29 21:11:33 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 0e4b created at Wed Nov 8 00:47:42 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ef00 created at Wed Nov 8 00:45:00 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e0d3 created at Sat Mar 9 10:09:09 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 5f92 created at Wed Dec 20 23:36:25 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 20bb created at Sat Mar 9 10:13:06 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature f0c1 created at Sat Mar 9 10:13:06 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 920a created at Sat Mar 9 10:13:04 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 7c4b created at Sat Mar 9 10:39:52 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3f5c created at Sat Mar 9 11:03:04 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 084d created at Wed Dec 20 23:15:17 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature d8f2 created at Sat Mar 9 10:11:15 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 7f18 created at Sat Mar 9 10:12:14 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 40be created at Wed Nov 8 01:01:12 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature f7a8 created at Sat Mar 9 10:45:52 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 60ea created at Sat Mar 9 10:45:52 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature f13a created at Sat Mar 9 10:45:48 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 5931 created at Wed Mar 15 20:08:20 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ee1f created at Wed Dec 20 23:35:19 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 61ed created at Wed Dec 20 23:35:19 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e08c created at Sat Sep 24 08:35:48 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature c39a created at Sat Mar 9 10:30:08 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3e91 created at Wed Mar 15 20:14:25 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature eb76 created at Wed Mar 15 20:15:16 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 5995 created at Wed Mar 15 20:25:05 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature a855 created at Wed Mar 15 20:42:13 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature a945 created at Wed Mar 15 20:42:12 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature a1c7 created at Wed Mar 15 20:42:17 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 75ff created at Wed Mar 15 20:42:16 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 02c3 created at Wed Mar 15 20:38:03 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 8be9 created at Wed Mar 15 20:12:57 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature c9fb created at Wed Nov 8 00:53:06 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature f655 created at Wed Mar 15 20:56:27 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e24a created at Sun Feb 26 13:55:22 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature b4d8 created at Sun Feb 26 13:55:22 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 0099 created at Wed Nov 8 00:54:51 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 702d created at Sun May 22 15:47:36 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature a335 created at Sun Apr 10 00:31:38 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature fd1a created at Sun Jun 2 14:26:18 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9051 created at Wed Mar 15 20:11:58 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 152d created at Sun Aug 3 19:34:44 2008 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 80d4 created at Fri Jun 21 09:35:17 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 2694 created at Fri Jun 21 09:35:17 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 726f created at Sun Aug 14 11:36:29 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 51cb created at Sun Aug 14 11:36:27 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e1fc created at Wed Mar 15 20:42:35 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature f007 created at Sun Apr 2 00:16:10 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 6eb7 created at Fri Jun 21 09:37:50 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e20a created at Sun Aug 14 12:00:05 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 1c44 created at Wed Mar 15 09:20:30 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature f620 created at Wed Mar 15 09:16:57 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 2e09 created at Wed Mar 15 20:29:38 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ec2a created at Wed Mar 15 20:53:51 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature aab4 created at Wed Mar 15 20:53:51 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 11af created at Wed Mar 15 20:31:46 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 1e92 created at Wed Mar 15 20:07:44 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 6d8b created at Wed Mar 15 20:21:29 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 1932 created at Wed Mar 15 09:17:03 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 332e created at Mon Apr 29 21:46:01 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 24a5 created at Mon Apr 29 21:46:01 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 13d8 created at Wed Mar 2 07:35:53 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ae5b created at Wed Mar 15 20:26:26 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature b350 created at Sat Mar 9 10:53:35 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 84a4 created at Wed Mar 15 09:22:58 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 53b3 created at Wed Mar 15 20:21:05 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 37ee created at Sat Mar 9 10:12:59 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9064 created at Wed Mar 15 09:27:06 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature bc72 created at Wed Mar 15 09:22:22 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature c2f2 created at Fri Jun 21 09:56:39 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 2e7d created at Wed Mar 15 17:43:31 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature b463 created at Mon May 24 10:05:32 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3f95 created at Fri Jun 21 09:32:19 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3c07 created at Sun Jun 12 21:23:19 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3094 created at Wed Mar 15 09:22:01 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ea96 created at Mon May 24 11:04:24 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 7247 created at Fri Jun 21 09:36:05 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature cbf3 created at Fri Jun 21 09:32:19 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature f063 created at Fri Jun 21 09:32:19 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature d227 created at Fri Jun 21 09:28:58 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 013b created at Sun Jun 12 21:52:00 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 78b4 created at Sun Feb 26 14:29:48 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9bd6 created at Wed Mar 15 09:20:33 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 665c created at Wed Mar 15 09:24:46 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 36b3 created at Sat Jul 17 22:07:37 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 4854 created at Sun Dec 18 23:36:24 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature c599 created at Fri Sep 8 10:45:07 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 4f0f created at Wed Mar 15 09:24:39 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9666 created at Wed Mar 15 17:50:28 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 05d0 created at Wed Mar 15 09:17:23 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3e7f created at Wed Mar 15 17:44:26 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature a384 created at Wed Mar 15 09:19:08 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature d7b9 created at Sun Jun 11 00:22:58 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 7077 created at Sun Jun 11 00:22:57 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ca3b created at Wed Mar 15 09:19:39 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 5eb7 created at Sun Feb 26 13:45:58 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 5bfa created at Wed Mar 15 17:40:38 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 608e created at Wed Mar 15 17:45:53 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 4dce created at Fri Jan 20 10:33:02 2012 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature c3d1 created at Thu Oct 1 07:35:33 2009 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature d7b1 created at Fri Jun 21 09:50:44 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature bb67 created at Wed Mar 15 17:58:23 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature c999 created at Wed Mar 15 17:53:26 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 2a01 created at Mon May 24 10:50:04 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 26f0 created at Wed Mar 15 09:19:34 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 606b created at Mon Dec 19 00:33:52 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 704f created at Wed Mar 15 09:24:44 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 61ed created at Sat Jan 28 12:34:51 2012 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature bbe8 created at Wed Apr 2 15:28:48 2008 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature cb4a created at Sun Aug 3 19:32:44 2008 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 7d63 created at Wed Mar 15 09:20:49 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature f859 created at Wed Mar 15 09:17:20 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 2620 created at Wed Mar 15 09:19:46 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 0219 created at Wed Mar 15 09:17:06 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 8af0 created at Sun Oct 30 10:43:22 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 73d8 created at Wed Mar 15 17:52:27 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature bf6f created at Wed Mar 15 09:20:39 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature bb52 created at Mon May 24 10:03:29 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature fa02 created at Mon May 24 10:15:52 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature bc0e created at Sun Dec 18 23:39:31 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 5e17 created at Wed Mar 15 17:54:01 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature dec5 created at Wed Mar 15 17:42:53 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature c272 created at Mon May 24 11:14:50 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature de04 created at Wed Mar 15 09:19:38 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature b235 created at Wed Mar 15 17:40:44 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 6710 created at Wed Mar 15 09:21:48 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature a286 created at Sun Jun 12 21:29:46 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature df56 created at Sat Jul 17 22:06:40 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature feeb created at Wed Mar 15 20:22:35 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 4e05 created at Sat Jul 17 22:41:03 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature bbea created at Wed Mar 15 20:01:29 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9434 created at Wed Mar 15 20:49:35 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 49ef created at Thu Jun 3 12:06:31 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature fbca created at Thu Jun 3 12:06:32 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature a73c created at Mon May 24 11:02:52 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ad97 created at Mon May 24 10:25:04 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature c2d7 created at Mon May 24 11:02:52 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 17d1 created at Mon May 24 10:25:05 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature cead created at Wed Mar 15 20:22:14 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9083 created at Wed Mar 15 20:22:13 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature da6c created at Wed Mar 15 20:10:39 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3dc2 created at Wed Mar 15 20:22:15 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ea85 created at Wed Mar 15 17:44:36 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 8559 created at Wed Mar 15 18:02:09 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3324 created at Wed Mar 15 17:54:49 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 31be created at Wed Mar 15 09:22:57 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 0d5c created at Wed Mar 15 20:42:05 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 5e42 created at Wed Mar 15 17:50:25 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e4a1 created at Wed Mar 15 09:27:12 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 1849 created at Wed Mar 15 17:52:26 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature fb87 created at Mon Mar 7 21:38:22 2011 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 8a38 created at Fri Jan 20 10:32:41 2012 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 5f80 created at Sun Feb 26 13:02:38 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 56b9 created at Wed Mar 15 17:54:32 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature cc25 created at Wed Mar 15 20:52:20 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 1d56 created at Mon May 24 11:03:40 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 0cc9 created at Mon May 24 10:35:36 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 5b29 created at Mon May 24 10:10:26 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature bb19 created at Fri Sep 8 10:23:25 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 1925 created at Wed Mar 15 09:20:35 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 864b created at Fri Sep 8 10:49:17 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature b76c created at Wed Mar 15 20:52:28 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature b167 created at Wed Mar 15 20:52:29 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 4052 created at Wed Mar 15 09:23:04 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 0fd0 created at Wed Mar 15 09:25:08 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 775d created at Fri Jan 20 10:34:03 2012 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3970 created at Wed Mar 15 17:40:14 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 4e0d created at Wed Mar 15 09:17:34 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 7bcf created at Wed Mar 15 09:26:06 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature a9e0 created at Wed Mar 15 09:22:33 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature d56c created at Wed Mar 15 18:01:00 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 95fe created at Wed Mar 15 17:39:39 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature cf6d created at Wed Mar 15 09:17:04 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 8377 created at Tue Aug 1 22:37:22 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 67ef created at Wed Mar 15 09:20:35 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3aee created at Wed Mar 15 17:47:11 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9be6 created at Fri Jan 20 10:32:35 2012 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature b4de created at Wed Mar 15 17:55:35 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 11be created at Fri Jan 20 10:32:04 2012 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ab0c created at Fri Dec 24 21:54:15 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 7ce9 created at Mon May 24 10:26:06 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 920d created at Fri Feb 15 15:04:33 2008 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 5a65 created at Wed Mar 15 17:50:34 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 03f2 created at Mon Nov 23 09:21:15 2009 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 6617 created at Mon Nov 23 09:21:23 2009 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature a3cb created at Mon Dec 19 00:16:20 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature c424 created at Wed Mar 15 17:41:54 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 8a9f created at Wed Mar 15 09:19:47 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e6a0 created at Fri Sep 8 10:42:06 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature b955 created at Wed Mar 15 17:54:36 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 7181 created at Wed Mar 15 09:24:54 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 293c created at Wed Mar 15 17:55:11 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ccb9 created at Wed Apr 2 15:28:44 2008 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 84b4 created at Sat Sep 24 09:11:38 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 683e created at Wed Mar 15 09:21:32 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 6f03 created at Mon May 24 10:50:01 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 8670 created at Mon May 24 10:40:58 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 2322 created at Wed Mar 15 17:43:29 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e5df created at Mon May 24 10:30:37 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3809 created at Sun Jun 12 21:18:24 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 2854 created at Fri Jan 20 10:33:23 2012 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 2ecd created at Fri Jan 20 10:33:21 2012 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 590f created at Wed Mar 15 09:27:46 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature f77c created at Wed Mar 15 20:03:48 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature f92a created at Sat Mar 9 10:28:41 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature cf17 created at Fri Sep 8 10:00:36 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 04b5 created at Fri Sep 8 10:45:29 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 24e5 created at Wed Mar 15 09:19:40 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature eeb5 created at Mon May 24 10:35:30 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature b1cf created at Wed Mar 15 17:41:09 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature f793 created at Wed Apr 2 15:28:48 2008 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 431f created at Wed Mar 15 17:43:43 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 6f07 created at Wed Mar 15 09:17:31 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature de11 created at Wed Mar 15 17:55:06 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 62af created at Sun Oct 30 11:04:38 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature b531 created at Wed Mar 15 17:50:37 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e831 created at Fri Sep 8 10:21:40 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 862a created at Wed Mar 15 17:43:48 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 48a2 created at Sun Dec 18 23:56:32 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature f5c6 created at Wed Mar 15 09:21:45 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 76a1 created at Wed Mar 15 17:39:53 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 4074 created at Wed Mar 15 17:50:16 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature af8b created at Sat Mar 9 10:57:38 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 53f4 created at Wed Mar 15 09:27:16 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ef21 created at Sat Sep 24 08:36:48 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 2345 created at Wed Mar 15 09:22:24 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e270 created at Mon May 24 10:27:51 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 24b8 created at Wed Mar 15 17:44:56 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature d37f created at Wed Mar 15 17:41:49 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature bc58 created at Wed Mar 15 09:22:26 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e19d created at Wed Oct 21 18:40:11 2009 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 58e1 created at Mon May 24 10:22:45 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 7114 created at Mon Dec 19 00:35:29 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 89d6 created at Wed Mar 15 09:22:25 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature cf89 created at Wed Mar 15 09:17:36 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ce4a created at Mon Dec 19 00:22:13 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 6860 created at Mon Nov 23 09:21:24 2009 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature b084 created at Wed Mar 15 17:42:13 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 8296 created at Mon Sep 26 06:06:42 2011 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 7726 created at Wed Mar 15 17:52:53 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 4f5f created at Wed Mar 15 17:53:01 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 2de1 created at Wed Mar 15 09:27:14 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e335 created at Wed Mar 15 09:17:27 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 41e2 created at Wed Mar 15 09:16:53 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature cdc2 created at Wed Mar 15 09:17:39 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 7aa7 created at Wed Mar 15 17:50:24 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 6d90 created at Mon Dec 19 00:08:57 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 717e created at Mon May 24 11:02:16 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 195d created at Wed Mar 15 09:20:30 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature fd14 created at Wed Mar 15 09:24:37 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 120e created at Wed Mar 15 17:42:34 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ad87 created at Mon May 24 10:46:45 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 1fee created at Mon May 24 11:07:35 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 092e created at Wed Mar 15 09:17:08 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature bfa7 created at Sat Sep 24 09:09:24 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature f3c6 created at Fri Sep 8 10:11:19 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 71d9 created at Wed Mar 15 17:41:17 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 313d created at Wed Mar 15 09:23:00 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 2332 created at Tue Aug 1 21:57:36 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 19d4 created at Mon May 24 10:22:03 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 8eb1 created at Mon May 24 10:18:02 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature fec1 created at Wed Mar 15 17:43:04 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 18ad created at Mon May 24 10:30:32 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 8d1e created at Fri Sep 8 10:10:37 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 5752 created at Wed Mar 15 17:44:32 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3ab2 created at Wed Mar 15 18:00:48 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 054a created at Sun Jun 12 20:22:13 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 23e7 created at Wed Mar 15 09:23:02 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 7d45 created at Mon May 24 11:10:07 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 1138 created at Wed Mar 15 09:19:35 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 05c5 created at Fri Jan 20 10:33:28 2012 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature c4fc created at Wed Mar 15 09:22:00 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature fc24 created at Wed Mar 15 17:43:47 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 1629 created at Wed Mar 15 17:43:33 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature b9db created at Mon May 24 10:07:09 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature b967 created at Wed Mar 15 17:53:57 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9ac5 created at Wed Mar 15 09:22:21 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 67ea created at Mon May 24 09:58:50 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 7d16 created at Mon May 24 11:10:31 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature f9cc created at Wed Mar 15 17:40:00 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature de5d created at Wed Mar 15 09:27:56 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 05e3 created at Fri Sep 8 10:04:10 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 2ad0 created at Wed Sep 16 18:44:40 2009 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature f83b created at Wed Mar 15 09:25:15 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 5dcc created at Wed Mar 15 09:24:55 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3b11 created at Wed Mar 15 17:39:51 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3bef created at Wed Mar 15 17:42:22 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature fcb4 created at Sun Jun 12 20:37:42 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature c8da created at Wed Mar 15 17:39:47 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 6e32 created at Mon May 24 10:52:17 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature f021 created at Wed Mar 15 17:39:52 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 6df7 created at Fri Jan 20 10:33:18 2012 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 47d7 created at Mon May 24 10:19:04 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 85fb created at Wed Sep 16 18:44:39 2009 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3108 created at Fri Sep 8 10:08:52 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature f71c created at Sun Aug 3 19:32:34 2008 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 912b created at Fri Aug 29 12:08:18 2008 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 12f4 created at Sat Sep 24 09:13:08 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature c068 created at Wed Mar 15 18:00:45 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 95a8 created at Fri Jan 20 10:32:08 2012 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 76f5 created at Wed Mar 15 17:42:38 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 0086 created at Wed Mar 15 17:50:08 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 4ac6 created at Sun Jun 12 20:20:20 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3b9a created at Fri Jun 21 09:40:23 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 664d created at Sun Jun 2 14:29:55 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ded3 created at Sat Mar 9 10:15:07 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 58db created at Sat Mar 9 10:54:44 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e7f2 created at Sat Mar 9 10:54:28 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ee2e created at Mon Apr 29 21:46:12 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 2898 created at Wed Mar 15 20:12:32 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature eb3b created at Wed Mar 15 18:02:37 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 1929 created at Wed Mar 15 17:56:22 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature a904 created at Wed Mar 15 17:55:10 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 56cc created at Wed Mar 15 09:21:59 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 6ac3 created at Wed Mar 15 20:07:32 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature d2e1 created at Wed Mar 15 17:55:15 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature f172 created at Wed Mar 15 17:39:57 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature aa78 created at Wed Mar 15 20:06:24 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature df08 created at Fri Jan 20 10:33:44 2012 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ad0f created at Wed Mar 15 17:53:43 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 786c created at Wed Mar 15 17:55:54 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ddf0 created at Wed Mar 15 17:55:33 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 611c created at Sat Mar 9 10:14:33 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 245a created at Sat Mar 9 10:14:33 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 2e47 created at Sat Mar 9 10:14:17 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 692a created at Wed Mar 15 20:52:44 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 67c7 created at Sat Oct 30 09:05:33 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature d878 created at Wed Mar 15 17:53:44 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature c7ca created at Wed Mar 15 20:47:33 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 1f95 created at Wed Mar 15 17:50:37 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature aa60 created at Wed Mar 15 18:04:07 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 6a62 created at Sat Sep 24 08:24:16 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ce30 created at Sun Aug 3 19:35:32 2008 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 8b51 created at Mon Dec 19 00:15:48 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature b2f3 created at Sat Mar 9 10:39:10 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 94ed created at Sun Jun 30 08:38:18 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 7e23 created at Sun Jun 30 08:38:18 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature d16a created at Sun May 22 16:34:20 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 53b5 created at Wed Mar 15 20:00:43 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature a65f created at Wed Mar 15 20:28:41 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 24d2 created at Wed Mar 15 20:27:28 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 2f22 created at Wed Mar 15 20:48:04 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 46b2 created at Sun Jun 2 14:14:43 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 77c1 created at Sun Jun 2 14:30:05 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ae69 created at Sun Jun 2 14:05:46 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 90ab created at Sun Jun 2 14:33:41 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 73a3 created at Sun Jun 2 14:06:15 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 8f05 created at Sun Jun 2 13:57:54 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 373b created at Fri Jun 21 09:55:16 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 31b4 created at Tue Oct 3 03:43:22 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 4f56 created at Tue Nov 30 00:22:39 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3d44 created at Wed Mar 15 17:55:39 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature b0aa created at Wed Mar 15 17:47:40 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ce2b created at Wed Mar 15 09:26:38 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 7a73 created at Wed Mar 15 09:17:46 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 02cb created at Wed Mar 15 09:17:00 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3fe6 created at Wed Mar 15 09:22:16 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 13e3 created at Wed Mar 15 17:42:47 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 82b7 created at Wed Mar 15 18:00:50 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 7069 created at Wed Mar 15 18:02:07 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 872f created at Fri Jun 21 09:32:19 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 7549 created at Wed Mar 15 09:20:46 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature c6c4 created at Fri Jun 21 09:28:07 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 0589 created at Fri Jun 21 09:48:39 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 22f5 created at Fri Jun 21 09:32:33 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3825 created at Fri Jun 21 09:55:19 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 10ae created at Fri Jun 21 09:32:19 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 1d22 created at Wed Mar 15 17:59:15 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 30fd created at Fri Jun 21 09:36:40 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 5b2c created at Wed Mar 15 09:22:27 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 07b6 created at Sun Aug 3 19:35:25 2008 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature a363 created at Wed Mar 15 09:17:07 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature b140 created at Wed Mar 15 20:05:05 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 30d7 created at Sun Feb 26 14:24:36 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature fcdd created at Wed Dec 20 23:27:09 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 7e63 created at Wed Nov 8 00:42:46 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3951 created at Wed Mar 15 20:12:00 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature a50b created at Wed Mar 15 20:14:04 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 5a91 created at Sun Jun 2 14:38:04 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9fc1 created at Wed Nov 8 00:42:45 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 37e9 created at Wed Nov 8 00:23:48 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 407a created at Fri Jul 26 16:59:51 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9a12 created at Wed Mar 15 20:29:09 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature bb33 created at Mon Nov 23 09:21:25 2009 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 64a9 created at Wed Mar 15 09:21:09 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 2927 created at Fri Feb 15 14:19:15 2008 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 37c2 created at Fri Feb 15 14:19:12 2008 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature dc4d created at Fri Jul 26 16:53:04 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 5e94 created at Fri Jan 20 10:33:24 2012 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature d02c created at Wed Mar 15 17:53:09 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 6754 created at Fri Jul 26 17:47:37 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 839a created at Fri Jul 26 17:17:17 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 5462 created at Sun Jun 2 14:06:23 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3d7d created at Wed Mar 15 20:04:01 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 7cf4 created at Wed Mar 15 20:01:39 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 1aab created at Wed Mar 15 20:46:11 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 2544 created at Sat Mar 9 10:40:49 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 0509 created at Fri Jul 26 17:23:56 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 0c54 created at Wed Mar 15 18:00:43 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 7db9 created at Sun Aug 3 19:35:32 2008 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 5d3d created at Fri Jul 26 16:59:11 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 714d created at Wed Mar 15 09:17:30 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature cf9a created at Fri Jul 26 17:28:48 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 68c5 created at Fri Feb 15 13:51:08 2008 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature aa6e created at Fri Feb 15 13:50:33 2008 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature fc23 created at Sat Apr 1 23:44:50 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature b9c2 created at Sat Mar 9 10:52:41 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ba52 created at Sun Apr 2 00:25:12 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 90ae created at Wed Mar 15 20:12:30 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 606e created at Fri Sep 8 10:15:24 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 947b created at Fri Jul 26 16:59:45 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 7025 created at Fri Jul 26 16:59:44 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 5edd created at Sat Mar 9 10:14:34 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature f784 created at Sat Apr 1 23:16:08 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature f57a created at Sun Jun 2 14:35:15 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature b4fe created at Sun Jun 2 14:35:15 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 0ad3 created at Sat Apr 1 23:49:03 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 1cbb created at Tue Oct 3 03:43:23 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ca31 created at Sat Mar 9 10:14:35 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature eacc created at Fri Sep 8 10:32:51 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature a673 created at Fri Sep 8 10:32:51 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 94ab created at Sat Mar 9 10:39:17 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9da8 created at Wed Mar 15 17:41:50 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3a43 created at Wed Mar 15 20:24:44 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature b29b created at Wed Mar 15 20:17:44 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature fe42 created at Tue Oct 3 03:43:22 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 1477 created at Tue Oct 3 03:43:22 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 7279 created at Tue Oct 3 03:42:03 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 504a created at Tue Oct 3 03:41:59 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 423a created at Tue Oct 3 03:41:59 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 37bf created at Tue Oct 3 03:43:20 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e1e4 created at Tue Oct 3 03:42:26 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature d41c created at Tue Oct 3 03:42:24 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 87aa created at Tue Oct 3 03:43:23 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature b20d created at Tue Oct 3 03:43:19 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 99d1 created at Tue Oct 3 03:42:14 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature c636 created at Tue Oct 3 03:42:24 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e967 created at Tue Oct 3 03:42:23 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature adfc created at Fri Jul 26 16:53:06 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature c460 created at Sun Sep 1 22:32:20 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e484 created at Sun Sep 1 22:32:23 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature cc92 created at Wed Mar 15 17:41:06 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature f006 created at Sun Sep 1 22:30:29 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 6cb9 created at Sun Aug 3 18:53:29 2008 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 754d created at Thu Apr 1 20:02:19 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 4bba created at Thu Apr 1 20:15:29 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature b411 created at Sat Aug 1 21:49:46 2009 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 2056 created at Thu May 19 07:40:22 2011 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 35c9 created at Sun Aug 3 18:53:29 2008 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature da8a created at Wed Mar 15 17:45:36 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 387b created at Sun Aug 3 18:53:29 2008 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature a3ff created at Sun Aug 3 18:53:28 2008 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e861 created at Thu Sep 3 18:58:30 2009 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 5db0 created at Sun Aug 3 18:53:28 2008 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature a75f created at Sun Aug 3 18:53:28 2008 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature caa9 created at Sun Aug 3 18:53:28 2008 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 46dc created at Sun Aug 3 18:53:28 2008 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e5f9 created at Sun Apr 10 00:20:03 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 6570 created at Mon Dec 25 21:21:04 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature a7f3 created at Mon Dec 25 21:21:03 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 1bb2 created at Wed Dec 20 23:20:59 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 8f7d created at Wed Dec 20 23:21:00 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ac0a created at Sat Apr 1 23:49:02 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9c8e created at Sat Mar 9 10:57:33 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 7ccd created at Sat Mar 9 10:57:33 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature b5f0 created at Wed Mar 15 20:45:12 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature fd0c created at Wed Mar 15 20:43:35 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3b5c created at Wed Mar 15 17:48:23 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 48c1 created at Sun Apr 10 01:34:03 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 07ae created at Sun Apr 10 01:34:00 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ca34 created at Sun Jun 2 14:13:17 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e0a5 created at Sun Jun 2 14:42:12 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 52ce created at Sun Jun 2 14:42:12 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 2573 created at Tue Oct 3 03:43:17 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 6480 created at Sat Aug 24 18:05:28 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 6cef created at Sat Aug 24 18:05:24 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 4a42 created at Sat Aug 24 18:05:27 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3a76 created at Sat Aug 24 18:05:26 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature bad1 created at Fri Jul 26 17:05:20 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature f80b created at Mon Apr 29 21:45:53 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 14a9 created at Mon Apr 29 21:45:53 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 8608 created at Tue Oct 3 03:42:02 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 1603 created at Tue Oct 3 03:42:27 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 743f created at Tue Oct 3 03:42:22 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 11da created at Sun Jun 6 21:39:02 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature eff6 created at Wed Mar 15 20:47:27 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature d3b1 created at Sat Jun 10 23:38:33 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 683b created at Sat Jun 10 22:57:00 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature b053 created at Sun Aug 14 12:36:28 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature b83f created at Mon Apr 25 21:29:43 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3b64 created at Sun Mar 14 20:17:45 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 4a30 created at Wed Mar 15 20:47:28 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 1261 created at Wed Mar 15 20:11:32 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 2382 created at Wed Mar 15 19:59:44 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e80b created at Wed Mar 15 19:59:45 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature c511 created at Sat Oct 12 08:34:06 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 4dc3 created at Wed Mar 15 20:24:09 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3a8c created at Wed Mar 15 20:24:08 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 6e20 created at Sat Aug 28 23:23:50 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3da9 created at Sun Sep 1 22:21:15 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 969e created at Sun Sep 1 22:21:16 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z rpm-sequoia-1.4.0-1.x32 rpm-sequoia-devel-1.4.0-1.x32 error: Verifying a signature, but no certificate was provided: Signature f4cc created at Sun Nov 17 22:57:59 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature c371 created at Tue Oct 3 03:42:08 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 83a4 created at Tue Oct 3 03:42:20 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature be76 created at Tue Oct 3 03:42:16 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature bf08 created at Tue Oct 3 03:42:20 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature f10f created at Sun Sep 1 22:30:25 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 16bf created at Sun Sep 1 22:30:25 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 440a created at Sat Apr 1 23:52:54 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 370c created at Sat Mar 9 10:46:15 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 0a4e created at Sat Mar 9 10:46:16 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 88d4 created at Sat Mar 9 10:33:54 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 081c created at Sat Mar 9 10:33:53 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature db8e created at Wed Mar 15 20:01:14 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature aac9 created at Wed Mar 15 20:01:13 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9d5c created at Wed Mar 15 20:03:54 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 21a3 created at Wed Mar 15 20:03:53 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 4bbd created at Wed Mar 15 20:12:40 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3fc8 created at Wed Nov 8 00:45:35 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 635d created at Tue Oct 3 03:41:56 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature a278 created at Tue Oct 3 03:42:24 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature b264 created at Tue Oct 3 03:42:00 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 0f12 created at Tue Oct 3 03:54:35 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 2761 created at Fri Jul 26 17:41:46 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 7693 created at Thu Apr 1 20:02:56 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 0a11 created at Wed Mar 15 18:02:05 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature c0bf created at Thu Apr 1 20:19:09 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e90c created at Thu Apr 1 20:10:14 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 44a1 created at Wed Mar 15 20:01:10 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature a599 created at Wed Mar 15 20:01:11 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 0526 created at Wed Dec 4 10:22:02 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e3ca created at Wed Nov 8 00:50:09 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 918e created at Sun Jun 2 14:44:28 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature dc25 created at Tue Aug 1 22:42:14 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature d7f4 created at Tue Aug 1 22:42:14 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 88ac created at Wed Mar 15 20:50:20 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature c285 created at Wed Mar 15 20:50:20 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9a44 created at Sun Jun 2 14:36:54 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 8902 created at Wed Mar 15 20:45:00 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 0805 created at Mon Apr 29 21:44:36 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3c4e created at Mon Apr 29 21:44:35 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature fcd1 created at Wed Mar 15 20:53:54 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature f60a created at Sun May 22 15:39:11 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature f441 created at Sun Apr 2 00:04:13 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature af49 created at Sun Apr 2 00:04:12 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature f513 created at Wed Mar 15 20:12:07 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature cf65 created at Wed Mar 15 20:13:19 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 98e0 created at Wed Mar 15 20:12:43 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 0466 created at Wed Mar 15 20:35:46 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 8075 created at Fri Sep 8 10:36:31 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9ac8 created at Sun Apr 10 01:30:20 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature de6c created at Sat Apr 1 23:18:27 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 00ca created at Wed Mar 15 17:48:16 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 02fa created at Wed Dec 4 10:38:48 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 552b created at Wed Dec 4 10:38:48 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 8aa0 created at Wed Mar 15 20:47:16 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature d104 created at Wed Mar 15 20:45:01 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 19ba created at Wed Mar 15 20:47:17 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 26f0 created at Wed Dec 4 10:09:11 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 6e85 created at Wed Dec 4 10:09:11 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 2c8a created at Wed Dec 4 10:09:11 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 41ce created at Wed Dec 4 10:09:09 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature f084 created at Sat Jul 17 22:32:10 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 278c created at Wed Mar 15 20:13:37 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 0f47 created at Wed Mar 15 20:53:13 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature d087 created at Wed Mar 15 20:30:44 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9f9d created at Sat Mar 9 10:27:46 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 033b created at Sat Mar 9 10:27:47 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 7c3c created at Sat Oct 12 08:36:08 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature c634 created at Tue Aug 1 22:05:11 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9f96 created at Sat Apr 1 23:52:54 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 4a27 created at Sat Dec 28 20:24:11 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 5e34 created at Sat Dec 11 01:13:19 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9e83 created at Wed Mar 15 17:55:26 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9192 created at Sat Dec 28 20:49:39 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e71c created at Wed Mar 15 20:30:09 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3cf2 created at Tue Oct 3 03:42:07 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 4d74 created at Tue Oct 3 03:42:27 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 19fb created at Wed Mar 15 20:53:54 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature cabd created at Wed Dec 4 10:36:51 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 46c4 created at Wed Dec 4 10:36:51 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 7c54 created at Wed Mar 15 20:15:53 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e997 created at Wed Mar 15 20:16:22 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z rpm-macros-systemd-254.23-1.noarch error: Verifying a signature, but no certificate was provided: Signature 6142 created at Sat Dec 28 20:44:12 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature cce9 created at Wed Dec 4 09:37:17 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e462 created at Wed Dec 4 09:37:17 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9f09 created at Tue Oct 3 03:42:45 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 1d42 created at Sat Apr 1 23:18:32 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ceb9 created at Sat Apr 1 23:18:32 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 23cd created at Sat Dec 28 20:23:15 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature fa13 created at Wed Dec 4 10:01:54 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 62d9 created at Fri Sep 8 10:09:02 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature d0ba created at Tue Aug 1 21:41:17 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 6077 created at Tue Aug 1 21:41:16 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 93e9 created at Wed Dec 4 09:37:10 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 82a9 created at Wed Dec 4 09:56:27 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 4d88 created at Wed Dec 4 09:40:26 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3c1c created at Wed Dec 4 10:23:05 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 848b created at Wed Mar 15 20:22:07 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature b6bc created at Sun Jun 2 14:36:20 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature a3de created at Wed Dec 4 10:10:04 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature bf34 created at Wed Dec 4 09:56:28 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 5ea5 created at Wed Dec 4 10:14:05 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 1b85 created at Wed Dec 4 10:05:00 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature d2cf created at Wed Dec 4 09:35:50 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 2906 created at Sat Dec 28 20:51:57 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 35d9 created at Sat Dec 28 20:51:57 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 4ec1 created at Wed Dec 4 09:56:27 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 0ef2 created at Wed Dec 4 09:56:27 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9977 created at Wed Dec 4 09:56:27 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e3fe created at Wed Dec 4 10:10:04 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature f971 created at Wed Dec 4 10:14:05 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 6d64 created at Wed Dec 4 09:37:10 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 8f4f created at Sat Oct 12 08:19:07 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 4337 created at Wed Dec 4 09:50:55 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature c4d5 created at Sun Oct 30 10:26:59 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 1760 created at Sun Oct 30 10:27:00 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 2230 created at Sun Jun 2 14:36:20 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature bb52 created at Wed Nov 8 00:52:14 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 69c7 created at Wed Dec 4 10:22:00 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature d51d created at Wed Dec 4 10:21:59 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 16be created at Wed Dec 4 10:27:43 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9723 created at Wed Dec 4 10:25:00 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 91a4 created at Wed Dec 4 10:24:59 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 4111 created at Wed Dec 4 10:31:33 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3e82 created at Wed Dec 4 10:31:32 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature abe0 created at Sat Dec 28 20:23:00 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 8386 created at Wed Dec 4 10:26:31 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature b0d1 created at Wed Mar 15 20:17:57 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 909d created at Wed Dec 4 10:26:32 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e1e8 created at Wed Dec 4 10:04:59 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature fca9 created at Wed Mar 15 20:17:58 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 5d3c created at Sat Dec 28 20:22:59 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 05ca created at Sat Dec 28 20:23:00 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 84eb created at Sat Dec 28 20:22:59 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 96cd created at Sat Dec 28 20:22:59 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 5371 created at Sat Dec 28 20:22:59 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 496c created at Mon Mar 14 08:31:13 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 78dd created at Wed Dec 4 09:50:55 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature c47f created at Fri Jul 26 17:46:00 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9fbe created at Fri Jul 26 17:28:27 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature dc58 created at Fri Jul 26 17:01:44 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ed4f created at Fri Jul 26 17:41:15 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature f0a7 created at Fri Jul 26 17:29:05 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature cf0d created at Fri Jul 26 17:26:47 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature be5d created at Fri Jul 26 17:29:04 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3c8d created at Fri Jul 26 17:54:36 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 8ecc created at Fri Jul 26 17:28:27 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature d870 created at Fri Jul 26 17:08:30 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 46c3 created at Fri Jul 26 17:21:44 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 767e created at Fri Jul 26 16:58:45 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature b73c created at Fri Jul 26 17:50:55 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 2260 created at Fri Jul 26 16:58:21 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 39c5 created at Fri Jul 26 17:01:44 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 5146 created at Fri Jul 26 17:22:44 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ec99 created at Fri Jul 26 17:19:22 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 41f7 created at Fri Jul 26 17:13:54 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9de1 created at Fri Jul 26 17:10:49 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature d063 created at Fri Jul 26 17:54:36 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature d28a created at Fri Jul 26 17:53:06 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 4408 created at Fri Jul 26 17:29:05 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 134f created at Fri Jul 26 17:24:17 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature dcb4 created at Fri Jul 26 17:02:32 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 05e7 created at Fri Jul 26 17:51:31 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 8952 created at Fri Jul 26 17:51:32 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature d9a6 created at Fri Jul 26 17:02:32 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 844d created at Fri Jul 26 17:24:17 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 6263 created at Fri Jul 26 17:13:54 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 32bc created at Fri Jul 26 17:22:44 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature bee5 created at Fri Jul 26 17:20:42 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9557 created at Fri Jul 26 16:58:21 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 6e89 created at Fri Jul 26 17:50:55 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 5af5 created at Fri Jul 26 17:21:45 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e5cb created at Fri Jul 26 17:22:57 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 09b6 created at Fri Jul 26 17:26:47 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 1fa1 created at Fri Jul 26 17:41:16 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 36bb created at Fri Jul 26 16:59:19 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ee9a created at Fri Jul 26 16:59:19 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 6ffd created at Fri Jul 26 17:53:06 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 1ae0 created at Fri Jul 26 17:10:49 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 2cee created at Fri Jul 26 17:19:22 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature c20b created at Fri Jul 26 16:58:45 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 59f0 created at Fri Jul 26 17:29:04 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature f229 created at Fri Jul 26 17:22:57 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 6b67 created at Fri Jul 26 16:58:56 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 0101 created at Fri Jul 26 17:18:43 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ec02 created at Fri Jul 26 17:54:58 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 828f created at Fri Jul 26 17:42:03 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 0c9f created at Fri Jul 26 17:51:35 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 16fb created at Fri Jul 26 17:37:51 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e45f created at Fri Jul 26 17:37:51 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 7070 created at Fri Jul 26 17:25:33 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 800e created at Fri Jul 26 17:25:33 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3bcd created at Fri Jul 26 17:47:24 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9f11 created at Fri Jul 26 17:47:24 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 758f created at Fri Jul 26 17:22:02 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 4127 created at Fri Jul 26 17:22:02 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 5544 created at Fri Jul 26 17:51:35 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ce88 created at Fri Jul 26 17:08:30 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature fb47 created at Mon Apr 29 21:43:14 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9499 created at Fri Jul 26 17:36:41 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 8ede created at Fri Jul 26 17:10:27 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 5e75 created at Fri Jul 26 17:44:03 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 2633 created at Mon Apr 29 21:43:14 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 743d created at Fri Jul 26 16:53:57 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 6e6f created at Fri Jul 26 17:09:13 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 2912 created at Sat Mar 9 10:18:21 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 6556 created at Fri Jul 26 17:41:55 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 0fe1 created at Fri Jul 26 17:36:42 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 4287 created at Fri Jul 26 17:16:30 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ec6c created at Fri Jul 26 17:22:59 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 6a9c created at Fri Jul 26 17:26:41 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ed01 created at Mon Apr 29 21:34:02 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 5af6 created at Fri Jul 26 17:26:42 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ac43 created at Fri Jul 26 17:22:59 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature fd32 created at Fri Jul 26 17:16:30 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 149c created at Fri Jul 26 17:41:55 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 08f3 created at Sat Mar 9 10:18:21 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 1b8f created at Fri Jul 26 17:09:13 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9b24 created at Fri Jul 26 16:53:57 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature c7b2 created at Fri Jul 26 17:54:58 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 7790 created at Fri Jul 26 17:42:03 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature a69b created at Fri Jul 26 17:44:03 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature c400 created at Fri Jul 26 16:58:56 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 641d created at Mon Apr 29 21:33:49 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 48bd created at Mon Apr 29 21:35:25 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e594 created at Mon Apr 29 21:39:57 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e1f2 created at Mon Apr 29 21:33:57 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature d0e8 created at Sun Nov 17 22:56:54 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature d3fc created at Mon Apr 29 21:35:25 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3a0c created at Mon Apr 29 21:33:50 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 51de created at Wed Mar 15 20:52:52 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 38de created at Wed Mar 15 20:34:17 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 00e6 created at Sun Jun 12 20:20:29 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature aa6b created at Sun Jun 12 20:20:28 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3cc4 created at Wed Mar 15 20:22:28 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 5207 created at Wed Mar 15 20:22:27 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ac56 created at Wed Mar 15 20:07:46 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 0868 created at Wed Mar 15 20:07:46 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 2096 created at Sat Oct 30 10:09:28 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature fea7 created at Sat Oct 30 10:09:28 2021 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 94cd created at Wed Mar 15 20:21:16 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature f3a7 created at Sun Apr 2 00:18:51 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature b489 created at Sat Dec 28 20:22:47 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 2146 created at Sat Dec 28 20:22:47 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature a925 created at Wed Mar 15 20:32:12 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 8ddf created at Wed Mar 15 20:32:12 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature dee0 created at Sun Jun 2 14:04:01 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 5630 created at Mon Apr 29 21:32:55 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature a3f0 created at Wed Dec 4 09:50:54 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature c95b created at Wed Dec 4 09:50:54 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e24b created at Wed Dec 4 10:31:46 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 8858 created at Wed Dec 4 10:31:46 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 6c29 created at Sat Oct 12 08:29:26 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 6adf created at Sat Oct 12 08:29:24 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature dbaa created at Wed Nov 8 00:25:44 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 4c40 created at Wed Nov 8 00:25:43 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature d099 created at Fri Jul 26 17:51:16 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 7104 created at Sun Jun 2 14:25:19 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 8d8e created at Wed Dec 4 10:05:09 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 82c1 created at Fri Jul 26 17:51:16 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ea9b created at Sat Oct 12 08:23:13 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 2edd created at Mon Apr 29 21:44:44 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 15c4 created at Mon Apr 29 21:37:36 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e5d8 created at Sun Sep 1 22:40:36 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature c2ae created at Fri Jul 26 17:43:43 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 5923 created at Fri Jul 26 16:59:17 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ca6f created at Fri Jul 26 16:59:17 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature fb07 created at Fri Jul 26 17:43:43 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 92c6 created at Fri Jul 26 17:18:43 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e34b created at Sat Dec 28 20:43:50 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 143c created at Sat Dec 28 20:43:49 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 4be7 created at Sat Dec 28 20:30:00 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 16d2 created at Sat Dec 28 20:43:48 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature ce16 created at Sat Dec 28 20:43:48 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3d17 created at Sat Oct 12 08:33:20 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 456b created at Sat Oct 12 08:33:20 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature cd54 created at Wed Dec 20 23:52:33 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 55a5 created at Wed Dec 20 23:52:33 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature cb00 created at Sat Dec 28 20:33:02 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3fed created at Wed Dec 4 10:15:11 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 4ee6 created at Wed Dec 4 10:23:23 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature cad1 created at Wed Dec 4 10:25:35 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 34ca created at Wed Dec 4 10:27:43 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 672a created at Sat Oct 12 08:34:05 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 577f created at Mon Apr 29 21:35:19 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 028e created at Mon Apr 29 21:35:19 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 5643 created at Sun Feb 26 12:21:46 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 8cee created at Sun Feb 26 12:21:45 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z rpm-lib-4.18.2-2.x32 error: Verifying a signature, but no certificate was provided: Signature d901 created at Sat Mar 9 11:03:57 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature a57b created at Sat Dec 28 20:44:29 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 2fd4 created at Sun Jun 2 14:11:57 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature c50a created at Wed Mar 2 07:09:29 2022 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature f188 created at Sat Jun 10 23:24:37 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 4538 created at Wed Dec 4 09:52:26 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 4717 created at Wed Dec 4 09:52:26 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 2ae8 created at Fri Jul 26 17:47:14 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 0cdf created at Wed Mar 15 20:27:31 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 86fd created at Wed Dec 4 09:44:40 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature bf62 created at Wed Sep 13 13:07:15 2023 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 660f created at Wed Dec 4 10:27:19 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 9088 created at Fri Dec 20 17:44:32 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 1c48 created at Fri Dec 20 17:44:40 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3568 created at Fri Dec 20 17:44:39 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 317e created at Wed Dec 4 09:41:05 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature 3277 created at Sat Oct 12 08:19:08 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z error: Verifying a signature, but no certificate was provided: Signature e5e5 created at Sat Oct 12 08:19:06 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z rpm-pld-macros-2.039-1.noarch rpm-pld-macros-build-2.039-1.noarch rpm-pld-macros-javaprov-2.039-1.noarch rpm-pld-macros-rubyprov-2.039-1.noarch rpm-pld-macros-php-pearprov-2.039-1.noarch rpm-lib-4.20.0-1.x32 rpm-devel-4.20.0-1.x32 rpm-base-4.20.0-1.x32 rpm-4.20.0-1.x32 rpm-utils-4.20.0-1.x32 rpm-build-4.20.0-1.x32 error: Verifying a signature, but no certificate was provided: Signature 7e74 created at Wed Dec 4 10:14:52 2024 invalid: signature relies on legacy cryptography because: Policy rejected non-revocation signature (Binary) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z Begin-PLD-Builder-Info Build-Time: user:2.37s sys:0.44s real:2.82s (faults io:9 non-io:39597) End-PLD-Builder-Info