Powered by GNU antilope. Your IP: 18.97.9.170 | command 71584326-f514-4189-b8c0-ac3be1ff8232Toc:- error 1
error: Verifying a signature, but no certificate was provided:
- error 2
error: Verifying a signature, but no certificate was provided:
- error 3
error: Verifying a signature, but no certificate was provided:
- error 4
error: Verifying a signature, but no certificate was provided:
- error 5
error: Verifying a signature, but no certificate was provided:
- error 6
error: Verifying a signature, but no certificate was provided:
- error 7
error: Verifying a signature, but no certificate was provided:
- error 8
error: Verifying a signature, but no certificate was provided:
- error 9
error: Verifying a signature, but no certificate was provided:
- error 10
error: Verifying a signature, but no certificate was provided:
- error 11
error: rpmdbNextIterator: skipping h# 14
- error 12
error: Verifying a signature, but no certificate was provided:
- error 13
error: Verifying a signature, but no certificate was provided:
- error 14
error: Verifying a signature, but no certificate was provided:
- error 15
error: Verifying a signature, but no certificate was provided:
- error 16
error: Verifying a signature, but no certificate was provided:
- error 17
error: Verifying a signature, but no certificate was provided:
- error 18
error: Verifying a signature, but no certificate was provided:
- error 19
error: Verifying a signature, but no certificate was provided:
- error 20
error: Verifying a signature, but no certificate was provided:
- error 21
error: Verifying a signature, but no certificate was provided:
- error 22
error: Verifying a signature, but no certificate was provided:
- error 23
error: Verifying a signature, but no certificate was provided:
- error 24
error: Verifying a signature, but no certificate was provided:
- error 25
error: Verifying a signature, but no certificate was provided:
- error 26
error: Verifying a signature, but no certificate was provided:
- error 27
error: Verifying a signature, but no certificate was provided:
- error 28
error: Verifying a signature, but no certificate was provided:
- error 29
error: Verifying a signature, but no certificate was provided:
- error 30
error: Verifying a signature, but no certificate was provided:
- error 31
error: Verifying a signature, but no certificate was provided:
- error 32
error: Verifying a signature, but no certificate was provided:
- error 33
error: Verifying a signature, but no certificate was provided:
- error 34
error: Verifying a signature, but no certificate was provided:
- error 35
error: Verifying a signature, but no certificate was provided:
- error 36
error: Verifying a signature, but no certificate was provided:
- error 37
error: Verifying a signature, but no certificate was provided:
- error 38
error: Verifying a signature, but no certificate was provided:
- error 39
error: Verifying a signature, but no certificate was provided:
- error 40
error: Verifying a signature, but no certificate was provided:
- error 41
error: Verifying a signature, but no certificate was provided:
- error 42
error: Verifying a signature, but no certificate was provided:
- error 43
error: Verifying a signature, but no certificate was provided:
- error 44
error: Verifying a signature, but no certificate was provided:
- error 45
error: Verifying a signature, but no certificate was provided:
- error 46
error: Verifying a signature, but no certificate was provided:
- error 47
error: Verifying a signature, but no certificate was provided:
- error 48
error: Verifying a signature, but no certificate was provided:
- error 49
error: Verifying a signature, but no certificate was provided:
- error 50
error: Verifying a signature, but no certificate was provided:
- error 51
error: Verifying a signature, but no certificate was provided:
- error 52
error: Verifying a signature, but no certificate was provided:
- error 53
error: Verifying a signature, but no certificate was provided:
- error 54
error: Verifying a signature, but no certificate was provided:
- error 55
error: Verifying a signature, but no certificate was provided:
- error 56
error: Verifying a signature, but no certificate was provided:
- error 57
error: Verifying a signature, but no certificate was provided:
- error 58
error: Verifying a signature, but no certificate was provided:
- error 59
error: Verifying a signature, but no certificate was provided:
- error 60
error: Verifying a signature, but no certificate was provided:
- error 61
error: Verifying a signature, but no certificate was provided:
- error 62
error: Verifying a signature, but no certificate was provided:
- error 63
error: Verifying a signature, but no certificate was provided:
- error 64
error: Verifying a signature, but no certificate was provided:
- error 65
error: Verifying a signature, but no certificate was provided:
- error 66
error: Verifying a signature, but no certificate was provided:
- error 67
error: Verifying a signature, but no certificate was provided:
- error 68
error: Verifying a signature, but no certificate was provided:
- error 69
error: Verifying a signature, but no certificate was provided:
- error 70
error: Verifying a signature, but no certificate was provided:
- error 71
error: Verifying a signature, but no certificate was provided:
- error 72
error: Verifying a signature, but no certificate was provided:
- error 73
error: Verifying a signature, but no certificate was provided:
- error 74
error: Verifying a signature, but no certificate was provided:
- error 75
error: Verifying a signature, but no certificate was provided:
- error 76
error: Verifying a signature, but no certificate was provided:
- error 77
error: Verifying a signature, but no certificate was provided:
- error 78
error: Verifying a signature, but no certificate was provided:
- error 79
error: Verifying a signature, but no certificate was provided:
- error 80
error: Verifying a signature, but no certificate was provided:
- error 81
error: Verifying a signature, but no certificate was provided:
- error 82
error: Verifying a signature, but no certificate was provided:
- error 83
error: Verifying a signature, but no certificate was provided:
- error 84
error: Verifying a signature, but no certificate was provided:
- error 85
error: Verifying a signature, but no certificate was provided:
- error 86
error: Verifying a signature, but no certificate was provided:
- error 87
error: Verifying a signature, but no certificate was provided:
- error 88
error: Verifying a signature, but no certificate was provided:
- error 89
error: Verifying a signature, but no certificate was provided:
- error 90
error: Verifying a signature, but no certificate was provided:
- error 91
error: Verifying a signature, but no certificate was provided:
- error 92
error: Verifying a signature, but no certificate was provided:
- error 93
error: Verifying a signature, but no certificate was provided:
- error 94
error: Verifying a signature, but no certificate was provided:
- error 95
error: Verifying a signature, but no certificate was provided:
- error 96
error: Verifying a signature, but no certificate was provided:
- error 97
error: Verifying a signature, but no certificate was provided:
- error 98
error: Verifying a signature, but no certificate was provided:
- error 99
error: Verifying a signature, but no certificate was provided:
- error 100
error: Verifying a signature, but no certificate was provided:
- error 101
error: Verifying a signature, but no certificate was provided:
- error 102
error: Verifying a signature, but no certificate was provided:
- error 103
error: Verifying a signature, but no certificate was provided:
- error 104
error: Verifying a signature, but no certificate was provided:
- error 105
error: Verifying a signature, but no certificate was provided:
- error 106
error: Verifying a signature, but no certificate was provided:
- error 107
error: Verifying a signature, but no certificate was provided:
- error 108
error: Verifying a signature, but no certificate was provided:
- error 109
error: Verifying a signature, but no certificate was provided:
- error 110
error: Verifying a signature, but no certificate was provided:
- error 111
error: Verifying a signature, but no certificate was provided:
- error 112
error: Verifying a signature, but no certificate was provided:
- error 113
error: Verifying a signature, but no certificate was provided:
- error 114
error: Verifying a signature, but no certificate was provided:
- error 115
error: Verifying a signature, but no certificate was provided:
- error 116
error: Verifying a signature, but no certificate was provided:
- error 117
error: Verifying a signature, but no certificate was provided:
- error 118
error: Verifying a signature, but no certificate was provided:
- error 119
error: Verifying a signature, but no certificate was provided:
- error 120
error: Verifying a signature, but no certificate was provided:
- error 121
error: Verifying a signature, but no certificate was provided:
- error 122
error: Verifying a signature, but no certificate was provided:
- error 123
error: Verifying a signature, but no certificate was provided:
- error 124
error: Verifying a signature, but no certificate was provided:
- error 125
error: Verifying a signature, but no certificate was provided:
- error 126
error: Verifying a signature, but no certificate was provided:
- error 127
error: Verifying a signature, but no certificate was provided:
- error 128
error: Verifying a signature, but no certificate was provided:
- error 129
error: Verifying a signature, but no certificate was provided:
- error 130
error: Verifying a signature, but no certificate was provided:
- error 131
error: Verifying a signature, but no certificate was provided:
- error 132
error: Verifying a signature, but no certificate was provided:
- error 133
error: Verifying a signature, but no certificate was provided:
- error 134
error: Verifying a signature, but no certificate was provided:
- error 135
error: Verifying a signature, but no certificate was provided:
- error 136
error: Verifying a signature, but no certificate was provided:
- error 137
error: Verifying a signature, but no certificate was provided:
- error 138
error: Verifying a signature, but no certificate was provided:
- error 139
error: Verifying a signature, but no certificate was provided:
- error 140
error: Verifying a signature, but no certificate was provided:
- error 141
error: Verifying a signature, but no certificate was provided:
- error 142
error: Verifying a signature, but no certificate was provided:
- error 143
error: Verifying a signature, but no certificate was provided:
- error 144
error: Verifying a signature, but no certificate was provided:
- error 145
error: Verifying a signature, but no certificate was provided:
- error 146
error: Verifying a signature, but no certificate was provided:
- error 147
error: Verifying a signature, but no certificate was provided:
- error 148
error: Verifying a signature, but no certificate was provided:
- error 149
error: Verifying a signature, but no certificate was provided:
- error 150
error: Verifying a signature, but no certificate was provided:
- error 151
error: Verifying a signature, but no certificate was provided:
- error 152
error: Verifying a signature, but no certificate was provided:
- error 153
error: Verifying a signature, but no certificate was provided:
- error 154
error: Verifying a signature, but no certificate was provided:
- error 155
error: Verifying a signature, but no certificate was provided:
- error 156
error: Verifying a signature, but no certificate was provided:
- error 157
error: Verifying a signature, but no certificate was provided:
- error 158
error: Verifying a signature, but no certificate was provided:
- error 159
error: Verifying a signature, but no certificate was provided:
- error 160
error: Verifying a signature, but no certificate was provided:
- error 161
error: Verifying a signature, but no certificate was provided:
- error 162
error: Verifying a signature, but no certificate was provided:
- error 163
error: Verifying a signature, but no certificate was provided:
- error 164
error: Verifying a signature, but no certificate was provided:
- error 165
error: Verifying a signature, but no certificate was provided:
- error 166
error: Verifying a signature, but no certificate was provided:
- error 167
error: Verifying a signature, but no certificate was provided:
- error 168
error: Verifying a signature, but no certificate was provided:
- error 169
error: Verifying a signature, but no certificate was provided:
- error 170
error: Verifying a signature, but no certificate was provided:
- error 171
error: Verifying a signature, but no certificate was provided:
- error 172
error: Verifying a signature, but no certificate was provided:
- error 173
error: Verifying a signature, but no certificate was provided:
- error 174
error: Verifying a signature, but no certificate was provided:
- error 175
error: Verifying a signature, but no certificate was provided:
- error 176
error: Verifying a signature, but no certificate was provided:
- error 177
error: Verifying a signature, but no certificate was provided:
- error 178
error: Verifying a signature, but no certificate was provided:
- error 179
error: Verifying a signature, but no certificate was provided:
- error 180
error: Verifying a signature, but no certificate was provided:
- error 181
error: Verifying a signature, but no certificate was provided:
- error 182
error: Verifying a signature, but no certificate was provided:
- error 183
error: Verifying a signature, but no certificate was provided:
- error 184
error: rpmdbNextIterator: skipping h# 382
- error 185
error: rpmdbNextIterator: skipping h# 385
- error 186
error: Verifying a signature, but no certificate was provided:
- error 187
error: Verifying a signature, but no certificate was provided:
- error 188
error: Verifying a signature, but no certificate was provided:
- error 189
error: Verifying a signature, but no certificate was provided:
- error 190
error: Verifying a signature, but no certificate was provided:
- error 191
error: Verifying a signature, but no certificate was provided:
- error 192
error: Verifying a signature, but no certificate was provided:
- error 193
error: Verifying a signature, but no certificate was provided:
- error 194
error: Verifying a signature, but no certificate was provided:
- error 195
error: Verifying a signature, but no certificate was provided:
- error 196
error: Verifying a signature, but no certificate was provided:
- error 197
error: rpmdbNextIterator: skipping h# 417
- error 198
error: rpmdbNextIterator: skipping h# 418
- error 199
error: Verifying a signature, but no certificate was provided:
- error 200
error: Verifying a signature, but no certificate was provided:
- error 201
error: Verifying a signature, but no certificate was provided:
- error 202
error: Verifying a signature, but no certificate was provided:
- error 203
error: Verifying a signature, but no certificate was provided:
- error 204
error: Verifying a signature, but no certificate was provided:
- error 205
error: Verifying a signature, but no certificate was provided:
- error 206
error: Verifying a signature, but no certificate was provided:
- error 207
error: Verifying a signature, but no certificate was provided:
- error 208
error: Verifying a signature, but no certificate was provided:
- error 209
error: Verifying a signature, but no certificate was provided:
- error 210
error: Verifying a signature, but no certificate was provided:
- error 211
error: Verifying a signature, but no certificate was provided:
- error 212
error: Verifying a signature, but no certificate was provided:
- error 213
error: Verifying a signature, but no certificate was provided:
- error 214
error: Verifying a signature, but no certificate was provided:
- error 215
error: rpmdbNextIterator: skipping h# 470
- error 216
error: rpmdbNextIterator: skipping h# 471
- error 217
error: Verifying a signature, but no certificate was provided:
- error 218
error: rpmdbNextIterator: skipping h# 472
- error 219
error: rpmdbNextIterator: skipping h# 473
- error 220
error: rpmdbNextIterator: skipping h# 474
- error 221
error: rpmdbNextIterator: skipping h# 476
- error 222
error: rpmdbNextIterator: skipping h# 477
- error 223
error: Verifying a signature, but no certificate was provided:
- error 224
error: Verifying a signature, but no certificate was provided:
- error 225
error: Verifying a signature, but no certificate was provided:
- error 226
error: Verifying a signature, but no certificate was provided:
- error 227
error: Verifying a signature, but no certificate was provided:
- error 228
error: Verifying a signature, but no certificate was provided:
- error 229
error: Verifying a signature, but no certificate was provided:
- error 230
error: Verifying a signature, but no certificate was provided:
- error 231
error: Verifying a signature, but no certificate was provided:
- error 232
error: rpmdbNextIterator: skipping h# 491
- error 233
error: rpmdbNextIterator: skipping h# 492
- error 234
error: Verifying a signature, but no certificate was provided:
- error 235
error: Verifying a signature, but no certificate was provided:
- error 236
error: Verifying a signature, but no certificate was provided:
- error 237
error: Verifying a signature, but no certificate was provided:
- error 238
error: Verifying a signature, but no certificate was provided:
- error 239
error: Verifying a signature, but no certificate was provided:
- error 240
error: Verifying a signature, but no certificate was provided:
- error 241
error: Verifying a signature, but no certificate was provided:
- error 242
error: Verifying a signature, but no certificate was provided:
- error 243
error: Verifying a signature, but no certificate was provided:
- error 244
error: Verifying a signature, but no certificate was provided:
- error 245
error: Verifying a signature, but no certificate was provided:
- error 246
error: Verifying a signature, but no certificate was provided:
- error 247
error: Verifying a signature, but no certificate was provided:
- error 248
error: Verifying a signature, but no certificate was provided:
- error 249
error: Verifying a signature, but no certificate was provided:
- error 250
error: Verifying a signature, but no certificate was provided:
- error 251
error: Verifying a signature, but no certificate was provided:
- error 252
error: Verifying a signature, but no certificate was provided:
- error 253
error: Verifying a signature, but no certificate was provided:
- error 254
error: Verifying a signature, but no certificate was provided:
- error 255
error: Verifying a signature, but no certificate was provided:
- error 256
error: Verifying a signature, but no certificate was provided:
- error 257
error: Verifying a signature, but no certificate was provided:
- error 258
error: Verifying a signature, but no certificate was provided:
- error 259
error: Verifying a signature, but no certificate was provided:
- error 260
error: Verifying a signature, but no certificate was provided:
- error 261
error: Verifying a signature, but no certificate was provided:
- error 262
error: Verifying a signature, but no certificate was provided:
- error 263
error: Verifying a signature, but no certificate was provided:
- error 264
error: Verifying a signature, but no certificate was provided:
- error 265
error: Verifying a signature, but no certificate was provided:
- error 266
error: Verifying a signature, but no certificate was provided:
- error 267
error: rpmdbNextIterator: skipping h# 554
- error 268
error: Verifying a signature, but no certificate was provided:
- error 269
error: Verifying a signature, but no certificate was provided:
- error 270
error: Verifying a signature, but no certificate was provided:
- error 271
error: Verifying a signature, but no certificate was provided:
- error 272
error: Verifying a signature, but no certificate was provided:
- error 273
error: Verifying a signature, but no certificate was provided:
- error 274
error: Verifying a signature, but no certificate was provided:
- error 275
error: rpmdbNextIterator: skipping h# 587
- error 276
error: Verifying a signature, but no certificate was provided:
- error 277
error: Verifying a signature, but no certificate was provided:
- error 278
error: Verifying a signature, but no certificate was provided:
- error 279
error: Verifying a signature, but no certificate was provided:
- error 280
error: Verifying a signature, but no certificate was provided:
- error 281
error: Verifying a signature, but no certificate was provided:
- error 282
error: Verifying a signature, but no certificate was provided:
- error 283
error: Verifying a signature, but no certificate was provided:
- error 284
error: Verifying a signature, but no certificate was provided:
- error 285
error: Verifying a signature, but no certificate was provided:
- error 286
error: Verifying a signature, but no certificate was provided:
- error 287
error: Verifying a signature, but no certificate was provided:
- error 288
error: Verifying a signature, but no certificate was provided:
- error 289
error: Verifying a signature, but no certificate was provided:
- error 290
error: Verifying a signature, but no certificate was provided:
- error 291
error: Verifying a signature, but no certificate was provided:
- error 292
error: Verifying a signature, but no certificate was provided:
- error 293
error: Verifying a signature, but no certificate was provided:
- error 294
error: Verifying a signature, but no certificate was provided:
- error 295
error: Verifying a signature, but no certificate was provided:
- error 296
error: Verifying a signature, but no certificate was provided:
- error 297
error: Verifying a signature, but no certificate was provided:
- error 298
error: Verifying a signature, but no certificate was provided:
- error 299
error: Verifying a signature, but no certificate was provided:
- error 300
error: Verifying a signature, but no certificate was provided:
- error 301
error: Verifying a signature, but no certificate was provided:
- error 302
error: Verifying a signature, but no certificate was provided:
- error 303
error: Verifying a signature, but no certificate was provided:
- error 304
error: Verifying a signature, but no certificate was provided:
- error 305
error: Verifying a signature, but no certificate was provided:
- error 306
error: Verifying a signature, but no certificate was provided:
- error 307
error: Verifying a signature, but no certificate was provided:
- error 308
error: Verifying a signature, but no certificate was provided:
- error 309
error: Verifying a signature, but no certificate was provided:
- error 310
error: Verifying a signature, but no certificate was provided:
- error 311
error: Verifying a signature, but no certificate was provided:
- error 312
error: Verifying a signature, but no certificate was provided:
- error 313
error: Verifying a signature, but no certificate was provided:
- error 314
error: Verifying a signature, but no certificate was provided:
- error 315
error: Verifying a signature, but no certificate was provided:
- error 316
error: Verifying a signature, but no certificate was provided:
- error 317
error: Verifying a signature, but no certificate was provided:
- error 318
error: Verifying a signature, but no certificate was provided:
- error 319
error: Verifying a signature, but no certificate was provided:
- error 320
error: Verifying a signature, but no certificate was provided:
- error 321
error: Verifying a signature, but no certificate was provided:
- error 322
error: Verifying a signature, but no certificate was provided:
- error 323
error: Verifying a signature, but no certificate was provided:
- error 324
error: Verifying a signature, but no certificate was provided:
- error 325
error: Verifying a signature, but no certificate was provided:
- error 326
error: Verifying a signature, but no certificate was provided:
- error 327
error: Verifying a signature, but no certificate was provided:
- error 328
error: Verifying a signature, but no certificate was provided:
- error 329
error: Verifying a signature, but no certificate was provided:
- error 330
error: Verifying a signature, but no certificate was provided:
- error 331
error: Verifying a signature, but no certificate was provided:
- error 332
error: Verifying a signature, but no certificate was provided:
- error 333
error: Verifying a signature, but no certificate was provided:
- error 334
error: Verifying a signature, but no certificate was provided:
- error 335
error: Verifying a signature, but no certificate was provided:
- error 336
error: Verifying a signature, but no certificate was provided:
- error 337
error: Verifying a signature, but no certificate was provided:
- error 338
error: Verifying a signature, but no certificate was provided:
- error 339
error: Verifying a signature, but no certificate was provided:
- error 340
error: Verifying a signature, but no certificate was provided:
- error 341
error: Verifying a signature, but no certificate was provided:
- error 342
error: Verifying a signature, but no certificate was provided:
- error 343
error: Verifying a signature, but no certificate was provided:
- error 344
error: Verifying a signature, but no certificate was provided:
- error 345
error: Verifying a signature, but no certificate was provided:
- error 346
error: Verifying a signature, but no certificate was provided:
- error 347
error: Verifying a signature, but no certificate was provided:
- error 348
error: Verifying a signature, but no certificate was provided:
- error 349
error: Verifying a signature, but no certificate was provided:
- error 350
error: Verifying a signature, but no certificate was provided:
- error 351
error: Verifying a signature, but no certificate was provided:
- error 352
error: Verifying a signature, but no certificate was provided:
- error 353
error: Verifying a signature, but no certificate was provided:
- error 354
error: Verifying a signature, but no certificate was provided:
- error 355
error: Verifying a signature, but no certificate was provided:
- error 356
error: Verifying a signature, but no certificate was provided:
- error 357
error: Verifying a signature, but no certificate was provided:
- error 358
error: Verifying a signature, but no certificate was provided:
- error 359
error: Verifying a signature, but no certificate was provided:
- error 360
error: Verifying a signature, but no certificate was provided:
- error 361
error: Verifying a signature, but no certificate was provided:
- error 362
error: rpmdbNextIterator: skipping h# 751
- error 363
error: Verifying a signature, but no certificate was provided:
- error 364
error: Verifying a signature, but no certificate was provided:
- error 365
error: Verifying a signature, but no certificate was provided:
- error 366
error: Verifying a signature, but no certificate was provided:
- error 367
error: Verifying a signature, but no certificate was provided:
- error 368
error: Verifying a signature, but no certificate was provided:
- error 369
error: Verifying a signature, but no certificate was provided:
- error 370
error: Verifying a signature, but no certificate was provided:
- error 371
error: rpmdbNextIterator: skipping h# 777
- error 372
error: rpmdbNextIterator: skipping h# 778
- error 373
error: rpmdbNextIterator: skipping h# 779
- error 374
error: Verifying a signature, but no certificate was provided:
- error 375
error: rpmdbNextIterator: skipping h# 796
- error 376
error: rpmdbNextIterator: skipping h# 797
- error 377
error: rpmdbNextIterator: skipping h# 798
- error 378
error: rpmdbNextIterator: skipping h# 799
- error 379
error: rpmdbNextIterator: skipping h# 800
- error 380
error: Verifying a signature, but no certificate was provided:
- error 381
error: rpmdbNextIterator: skipping h# 801
- error 382
error: rpmdbNextIterator: skipping h# 802
- error 383
error: Verifying a signature, but no certificate was provided:
- error 384
error: Verifying a signature, but no certificate was provided:
- error 385
error: Verifying a signature, but no certificate was provided:
- error 386
error: Verifying a signature, but no certificate was provided:
- error 387
error: Verifying a signature, but no certificate was provided:
- error 388
error: rpmdbNextIterator: skipping h# 817
- error 389
error: rpmdbNextIterator: skipping h# 818
- error 390
error: rpmdbNextIterator: skipping h# 819
- error 391
error: Verifying a signature, but no certificate was provided:
- error 392
error: Verifying a signature, but no certificate was provided:
- error 393
error: Verifying a signature, but no certificate was provided:
- error 394
error: Verifying a signature, but no certificate was provided:
- error 395
error: rpmdbNextIterator: skipping h# 832
- error 396
error: rpmdbNextIterator: skipping h# 833
- error 397
error: Verifying a signature, but no certificate was provided:
- error 398
error: rpmdbNextIterator: skipping h# 834
- error 399
error: rpmdbNextIterator: skipping h# 842
- error 400
error: Verifying a signature, but no certificate was provided:
- error 401
error: Verifying a signature, but no certificate was provided:
- error 402
error: Verifying a signature, but no certificate was provided:
- error 403
error: Verifying a signature, but no certificate was provided:
- error 404
error: Verifying a signature, but no certificate was provided:
- error 405
error: Verifying a signature, but no certificate was provided:
- error 406
error: Verifying a signature, but no certificate was provided:
- error 407
error: Verifying a signature, but no certificate was provided:
- error 408
error: Verifying a signature, but no certificate was provided:
- error 409
error: Verifying a signature, but no certificate was provided:
- error 410
error: Verifying a signature, but no certificate was provided:
- error 411
error: Verifying a signature, but no certificate was provided:
- error 412
error: Verifying a signature, but no certificate was provided:
- error 413
error: rpmdbNextIterator: skipping h# 863
- error 414
error: rpmdbNextIterator: skipping h# 864
- error 415
error: rpmdbNextIterator: skipping h# 865
- error 416
error: rpmdbNextIterator: skipping h# 866
- error 417
error: rpmdbNextIterator: skipping h# 871
- error 418
error: Verifying a signature, but no certificate was provided:
- error 419
error: Verifying a signature, but no certificate was provided:
- error 420
error: Verifying a signature, but no certificate was provided:
- error 421
error: Verifying a signature, but no certificate was provided:
- error 422
error: Verifying a signature, but no certificate was provided:
- error 423
error: Verifying a signature, but no certificate was provided:
- error 424
error: Verifying a signature, but no certificate was provided:
- error 425
error: Verifying a signature, but no certificate was provided:
- error 426
error: rpmdbNextIterator: skipping h# 912
- error 427
error: rpmdbNextIterator: skipping h# 913
- error 428
error: Verifying a signature, but no certificate was provided:
- error 429
error: rpmdbNextIterator: skipping h# 919
- error 430
error: rpmdbNextIterator: skipping h# 920
- error 431
error: Verifying a signature, but no certificate was provided:
- error 432
error: rpmdbNextIterator: skipping h# 921
- error 433
error: Verifying a signature, but no certificate was provided:
- error 434
error: Verifying a signature, but no certificate was provided:
- error 435
error: Verifying a signature, but no certificate was provided:
- error 436
error: rpmdbNextIterator: skipping h# 928
- error 437
error: rpmdbNextIterator: skipping h# 929
- error 438
error: Verifying a signature, but no certificate was provided:
- error 439
error: Verifying a signature, but no certificate was provided:
- error 440
error: Verifying a signature, but no certificate was provided:
- error 441
error: Verifying a signature, but no certificate was provided:
- error 442
error: Verifying a signature, but no certificate was provided:
- error 443
error: Verifying a signature, but no certificate was provided:
- error 444
error: Verifying a signature, but no certificate was provided:
- error 445
error: rpmdbNextIterator: skipping h# 942
- error 446
error: rpmdbNextIterator: skipping h# 949
- error 447
error: Verifying a signature, but no certificate was provided:
- error 448
error: rpmdbNextIterator: skipping h# 950
- error 449
error: rpmdbNextIterator: skipping h# 951
- error 450
error: rpmdbNextIterator: skipping h# 955
- error 451
error: rpmdbNextIterator: skipping h# 956
- error 452
error: rpmdbNextIterator: skipping h# 961
- error 453
error: rpmdbNextIterator: skipping h# 962
- error 454
error: rpmdbNextIterator: skipping h# 977
- error 455
error: rpmdbNextIterator: skipping h# 978
- error 456
error: Verifying a signature, but no certificate was provided:
- error 457
error: Verifying a signature, but no certificate was provided:
- error 458
error: Verifying a signature, but no certificate was provided:
- error 459
error: Verifying a signature, but no certificate was provided:
- error 460
error: Verifying a signature, but no certificate was provided:
- error 461
error: Verifying a signature, but no certificate was provided:
- error 462
error: Verifying a signature, but no certificate was provided:
- error 463
error: Verifying a signature, but no certificate was provided:
- error 464
error: Verifying a signature, but no certificate was provided:
- error 465
error: Verifying a signature, but no certificate was provided:
- error 466
error: Verifying a signature, but no certificate was provided:
- error 467
error: Verifying a signature, but no certificate was provided:
- error 468
error: Verifying a signature, but no certificate was provided:
- error 469
error: Verifying a signature, but no certificate was provided:
- error 470
error: Verifying a signature, but no certificate was provided:
- error 471
error: Verifying a signature, but no certificate was provided:
- error 472
error: Verifying a signature, but no certificate was provided:
- error 473
error: rpmdbNextIterator: skipping h# 1028
- error 474
error: rpmdbNextIterator: skipping h# 1029
- error 475
error: rpmdbNextIterator: skipping h# 1030
- error 476
error: rpmdbNextIterator: skipping h# 1031
- error 477
error: Verifying a signature, but no certificate was provided:
- error 478
error: Verifying a signature, but no certificate was provided:
- error 479
error: rpmdbNextIterator: skipping h# 1041
- error 480
error: rpmdbNextIterator: skipping h# 1042
- error 481
error: rpmdbNextIterator: skipping h# 1046
- error 482
error: Verifying a signature, but no certificate was provided:
- error 483
error: Verifying a signature, but no certificate was provided:
- error 484
error: rpmdbNextIterator: skipping h# 1055
- error 485
error: Verifying a signature, but no certificate was provided:
- error 486
error: Verifying a signature, but no certificate was provided:
- error 487
error: Verifying a signature, but no certificate was provided:
- error 488
error: Verifying a signature, but no certificate was provided:
- error 489
error: Verifying a signature, but no certificate was provided:
- error 490
error: Verifying a signature, but no certificate was provided:
- error 491
error: Verifying a signature, but no certificate was provided:
- error 492
error: Verifying a signature, but no certificate was provided:
- error 493
error: Verifying a signature, but no certificate was provided:
- error 494
error: Verifying a signature, but no certificate was provided:
- error 495
error: Verifying a signature, but no certificate was provided:
- error 496
error: Verifying a signature, but no certificate was provided:
- error 497
error: Verifying a signature, but no certificate was provided:
- error 498
error: rpmdbNextIterator: skipping h# 1080
- error 499
error: rpmdbNextIterator: skipping h# 1084
- error 500
error: rpmdbNextIterator: skipping h# 1086
- error 501
error: Verifying a signature, but no certificate was provided:
- error 502
error: Verifying a signature, but no certificate was provided:
- error 503
error: rpmdbNextIterator: skipping h# 1103
- error 504
error: rpmdbNextIterator: skipping h# 1106
- error 505
error: rpmdbNextIterator: skipping h# 1107
- error 506
error: Verifying a signature, but no certificate was provided:
- error 507
error: Verifying a signature, but no certificate was provided:
- error 508
error: Verifying a signature, but no certificate was provided:
- error 509
error: Verifying a signature, but no certificate was provided:
- error 510
error: Verifying a signature, but no certificate was provided:
- error 511
error: Verifying a signature, but no certificate was provided:
- error 512
error: Verifying a signature, but no certificate was provided:
- error 513
error: Verifying a signature, but no certificate was provided:
- error 514
error: Verifying a signature, but no certificate was provided:
- error 515
error: Verifying a signature, but no certificate was provided:
- error 516
error: Verifying a signature, but no certificate was provided:
- error 517
error: Verifying a signature, but no certificate was provided:
- error 518
error: Verifying a signature, but no certificate was provided:
- error 519
error: Verifying a signature, but no certificate was provided:
- error 520
error: Verifying a signature, but no certificate was provided:
- error 521
error: Verifying a signature, but no certificate was provided:
- error 522
error: Verifying a signature, but no certificate was provided:
- error 523
error: rpmdbNextIterator: skipping h# 1173
- error 524
error: rpmdbNextIterator: skipping h# 1174
- error 525
error: rpmdbNextIterator: skipping h# 1175
- error 526
error: rpmdbNextIterator: skipping h# 1176
- error 527
error: Verifying a signature, but no certificate was provided:
- error 528
error: rpmdbNextIterator: skipping h# 1177
- error 529
error: rpmdbNextIterator: skipping h# 1178
- error 530
error: Verifying a signature, but no certificate was provided:
- error 531
error: rpmdbNextIterator: skipping h# 1180
- error 532
error: rpmdbNextIterator: skipping h# 1181
- error 533
error: rpmdbNextIterator: skipping h# 1182
- error 534
error: Verifying a signature, but no certificate was provided:
- error 535
error: rpmdbNextIterator: skipping h# 1183
- error 536
error: rpmdbNextIterator: skipping h# 1186
- error 537
error: Verifying a signature, but no certificate was provided:
- error 538
error: rpmdbNextIterator: skipping h# 1187
- error 539
error: Verifying a signature, but no certificate was provided:
- error 540
error: rpmdbNextIterator: skipping h# 1198
- error 541
error: Verifying a signature, but no certificate was provided:
- error 542
error: Verifying a signature, but no certificate was provided:
- error 543
error: Verifying a signature, but no certificate was provided:
- error 544
error: Verifying a signature, but no certificate was provided:
- error 545
error: Verifying a signature, but no certificate was provided:
- error 546
error: Verifying a signature, but no certificate was provided:
- error 547
error: Verifying a signature, but no certificate was provided:
- error 548
error: Verifying a signature, but no certificate was provided:
- error 549
error: Verifying a signature, but no certificate was provided:
- error 550
error: rpmdbNextIterator: skipping h# 1227
- error 551
error: Verifying a signature, but no certificate was provided:
- error 552
error: Verifying a signature, but no certificate was provided:
- error 553
error: rpmdbNextIterator: skipping h# 1236
- error 554
error: rpmdbNextIterator: skipping h# 1237
- error 555
error: Verifying a signature, but no certificate was provided:
- error 556
error: Verifying a signature, but no certificate was provided:
- error 557
error: Verifying a signature, but no certificate was provided:
- error 558
error: Verifying a signature, but no certificate was provided:
- error 559
error: Verifying a signature, but no certificate was provided:
- error 560
error: Verifying a signature, but no certificate was provided:
- error 561
error: Verifying a signature, but no certificate was provided:
- error 562
error: Verifying a signature, but no certificate was provided:
- error 563
error: Verifying a signature, but no certificate was provided:
- error 564
error: Verifying a signature, but no certificate was provided:
- error 565
error: rpmdbNextIterator: skipping h# 1282
- error 566
error: rpmdbNextIterator: skipping h# 1290
- error 567
error: rpmdbNextIterator: skipping h# 1291
- error 568
error: Verifying a signature, but no certificate was provided:
- error 569
error: rpmdbNextIterator: skipping h# 1293
- error 570
error: rpmdbNextIterator: skipping h# 1294
- error 571
error: rpmdbNextIterator: skipping h# 1295
- error 572
error: rpmdbNextIterator: skipping h# 1296
- error 573
error: rpmdbNextIterator: skipping h# 1297
- error 574
error: rpmdbNextIterator: skipping h# 1298
- error 575
error: rpmdbNextIterator: skipping h# 1305
- error 576
error: rpmdbNextIterator: skipping h# 1306
- error 577
error: Verifying a signature, but no certificate was provided:
- error 578
error: Verifying a signature, but no certificate was provided:
- error 579
error: Verifying a signature, but no certificate was provided:
- error 580
error: rpmdbNextIterator: skipping h# 1356
- error 581
error: rpmdbNextIterator: skipping h# 1357
- error 582
error: rpmdbNextIterator: skipping h# 1363
- error 583
error: rpmdbNextIterator: skipping h# 1373
- error 584
error: Verifying a signature, but no certificate was provided:
- error 585
error: Verifying a signature, but no certificate was provided:
- error 586
error: rpmdbNextIterator: skipping h# 1383
- error 587
error: Verifying a signature, but no certificate was provided:
- error 588
error: rpmdbNextIterator: skipping h# 1393
- error 589
error: rpmdbNextIterator: skipping h# 1394
- error 590
error: Verifying a signature, but no certificate was provided:
- error 591
error: Verifying a signature, but no certificate was provided:
- error 592
error: Verifying a signature, but no certificate was provided:
- error 593
error: Verifying a signature, but no certificate was provided:
- error 594
error: Verifying a signature, but no certificate was provided:
- error 595
error: Verifying a signature, but no certificate was provided:
- error 596
error: rpmdbNextIterator: skipping h# 1424
- error 597
error: rpmdbNextIterator: skipping h# 1425
- error 598
error: rpmdbNextIterator: skipping h# 1433
- error 599
error: rpmdbNextIterator: skipping h# 1434
- error 600
error: rpmdbNextIterator: skipping h# 1435
- error 601
error: rpmdbNextIterator: skipping h# 1444
- error 602
error: rpmdbNextIterator: skipping h# 1445
- error 603
error: Verifying a signature, but no certificate was provided:
- error 604
error: Verifying a signature, but no certificate was provided:
- error 605
error: Verifying a signature, but no certificate was provided:
- error 606
error: Verifying a signature, but no certificate was provided:
- error 607
error: Verifying a signature, but no certificate was provided:
- error 608
error: Verifying a signature, but no certificate was provided:
- error 609
error: Verifying a signature, but no certificate was provided:
- error 610
error: Verifying a signature, but no certificate was provided:
- error 611
error: Verifying a signature, but no certificate was provided:
- error 612
error: Verifying a signature, but no certificate was provided:
- error 613
error: rpmdbNextIterator: skipping h# 1493
- error 614
error: rpmdbNextIterator: skipping h# 1507
- error 615
error: rpmdbNextIterator: skipping h# 1508
- error 616
error: rpmdbNextIterator: skipping h# 1509
- error 617
error: rpmdbNextIterator: skipping h# 1510
- error 618
error: rpmdbNextIterator: skipping h# 1511
- error 619
error: rpmdbNextIterator: skipping h# 1515
- error 620
error: rpmdbNextIterator: skipping h# 1516
- error 621
error: rpmdbNextIterator: skipping h# 1519
- error 622
error: Verifying a signature, but no certificate was provided:
- error 623
error: Verifying a signature, but no certificate was provided:
- error 624
error: Verifying a signature, but no certificate was provided:
- error 625
error: Verifying a signature, but no certificate was provided:
- error 626
error: rpmdbNextIterator: skipping h# 1538
- error 627
error: rpmdbNextIterator: skipping h# 1543
- error 628
error: rpmdbNextIterator: skipping h# 1544
- error 629
error: rpmdbNextIterator: skipping h# 1547
- error 630
error: rpmdbNextIterator: skipping h# 1548
- error 631
error: rpmdbNextIterator: skipping h# 1549
- error 632
error: Verifying a signature, but no certificate was provided:
- error 633
error: Verifying a signature, but no certificate was provided:
- error 634
error: Verifying a signature, but no certificate was provided:
- error 635
error: Verifying a signature, but no certificate was provided:
- error 636
error: Verifying a signature, but no certificate was provided:
- error 637
error: Verifying a signature, but no certificate was provided:
- error 638
error: rpmdbNextIterator: skipping h# 1574
- error 639
error: rpmdbNextIterator: skipping h# 1579
- error 640
error: rpmdbNextIterator: skipping h# 1581
- error 641
error: Verifying a signature, but no certificate was provided:
- error 642
error: rpmdbNextIterator: skipping h# 1586
- error 643
error: rpmdbNextIterator: skipping h# 1587
- error 644
error: Verifying a signature, but no certificate was provided:
- error 645
error: rpmdbNextIterator: skipping h# 1588
- error 646
error: rpmdbNextIterator: skipping h# 1589
- error 647
error: rpmdbNextIterator: skipping h# 1594
- error 648
error: rpmdbNextIterator: skipping h# 1595
- error 649
error: rpmdbNextIterator: skipping h# 1606
- error 650
error: Verifying a signature, but no certificate was provided:
- error 651
error: rpmdbNextIterator: skipping h# 1661
- error 652
error: rpmdbNextIterator: skipping h# 1687
- error 653
error: rpmdbNextIterator: skipping h# 1737
- error 654
error: rpmdbNextIterator: skipping h# 1738
- error 655
error: rpmdbNextIterator: skipping h# 1739
- error 656
error: rpmdbNextIterator: skipping h# 1742
- error 657
error: Verifying a signature, but no certificate was provided:
- error 658
error: Verifying a signature, but no certificate was provided:
- error 659
error: Verifying a signature, but no certificate was provided:
- error 660
error: Verifying a signature, but no certificate was provided:
- error 661
error: Verifying a signature, but no certificate was provided:
- error 662
error: Verifying a signature, but no certificate was provided:
- error 663
error: rpmdbNextIterator: skipping h# 1830
- error 664
error: rpmdbNextIterator: skipping h# 1862
- error 665
error: rpmdbNextIterator: skipping h# 1863
- error 666
error: rpmdbNextIterator: skipping h# 1868
- error 667
error: rpmdbNextIterator: skipping h# 1869
- error 668
error: Verifying a signature, but no certificate was provided:
- error 669
error: rpmdbNextIterator: skipping h# 1874
- error 670
error: Verifying a signature, but no certificate was provided:
- error 671
error: Verifying a signature, but no certificate was provided:
- error 672
error: rpmdbNextIterator: skipping h# 1891
- error 673
error: rpmdbNextIterator: skipping h# 1904
- error 674
error: rpmdbNextIterator: skipping h# 1905
- error 675
error: rpmdbNextIterator: skipping h# 1907
- error 676
error: Verifying a signature, but no certificate was provided:
- error 677
error: rpmdbNextIterator: skipping h# 1908
- error 678
error: rpmdbNextIterator: skipping h# 1909
- error 679
error: rpmdbNextIterator: skipping h# 1910
- error 680
error: Verifying a signature, but no certificate was provided:
- error 681
error: rpmdbNextIterator: skipping h# 1911
- error 682
error: Verifying a signature, but no certificate was provided:
- error 683
error: Verifying a signature, but no certificate was provided:
- error 684
error: rpmdbNextIterator: skipping h# 2211
- error 685
error: Verifying a signature, but no certificate was provided:
- error 686
error: Verifying a signature, but no certificate was provided:
- error 687
error: Verifying a signature, but no certificate was provided:
- error 688
error: Verifying a signature, but no certificate was provided:
- error 689
error: Verifying a signature, but no certificate was provided:
- error 690
error: Verifying a signature, but no certificate was provided:
- error 691
error: rpmdbNextIterator: skipping h# 2373
- error 692
error: rpmdbNextIterator: skipping h# 2374
- error 693
error: rpmdbNextIterator: skipping h# 2375
- error 694
error: rpmdbNextIterator: skipping h# 2393
- error 695
error: Verifying a signature, but no certificate was provided:
- error 696
error: Verifying a signature, but no certificate was provided:
- error 697
error: Verifying a signature, but no certificate was provided:
- error 698
error: rpmdbNextIterator: skipping h# 2462
- error 699
error: rpmdbNextIterator: skipping h# 2463
- error 700
error: Verifying a signature, but no certificate was provided:
- error 701
error: Verifying a signature, but no certificate was provided:
- error 702
error: rpmdbNextIterator: skipping h# 2486
- error 703
error: Verifying a signature, but no certificate was provided:
- error 704
error: rpmdbNextIterator: skipping h# 2487
- error 705
error: rpmdbNextIterator: skipping h# 2488
- error 706
error: rpmdbNextIterator: skipping h# 2489
- error 707
error: Verifying a signature, but no certificate was provided:
- error 708
error: rpmdbNextIterator: skipping h# 2490
- error 709
error: rpmdbNextIterator: skipping h# 2491
- error 710
error: rpmdbNextIterator: skipping h# 2493
- error 711
error: rpmdbNextIterator: skipping h# 2494
- error 712
error: Verifying a signature, but no certificate was provided:
- error 713
error: rpmdbNextIterator: skipping h# 2495
- error 714
error: Verifying a signature, but no certificate was provided:
- error 715
error: rpmdbNextIterator: skipping h# 2507
- error 716
error: rpmdbNextIterator: skipping h# 2515
- error 717
error: rpmdbNextIterator: skipping h# 2516
- error 718
error: Verifying a signature, but no certificate was provided:
- error 719
error: rpmdbNextIterator: skipping h# 2517
- error 720
error: rpmdbNextIterator: skipping h# 2518
- error 721
error: rpmdbNextIterator: skipping h# 2527
- error 722
error: rpmdbNextIterator: skipping h# 2530
- error 723
error: rpmdbNextIterator: skipping h# 2535
- error 724
error: rpmdbNextIterator: skipping h# 2575
- error 725
error: Verifying a signature, but no certificate was provided:
- error 726
error: rpmdbNextIterator: skipping h# 2585
- error 727
error: Verifying a signature, but no certificate was provided:
- error 728
error: Verifying a signature, but no certificate was provided:
- error 729
error: Verifying a signature, but no certificate was provided:
- error 730
error: rpmdbNextIterator: skipping h# 2592
- error 731
error: rpmdbNextIterator: skipping h# 2593
- error 732
error: Verifying a signature, but no certificate was provided:
- error 733
error: rpmdbNextIterator: skipping h# 2594
- error 734
error: rpmdbNextIterator: skipping h# 2595
- error 735
error: rpmdbNextIterator: skipping h# 2631
- error 736
error: Verifying a signature, but no certificate was provided:
- error 737
error: Verifying a signature, but no certificate was provided:
- error 738
error: Verifying a signature, but no certificate was provided:
- error 739
error: rpmdbNextIterator: skipping h# 2707
- error 740
error: rpmdbNextIterator: skipping h# 2708
- error 741
error: rpmdbNextIterator: skipping h# 2709
- error 742
error: Verifying a signature, but no certificate was provided:
- error 743
error: Verifying a signature, but no certificate was provided:
- error 744
error: Verifying a signature, but no certificate was provided:
- error 745
error: Verifying a signature, but no certificate was provided:
- error 746
error: rpmdbNextIterator: skipping h# 2725
- error 747
error: rpmdbNextIterator: skipping h# 2726
- error 748
error: rpmdbNextIterator: skipping h# 2746
- error 749
error: Verifying a signature, but no certificate was provided:
- error 750
error: rpmdbNextIterator: skipping h# 2819
- error 751
error: Verifying a signature, but no certificate was provided:
- error 752
error: Verifying a signature, but no certificate was provided:
- error 753
error: Verifying a signature, but no certificate was provided:
- error 754
error: rpmdbNextIterator: skipping h# 2896
- error 755
error: rpmdbNextIterator: skipping h# 2897
- error 756
error: rpmdbNextIterator: skipping h# 2912
- error 757
error: rpmdbNextIterator: skipping h# 2913
- error 758
error: Verifying a signature, but no certificate was provided:
- error 759
error: rpmdbNextIterator: skipping h# 2916
- error 760
error: rpmdbNextIterator: skipping h# 2917
- error 761
error: rpmdbNextIterator: skipping h# 2918
- error 762
error: rpmdbNextIterator: skipping h# 2928
- error 763
error: rpmdbNextIterator: skipping h# 2929
- error 764
error: rpmdbNextIterator: skipping h# 2938
- error 765
error: Verifying a signature, but no certificate was provided:
- error 766
error: rpmdbNextIterator: skipping h# 2939
- error 767
error: rpmdbNextIterator: skipping h# 2941
- error 768
error: rpmdbNextIterator: skipping h# 2942
- error 769
error: rpmdbNextIterator: skipping h# 3030
- error 770
error: Verifying a signature, but no certificate was provided:
- error 771
error: rpmdbNextIterator: skipping h# 3031
- error 772
error: Verifying a signature, but no certificate was provided:
- error 773
error: rpmdbNextIterator: skipping h# 3032
- error 774
error: rpmdbNextIterator: skipping h# 3033
- error 775
error: rpmdbNextIterator: skipping h# 3041
- error 776
error: rpmdbNextIterator: skipping h# 3076
- error 777
error: Verifying a signature, but no certificate was provided:
- error 778
error: rpmdbNextIterator: skipping h# 3121
- error 779
error: rpmdbNextIterator: skipping h# 3122
- error 780
error: rpmdbNextIterator: skipping h# 3125
- error 781
error: rpmdbNextIterator: skipping h# 3126
- error 782
error: rpmdbNextIterator: skipping h# 3127
- error 783
error: rpmdbNextIterator: skipping h# 3128
- error 784
error: rpmdbNextIterator: skipping h# 3132
- error 785
error: rpmdbNextIterator: skipping h# 3133
- error 786
error: Verifying a signature, but no certificate was provided:
- error 787
error: Verifying a signature, but no certificate was provided:
- error 788
error: rpmdbNextIterator: skipping h# 3146
- error 789
error: rpmdbNextIterator: skipping h# 3147
- error 790
error: rpmdbNextIterator: skipping h# 3187
- error 791
error: rpmdbNextIterator: skipping h# 3188
- error 792
error: rpmdbNextIterator: skipping h# 3189
- error 793
error: rpmdbNextIterator: skipping h# 3190
- error 794
error: rpmdbNextIterator: skipping h# 3206
- error 795
error: rpmdbNextIterator: skipping h# 3207
- error 796
error: rpmdbNextIterator: skipping h# 3242
- error 797
error: rpmdbNextIterator: skipping h# 3243
- error 798
error: rpmdbNextIterator: skipping h# 3260
- error 799
error: rpmdbNextIterator: skipping h# 3261
- error 800
error: rpmdbNextIterator: skipping h# 3445
- error 801
error: rpmdbNextIterator: skipping h# 3446
- error 802
error: rpmdbNextIterator: skipping h# 3463
- error 803
error: Verifying a signature, but no certificate was provided:
- error 804
error: rpmdbNextIterator: skipping h# 3464
- error 805
error: rpmdbNextIterator: skipping h# 3469
- error 806
error: rpmdbNextIterator: skipping h# 3470
- error 807
error: rpmdbNextIterator: skipping h# 3478
- error 808
error: Verifying a signature, but no certificate was provided:
- error 809
error: rpmdbNextIterator: skipping h# 3479
- error 810
error: rpmdbNextIterator: skipping h# 3481
- error 811
error: rpmdbNextIterator: skipping h# 3482
- error 812
error: rpmdbNextIterator: skipping h# 3488
- error 813
error: rpmdbNextIterator: skipping h# 3489
- error 814
error: rpmdbNextIterator: skipping h# 3517
- error 815
error: rpmdbNextIterator: skipping h# 3670
- error 816
error: Verifying a signature, but no certificate was provided:
- error 817
error: rpmdbNextIterator: skipping h# 3725
- error 818
error: rpmdbNextIterator: skipping h# 3726
- error 819
error: rpmdbNextIterator: skipping h# 3774
- error 820
error: Verifying a signature, but no certificate was provided:
- error 821
error: rpmdbNextIterator: skipping h# 3775
- error 822
error: rpmdbNextIterator: skipping h# 3829
- error 823
error: rpmdbNextIterator: skipping h# 3830
- error 824
error: rpmdbNextIterator: skipping h# 3902
- error 825
error: rpmdbNextIterator: skipping h# 3903
- error 826
error: Verifying a signature, but no certificate was provided:
- error 827
error: Verifying a signature, but no certificate was provided:
- error 828
error: Verifying a signature, but no certificate was provided:
- error 829
error: Verifying a signature, but no certificate was provided:
- error 830
error: Verifying a signature, but no certificate was provided:
- error 831
error: rpmdbNextIterator: skipping h# 3948
- error 832
error: rpmdbNextIterator: skipping h# 3949
- error 833
error: rpmdbNextIterator: skipping h# 3979
- error 834
error: rpmdbNextIterator: skipping h# 4005
- error 835
error: rpmdbNextIterator: skipping h# 4055
- error 836
error: rpmdbNextIterator: skipping h# 4058
- error 837
error: rpmdbNextIterator: skipping h# 4059
- error 838
error: rpmdbNextIterator: skipping h# 4086
- error 839
error: Verifying a signature, but no certificate was provided:
- error 840
error: rpmdbNextIterator: skipping h# 4087
- error 841
error: rpmdbNextIterator: skipping h# 4088
- error 842
error: rpmdbNextIterator: skipping h# 4137
- error 843
error: rpmdbNextIterator: skipping h# 4138
- error 844
error: rpmdbNextIterator: skipping h# 4267
- error 845
error: rpmdbNextIterator: skipping h# 4269
- error 846
error: Verifying a signature, but no certificate was provided:
- error 847
error: rpmdbNextIterator: skipping h# 4270
- error 848
error: rpmdbNextIterator: skipping h# 4273
- error 849
error: rpmdbNextIterator: skipping h# 4291
- error 850
error: rpmdbNextIterator: skipping h# 4293
- error 851
error: rpmdbNextIterator: skipping h# 4343
- error 852
error: rpmdbNextIterator: skipping h# 4364
- error 853
error: rpmdbNextIterator: skipping h# 4365
- error 854
error: rpmdbNextIterator: skipping h# 4398
- error 855
error: rpmdbNextIterator: skipping h# 4606
- error 856
error: rpmdbNextIterator: skipping h# 4607
- error 857
error: rpmdbNextIterator: skipping h# 4632
- error 858
error: rpmdbNextIterator: skipping h# 4633
- error 859
error: Verifying a signature, but no certificate was provided:
- error 860
error: rpmdbNextIterator: skipping h# 4638
- error 861
error: Verifying a signature, but no certificate was provided:
- error 862
error: rpmdbNextIterator: skipping h# 4652
- error 863
error: rpmdbNextIterator: skipping h# 4653
- error 864
error: rpmdbNextIterator: skipping h# 4656
- error 865
error: Verifying a signature, but no certificate was provided:
- error 866
error: rpmdbNextIterator: skipping h# 4686
- error 867
error: Verifying a signature, but no certificate was provided:
- error 868
error: rpmdbNextIterator: skipping h# 4691
- error 869
error: rpmdbNextIterator: skipping h# 4692
- error 870
error: rpmdbNextIterator: skipping h# 4708
- error 871
error: rpmdbNextIterator: skipping h# 4776
- error 872
error: Verifying a signature, but no certificate was provided:
- error 873
error: Verifying a signature, but no certificate was provided:
- error 874
error: rpmdbNextIterator: skipping h# 4797
- error 875
error: rpmdbNextIterator: skipping h# 4798
- error 876
error: rpmdbNextIterator: skipping h# 4801
- error 877
error: Verifying a signature, but no certificate was provided:
- error 878
error: rpmdbNextIterator: skipping h# 4802
- error 879
error: Verifying a signature, but no certificate was provided:
- error 880
error: rpmdbNextIterator: skipping h# 4865
- error 881
error: rpmdbNextIterator: skipping h# 4866
- error 882
error: Verifying a signature, but no certificate was provided:
- error 883
error: Verifying a signature, but no certificate was provided:
- error 884
error: rpmdbNextIterator: skipping h# 4870
- error 885
error: rpmdbNextIterator: skipping h# 4903
- error 886
error: rpmdbNextIterator: skipping h# 5019
- error 887
error: rpmdbNextIterator: skipping h# 5029
- error 888
error: rpmdbNextIterator: skipping h# 5031
- error 889
error: rpmdbNextIterator: skipping h# 5059
- error 890
error: rpmdbNextIterator: skipping h# 5060
- error 891
error: rpmdbNextIterator: skipping h# 5170
- error 892
error: rpmdbNextIterator: skipping h# 5171
- error 893
error: rpmdbNextIterator: skipping h# 5193
- error 894
error: Verifying a signature, but no certificate was provided:
- error 895
error: Verifying a signature, but no certificate was provided:
- error 896
error: Verifying a signature, but no certificate was provided:
- error 897
error: rpmdbNextIterator: skipping h# 5259
- error 898
error: rpmdbNextIterator: skipping h# 5260
- error 899
error: rpmdbNextIterator: skipping h# 5263
- error 900
error: rpmdbNextIterator: skipping h# 5264
- error 901
error: rpmdbNextIterator: skipping h# 5313
- error 902
error: rpmdbNextIterator: skipping h# 5427
- error 903
error: rpmdbNextIterator: skipping h# 5428
- error 904
error: rpmdbNextIterator: skipping h# 5429
- error 905
error: rpmdbNextIterator: skipping h# 5430
- error 906
error: rpmdbNextIterator: skipping h# 5431
- error 907
error: Verifying a signature, but no certificate was provided:
- error 908
error: rpmdbNextIterator: skipping h# 5434
- error 909
error: Verifying a signature, but no certificate was provided:
- error 910
error: rpmdbNextIterator: skipping h# 5463
- error 911
error: rpmdbNextIterator: skipping h# 5464
- error 912
error: Verifying a signature, but no certificate was provided:
- error 913
error: Verifying a signature, but no certificate was provided:
- error 914
error: Verifying a signature, but no certificate was provided:
- error 915
error: Verifying a signature, but no certificate was provided:
- error 916
error: rpmdbNextIterator: skipping h# 5618
- error 917
error: rpmdbNextIterator: skipping h# 5619
- error 918
error: rpmdbNextIterator: skipping h# 5721
- error 919
error: Verifying a signature, but no certificate was provided:
- error 920
error: Verifying a signature, but no certificate was provided:
- error 921
error: Verifying a signature, but no certificate was provided:
- error 922
error: Verifying a signature, but no certificate was provided:
- error 923
error: Verifying a signature, but no certificate was provided:
- error 924
error: Verifying a signature, but no certificate was provided:
- error 925
error: Verifying a signature, but no certificate was provided:
- error 926
error: Verifying a signature, but no certificate was provided:
- error 927
error: Verifying a signature, but no certificate was provided:
- error 928
error: Verifying a signature, but no certificate was provided:
- error 929
error: Verifying a signature, but no certificate was provided:
- error 930
error: Verifying a signature, but no certificate was provided:
- error 931
error: Verifying a signature, but no certificate was provided:
- error 932
error: Verifying a signature, but no certificate was provided:
- error 933
error: Verifying a signature, but no certificate was provided:
- error 934
error: Verifying a signature, but no certificate was provided:
- error 935
error: Verifying a signature, but no certificate was provided:
- error 936
error: Verifying a signature, but no certificate was provided:
- error 937
error: Verifying a signature, but no certificate was provided:
- error 938
error: Verifying a signature, but no certificate was provided:
- error 939
error: Verifying a signature, but no certificate was provided:
- error 940
error: Verifying a signature, but no certificate was provided:
- error 941
error: Verifying a signature, but no certificate was provided:
- error 942
error: Verifying a signature, but no certificate was provided:
- error 943
error: Verifying a signature, but no certificate was provided:
- error 944
error: Verifying a signature, but no certificate was provided:
- error 945
error: Verifying a signature, but no certificate was provided:
- error 946
error: Verifying a signature, but no certificate was provided:
- error 947
error: Verifying a signature, but no certificate was provided:
- error 948
error: Verifying a signature, but no certificate was provided:
- error 949
error: Verifying a signature, but no certificate was provided:
- error 950
error: Verifying a signature, but no certificate was provided:
- error 951
error: Verifying a signature, but no certificate was provided:
- error 952
error: Verifying a signature, but no certificate was provided:
- error 953
error: Verifying a signature, but no certificate was provided:
- error 954
error: Verifying a signature, but no certificate was provided:
- error 955
error: Verifying a signature, but no certificate was provided:
- error 956
error: Verifying a signature, but no certificate was provided:
- error 957
error: Verifying a signature, but no certificate was provided:
- error 958
error: Verifying a signature, but no certificate was provided:
- error 959
error: Verifying a signature, but no certificate was provided:
- error 960
error: Verifying a signature, but no certificate was provided:
- error 961
error: Verifying a signature, but no certificate was provided:
- error 962
error: Verifying a signature, but no certificate was provided:
- error 963
error: Verifying a signature, but no certificate was provided:
- error 964
error: Verifying a signature, but no certificate was provided:
- error 965
error: Verifying a signature, but no certificate was provided:
- error 966
error: Verifying a signature, but no certificate was provided:
- error 967
error: Verifying a signature, but no certificate was provided:
- error 968
error: Verifying a signature, but no certificate was provided:
- error 969
error: Verifying a signature, but no certificate was provided:
- error 970
error: Verifying a signature, but no certificate was provided:
- error 971
error: Verifying a signature, but no certificate was provided:
- error 972
error: Verifying a signature, but no certificate was provided:
- error 973
error: Verifying a signature, but no certificate was provided:
- error 974
error: Verifying a signature, but no certificate was provided:
- error 975
error: Verifying a signature, but no certificate was provided:
- error 976
error: Verifying a signature, but no certificate was provided:
- error 977
error: Verifying a signature, but no certificate was provided:
- error 978
error: Verifying a signature, but no certificate was provided:
- error 979
error: Verifying a signature, but no certificate was provided:
- error 980
error: Verifying a signature, but no certificate was provided:
- error 981
error: Verifying a signature, but no certificate was provided:
- error 982
error: Verifying a signature, but no certificate was provided:
- error 983
error: Verifying a signature, but no certificate was provided:
- error 984
error: Verifying a signature, but no certificate was provided:
- error 985
error: Verifying a signature, but no certificate was provided:
- error 986
error: Verifying a signature, but no certificate was provided:
- error 987
error: Verifying a signature, but no certificate was provided:
- error 988
error: Verifying a signature, but no certificate was provided:
- error 989
error: Verifying a signature, but no certificate was provided:
- error 990
error: Verifying a signature, but no certificate was provided:
- error 991
error: Verifying a signature, but no certificate was provided:
- error 992
error: Verifying a signature, but no certificate was provided:
- error 993
error: Verifying a signature, but no certificate was provided:
- error 994
error: Verifying a signature, but no certificate was provided:
- error 995
error: Verifying a signature, but no certificate was provided:
- error 996
error: Verifying a signature, but no certificate was provided:
- error 997
error: Verifying a signature, but no certificate was provided:
- error 998
error: Verifying a signature, but no certificate was provided:
- error 999
error: Verifying a signature, but no certificate was provided:
- error 1000
error: Verifying a signature, but no certificate was provided:
- error 1001
error: Verifying a signature, but no certificate was provided:
- error 1002
error: Verifying a signature, but no certificate was provided:
- error 1003
error: Verifying a signature, but no certificate was provided:
- error 1004
error: Verifying a signature, but no certificate was provided:
- error 1005
error: Verifying a signature, but no certificate was provided:
- error 1006
error: Verifying a signature, but no certificate was provided:
- error 1007
error: Verifying a signature, but no certificate was provided:
- error 1008
error: Verifying a signature, but no certificate was provided:
- error 1009
error: Verifying a signature, but no certificate was provided:
- error 1010
error: Verifying a signature, but no certificate was provided:
- error 1011
error: Verifying a signature, but no certificate was provided:
- error 1012
error: Verifying a signature, but no certificate was provided:
- error 1013
error: Verifying a signature, but no certificate was provided:
- error 1014
error: Verifying a signature, but no certificate was provided:
- error 1015
error: Verifying a signature, but no certificate was provided:
- error 1016
error: Verifying a signature, but no certificate was provided:
- error 1017
error: Verifying a signature, but no certificate was provided:
- error 1018
error: Verifying a signature, but no certificate was provided:
- error 1019
error: Verifying a signature, but no certificate was provided:
- error 1020
error: Verifying a signature, but no certificate was provided:
- error 1021
error: Verifying a signature, but no certificate was provided:
- error 1022
error: Verifying a signature, but no certificate was provided:
- error 1023
error: Verifying a signature, but no certificate was provided:
- error 1024
error: Verifying a signature, but no certificate was provided:
- error 1025
error: Verifying a signature, but no certificate was provided:
- error 1026
error: Verifying a signature, but no certificate was provided:
- error 1027
error: Verifying a signature, but no certificate was provided:
- error 1028
error: Verifying a signature, but no certificate was provided:
- error 1029
error: Verifying a signature, but no certificate was provided:
- error 1030
error: Verifying a signature, but no certificate was provided:
- error 1031
error: Verifying a signature, but no certificate was provided:
- error 1032
error: Verifying a signature, but no certificate was provided:
- error 1033
error: Verifying a signature, but no certificate was provided:
- error 1034
error: Verifying a signature, but no certificate was provided:
- error 1035
error: Verifying a signature, but no certificate was provided:
- error 1036
error: Verifying a signature, but no certificate was provided:
- error 1037
error: Verifying a signature, but no certificate was provided:
- error 1038
error: Verifying a signature, but no certificate was provided:
- error 1039
error: Verifying a signature, but no certificate was provided:
- error 1040
error: Verifying a signature, but no certificate was provided:
- error 1041
error: Verifying a signature, but no certificate was provided:
- error 1042
error: Verifying a signature, but no certificate was provided:
- error 1043
error: Verifying a signature, but no certificate was provided:
- error 1044
error: Verifying a signature, but no certificate was provided:
- error 1045
error: Verifying a signature, but no certificate was provided:
- error 1046
error: Verifying a signature, but no certificate was provided:
- error 1047
error: Verifying a signature, but no certificate was provided:
- error 1048
error: Verifying a signature, but no certificate was provided:
- error 1049
error: Verifying a signature, but no certificate was provided:
- error 1050
error: Verifying a signature, but no certificate was provided:
- error 1051
error: Verifying a signature, but no certificate was provided:
- error 1052
error: Verifying a signature, but no certificate was provided:
- error 1053
error: Verifying a signature, but no certificate was provided:
- error 1054
error: Verifying a signature, but no certificate was provided:
- error 1055
error: Verifying a signature, but no certificate was provided:
- error 1056
error: Verifying a signature, but no certificate was provided:
- error 1057
error: Verifying a signature, but no certificate was provided:
- error 1058
error: Verifying a signature, but no certificate was provided:
- error 1059
error: Verifying a signature, but no certificate was provided:
- error 1060
error: Verifying a signature, but no certificate was provided:
- error 1061
error: Verifying a signature, but no certificate was provided:
- error 1062
error: Verifying a signature, but no certificate was provided:
- error 1063
error: Verifying a signature, but no certificate was provided:
- error 1064
error: Verifying a signature, but no certificate was provided:
- error 1065
error: Verifying a signature, but no certificate was provided:
- error 1066
error: Verifying a signature, but no certificate was provided:
- error 1067
error: Verifying a signature, but no certificate was provided:
- error 1068
error: Verifying a signature, but no certificate was provided:
- error 1069
error: Verifying a signature, but no certificate was provided:
- error 1070
error: Verifying a signature, but no certificate was provided:
- error 1071
error: Verifying a signature, but no certificate was provided:
- error 1072
error: Verifying a signature, but no certificate was provided:
- error 1073
error: Verifying a signature, but no certificate was provided:
- error 1074
error: Verifying a signature, but no certificate was provided:
- error 1075
error: Verifying a signature, but no certificate was provided:
- error 1076
error: Verifying a signature, but no certificate was provided:
- error 1077
error: Verifying a signature, but no certificate was provided:
- error 1078
error: Verifying a signature, but no certificate was provided:
- error 1079
error: Verifying a signature, but no certificate was provided:
- error 1080
error: Verifying a signature, but no certificate was provided:
- error 1081
error: Verifying a signature, but no certificate was provided:
- error 1082
error: Verifying a signature, but no certificate was provided:
- error 1083
error: Verifying a signature, but no certificate was provided:
- error 1084
error: Verifying a signature, but no certificate was provided:
- error 1085
error: Verifying a signature, but no certificate was provided:
- error 1086
error: Verifying a signature, but no certificate was provided:
- error 1087
error: Verifying a signature, but no certificate was provided:
- error 1088
error: Verifying a signature, but no certificate was provided:
- error 1089
error: Verifying a signature, but no certificate was provided:
- error 1090
error: Verifying a signature, but no certificate was provided:
- error 1091
error: Verifying a signature, but no certificate was provided:
- error 1092
error: Verifying a signature, but no certificate was provided:
- error 1093
error: Verifying a signature, but no certificate was provided:
- error 1094
error: Verifying a signature, but no certificate was provided:
- error 1095
error: Verifying a signature, but no certificate was provided:
- error 1096
error: Verifying a signature, but no certificate was provided:
- error 1097
error: Verifying a signature, but no certificate was provided:
- error 1098
error: Verifying a signature, but no certificate was provided:
- error 1099
error: Verifying a signature, but no certificate was provided:
- error 1100
error: Verifying a signature, but no certificate was provided:
- error 1101
error: Verifying a signature, but no certificate was provided:
- error 1102
error: Verifying a signature, but no certificate was provided:
- error 1103
error: Verifying a signature, but no certificate was provided:
- error 1104
error: Verifying a signature, but no certificate was provided:
- error 1105
error: Verifying a signature, but no certificate was provided:
- error 1106
error: Verifying a signature, but no certificate was provided:
- error 1107
error: Verifying a signature, but no certificate was provided:
- error 1108
error: Verifying a signature, but no certificate was provided:
- error 1109
error: Verifying a signature, but no certificate was provided:
- error 1110
error: Verifying a signature, but no certificate was provided:
- error 1111
error: Verifying a signature, but no certificate was provided:
- error 1112
error: Verifying a signature, but no certificate was provided:
- error 1113
error: Verifying a signature, but no certificate was provided:
- error 1114
error: Verifying a signature, but no certificate was provided:
- error 1115
error: Verifying a signature, but no certificate was provided:
- error 1116
error: Verifying a signature, but no certificate was provided:
- error 1117
error: Verifying a signature, but no certificate was provided:
- error 1118
error: Verifying a signature, but no certificate was provided:
- error 1119
error: Verifying a signature, but no certificate was provided:
- error 1120
error: Verifying a signature, but no certificate was provided:
- error 1121
error: Verifying a signature, but no certificate was provided:
- error 1122
error: Verifying a signature, but no certificate was provided:
- error 1123
error: Verifying a signature, but no certificate was provided:
- error 1124
error: Verifying a signature, but no certificate was provided:
- error 1125
error: Verifying a signature, but no certificate was provided:
- error 1126
error: Verifying a signature, but no certificate was provided:
- error 1127
error: Verifying a signature, but no certificate was provided:
- error 1128
error: Verifying a signature, but no certificate was provided:
- error 1129
error: Verifying a signature, but no certificate was provided:
- error 1130
error: Verifying a signature, but no certificate was provided:
- error 1131
error: Verifying a signature, but no certificate was provided:
- error 1132
error: Verifying a signature, but no certificate was provided:
- error 1133
error: Verifying a signature, but no certificate was provided:
- error 1134
error: Verifying a signature, but no certificate was provided:
- error 1135
error: Verifying a signature, but no certificate was provided:
- error 1136
error: Verifying a signature, but no certificate was provided:
- error 1137
error: Verifying a signature, but no certificate was provided:
- error 1138
error: Verifying a signature, but no certificate was provided:
- error 1139
error: Verifying a signature, but no certificate was provided:
- error 1140
error: Verifying a signature, but no certificate was provided:
- error 1141
error: Verifying a signature, but no certificate was provided:
- error 1142
error: Verifying a signature, but no certificate was provided:
- error 1143
error: Verifying a signature, but no certificate was provided:
- error 1144
error: Verifying a signature, but no certificate was provided:
- error 1145
error: Verifying a signature, but no certificate was provided:
- error 1146
error: Verifying a signature, but no certificate was provided:
- error 1147
error: Verifying a signature, but no certificate was provided:
- error 1148
error: Verifying a signature, but no certificate was provided:
- error 1149
error: Verifying a signature, but no certificate was provided:
- error 1150
error: Verifying a signature, but no certificate was provided:
- error 1151
error: Verifying a signature, but no certificate was provided:
- error 1152
error: Verifying a signature, but no certificate was provided:
- error 1153
error: Verifying a signature, but no certificate was provided:
- error 1154
error: Verifying a signature, but no certificate was provided:
- error 1155
error: Verifying a signature, but no certificate was provided:
- error 1156
error: Verifying a signature, but no certificate was provided:
- error 1157
error: Verifying a signature, but no certificate was provided:
- error 1158
error: Verifying a signature, but no certificate was provided:
- error 1159
error: Verifying a signature, but no certificate was provided:
- error 1160
error: Verifying a signature, but no certificate was provided:
- error 1161
error: Verifying a signature, but no certificate was provided:
- error 1162
error: Verifying a signature, but no certificate was provided:
- error 1163
error: Verifying a signature, but no certificate was provided:
- error 1164
error: Verifying a signature, but no certificate was provided:
- error 1165
error: Verifying a signature, but no certificate was provided:
- error 1166
error: Verifying a signature, but no certificate was provided:
- error 1167
error: Verifying a signature, but no certificate was provided:
- error 1168
error: Verifying a signature, but no certificate was provided:
- error 1169
error: Verifying a signature, but no certificate was provided:
- error 1170
error: Verifying a signature, but no certificate was provided:
- error 1171
error: Verifying a signature, but no certificate was provided:
- error 1172
error: Verifying a signature, but no certificate was provided:
- error 1173
error: Verifying a signature, but no certificate was provided:
- error 1174
error: Verifying a signature, but no certificate was provided:
- error 1175
error: Verifying a signature, but no certificate was provided:
- error 1176
error: Verifying a signature, but no certificate was provided:
- error 1177
error: Verifying a signature, but no certificate was provided:
- error 1178
error: Verifying a signature, but no certificate was provided:
- error 1179
error: Verifying a signature, but no certificate was provided:
- error 1180
error: Verifying a signature, but no certificate was provided:
- error 1181
error: Verifying a signature, but no certificate was provided:
- error 1182
error: Verifying a signature, but no certificate was provided:
- error 1183
error: Verifying a signature, but no certificate was provided:
- error 1184
error: Verifying a signature, but no certificate was provided:
- error 1185
error: Verifying a signature, but no certificate was provided:
- error 1186
error: Verifying a signature, but no certificate was provided:
- error 1187
error: Verifying a signature, but no certificate was provided:
- error 1188
error: Verifying a signature, but no certificate was provided:
- error 1189
error: Verifying a signature, but no certificate was provided:
- error 1190
error: Verifying a signature, but no certificate was provided:
- error 1191
error: Verifying a signature, but no certificate was provided:
- error 1192
error: Verifying a signature, but no certificate was provided:
- error 1193
error: Verifying a signature, but no certificate was provided:
- error 1194
error: Verifying a signature, but no certificate was provided:
- error 1195
error: Verifying a signature, but no certificate was provided:
- error 1196
error: Verifying a signature, but no certificate was provided:
- error 1197
error: Verifying a signature, but no certificate was provided:
- error 1198
error: Verifying a signature, but no certificate was provided:
- error 1199
error: Verifying a signature, but no certificate was provided:
- error 1200
error: Verifying a signature, but no certificate was provided:
- error 1201
error: Verifying a signature, but no certificate was provided:
- error 1202
error: Verifying a signature, but no certificate was provided:
- error 1203
error: Verifying a signature, but no certificate was provided:
- error 1204
error: Verifying a signature, but no certificate was provided:
- error 1205
error: Verifying a signature, but no certificate was provided:
- error 1206
error: Verifying a signature, but no certificate was provided:
- error 1207
error: Verifying a signature, but no certificate was provided:
- error 1208
error: Verifying a signature, but no certificate was provided:
- error 1209
error: Verifying a signature, but no certificate was provided:
- error 1210
error: Verifying a signature, but no certificate was provided:
- error 1211
error: Verifying a signature, but no certificate was provided:
- error 1212
error: Verifying a signature, but no certificate was provided:
- error 1213
error: Verifying a signature, but no certificate was provided:
- error 1214
error: Verifying a signature, but no certificate was provided:
- error 1215
error: Verifying a signature, but no certificate was provided:
- error 1216
error: Verifying a signature, but no certificate was provided:
- error 1217
error: Verifying a signature, but no certificate was provided:
- error 1218
error: Verifying a signature, but no certificate was provided:
- error 1219
error: Verifying a signature, but no certificate was provided:
- error 1220
error: Verifying a signature, but no certificate was provided:
- error 1221
error: Verifying a signature, but no certificate was provided:
- error 1222
error: Verifying a signature, but no certificate was provided:
- error 1223
error: Verifying a signature, but no certificate was provided:
- error 1224
error: Verifying a signature, but no certificate was provided:
- error 1225
error: Verifying a signature, but no certificate was provided:
- error 1226
error: Verifying a signature, but no certificate was provided:
- error 1227
error: Verifying a signature, but no certificate was provided:
- error 1228
error: Verifying a signature, but no certificate was provided:
- error 1229
error: Verifying a signature, but no certificate was provided:
- error 1230
error: Verifying a signature, but no certificate was provided:
- error 1231
error: Verifying a signature, but no certificate was provided:
- error 1232
error: Verifying a signature, but no certificate was provided:
- error 1233
error: Verifying a signature, but no certificate was provided:
- error 1234
error: Verifying a signature, but no certificate was provided:
- error 1235
error: Verifying a signature, but no certificate was provided:
- error 1236
error: Verifying a signature, but no certificate was provided:
- error 1237
error: Verifying a signature, but no certificate was provided:
- error 1238
error: Verifying a signature, but no certificate was provided:
- error 1239
error: Verifying a signature, but no certificate was provided:
- error 1240
error: Verifying a signature, but no certificate was provided:
- error 1241
error: Verifying a signature, but no certificate was provided:
- error 1242
error: Verifying a signature, but no certificate was provided:
- error 1243
error: Verifying a signature, but no certificate was provided:
- error 1244
error: Verifying a signature, but no certificate was provided:
- error 1245
error: Verifying a signature, but no certificate was provided:
- error 1246
error: Verifying a signature, but no certificate was provided:
- error 1247
error: Verifying a signature, but no certificate was provided:
- error 1248
error: Verifying a signature, but no certificate was provided:
- error 1249
error: Verifying a signature, but no certificate was provided:
- error 1250
error: Verifying a signature, but no certificate was provided:
- error 1251
error: Verifying a signature, but no certificate was provided:
- error 1252
error: Verifying a signature, but no certificate was provided:
- error 1253
error: Verifying a signature, but no certificate was provided:
- error 1254
error: Verifying a signature, but no certificate was provided:
- error 1255
error: Verifying a signature, but no certificate was provided:
- error 1256
error: Verifying a signature, but no certificate was provided:
- error 1257
error: Verifying a signature, but no certificate was provided:
- error 1258
error: Verifying a signature, but no certificate was provided:
- error 1259
error: Verifying a signature, but no certificate was provided:
- error 1260
error: Verifying a signature, but no certificate was provided:
- error 1261
error: Verifying a signature, but no certificate was provided:
- error 1262
error: Verifying a signature, but no certificate was provided:
- error 1263
error: Verifying a signature, but no certificate was provided:
- error 1264
error: Verifying a signature, but no certificate was provided:
- error 1265
error: Verifying a signature, but no certificate was provided:
- error 1266
error: Verifying a signature, but no certificate was provided:
- error 1267
error: Verifying a signature, but no certificate was provided:
- error 1268
error: Verifying a signature, but no certificate was provided:
- error 1269
error: Verifying a signature, but no certificate was provided:
- error 1270
error: Verifying a signature, but no certificate was provided:
- error 1271
error: Verifying a signature, but no certificate was provided:
- error 1272
error: Verifying a signature, but no certificate was provided:
- error 1273
error: Verifying a signature, but no certificate was provided:
- error 1274
error: Verifying a signature, but no certificate was provided:
- error 1275
error: Verifying a signature, but no certificate was provided:
- error 1276
error: Verifying a signature, but no certificate was provided:
- error 1277
error: Verifying a signature, but no certificate was provided:
- error 1278
error: Verifying a signature, but no certificate was provided:
- error 1279
error: Verifying a signature, but no certificate was provided:
- error 1280
error: Verifying a signature, but no certificate was provided:
- error 1281
error: Verifying a signature, but no certificate was provided:
- error 1282
error: Verifying a signature, but no certificate was provided:
- error 1283
error: Verifying a signature, but no certificate was provided:
- error 1284
error: Verifying a signature, but no certificate was provided:
- error 1285
error: Verifying a signature, but no certificate was provided:
- error 1286
error: Verifying a signature, but no certificate was provided:
- error 1287
error: Verifying a signature, but no certificate was provided:
- error 1288
error: Verifying a signature, but no certificate was provided:
- error 1289
error: Verifying a signature, but no certificate was provided:
- error 1290
error: Verifying a signature, but no certificate was provided:
- error 1291
error: Verifying a signature, but no certificate was provided:
- error 1292
error: Verifying a signature, but no certificate was provided:
- error 1293
error: Verifying a signature, but no certificate was provided:
- error 1294
error: Verifying a signature, but no certificate was provided:
- error 1295
error: Verifying a signature, but no certificate was provided:
- error 1296
error: Verifying a signature, but no certificate was provided:
- error 1297
error: Verifying a signature, but no certificate was provided:
- error 1298
error: Verifying a signature, but no certificate was provided:
- error 1299
error: Verifying a signature, but no certificate was provided:
- error 1300
error: Verifying a signature, but no certificate was provided:
- error 1301
error: Verifying a signature, but no certificate was provided:
- error 1302
error: Verifying a signature, but no certificate was provided:
- error 1303
error: Verifying a signature, but no certificate was provided:
- error 1304
error: Verifying a signature, but no certificate was provided:
- error 1305
error: Verifying a signature, but no certificate was provided:
- error 1306
error: Verifying a signature, but no certificate was provided:
- error 1307
error: Verifying a signature, but no certificate was provided:
- error 1308
error: Verifying a signature, but no certificate was provided:
- error 1309
error: Verifying a signature, but no certificate was provided:
- error 1310
error: Verifying a signature, but no certificate was provided:
- error 1311
error: Verifying a signature, but no certificate was provided:
- error 1312
error: Verifying a signature, but no certificate was provided:
- error 1313
error: Verifying a signature, but no certificate was provided:
- error 1314
error: Verifying a signature, but no certificate was provided:
- error 1315
error: Verifying a signature, but no certificate was provided:
- error 1316
error: Verifying a signature, but no certificate was provided:
- error 1317
error: Verifying a signature, but no certificate was provided:
- error 1318
error: Verifying a signature, but no certificate was provided:
- error 1319
error: Verifying a signature, but no certificate was provided:
- error 1320
error: Verifying a signature, but no certificate was provided:
- error 1321
error: Verifying a signature, but no certificate was provided:
- error 1322
error: Verifying a signature, but no certificate was provided:
- error 1323
error: Verifying a signature, but no certificate was provided:
- error 1324
error: Verifying a signature, but no certificate was provided:
- error 1325
error: Verifying a signature, but no certificate was provided:
- error 1326
error: Verifying a signature, but no certificate was provided:
- error 1327
error: Verifying a signature, but no certificate was provided:
- error 1328
error: Verifying a signature, but no certificate was provided:
- error 1329
error: Verifying a signature, but no certificate was provided:
- error 1330
error: Verifying a signature, but no certificate was provided:
- error 1331
error: Verifying a signature, but no certificate was provided:
- error 1332
error: Verifying a signature, but no certificate was provided:
- error 1333
error: Verifying a signature, but no certificate was provided:
- error 1334
error: Verifying a signature, but no certificate was provided:
- error 1335
error: Verifying a signature, but no certificate was provided:
- error 1336
error: Verifying a signature, but no certificate was provided:
- error 1337
error: Verifying a signature, but no certificate was provided:
- error 1338
error: Verifying a signature, but no certificate was provided:
- error 1339
error: Verifying a signature, but no certificate was provided:
- error 1340
error: Verifying a signature, but no certificate was provided:
- error 1341
error: Verifying a signature, but no certificate was provided:
- error 1342
error: Verifying a signature, but no certificate was provided:
- error 1343
error: Verifying a signature, but no certificate was provided:
- error 1344
error: Verifying a signature, but no certificate was provided:
- error 1345
error: Verifying a signature, but no certificate was provided:
- error 1346
error: Verifying a signature, but no certificate was provided:
- error 1347
error: Verifying a signature, but no certificate was provided:
- error 1348
error: Verifying a signature, but no certificate was provided:
- error 1349
error: Verifying a signature, but no certificate was provided:
- error 1350
error: Verifying a signature, but no certificate was provided:
- error 1351
error: Verifying a signature, but no certificate was provided:
- error 1352
error: Verifying a signature, but no certificate was provided:
- error 1353
error: Verifying a signature, but no certificate was provided:
- error 1354
error: Verifying a signature, but no certificate was provided:
- error 1355
error: Verifying a signature, but no certificate was provided:
- error 1356
error: Verifying a signature, but no certificate was provided:
- error 1357
error: Verifying a signature, but no certificate was provided:
- error 1358
error: Verifying a signature, but no certificate was provided:
- error 1359
error: Verifying a signature, but no certificate was provided:
- error 1360
error: Verifying a signature, but no certificate was provided:
- error 1361
error: Verifying a signature, but no certificate was provided:
- error 1362
error: Verifying a signature, but no certificate was provided:
- error 1363
error: Verifying a signature, but no certificate was provided:
- error 1364
error: Verifying a signature, but no certificate was provided:
- error 1365
error: Verifying a signature, but no certificate was provided:
- error 1366
error: Verifying a signature, but no certificate was provided:
- error 1367
error: Verifying a signature, but no certificate was provided:
- error 1368
error: Verifying a signature, but no certificate was provided:
- error 1369
error: Verifying a signature, but no certificate was provided:
- error 1370
error: Verifying a signature, but no certificate was provided:
- error 1371
error: Verifying a signature, but no certificate was provided:
- error 1372
error: Verifying a signature, but no certificate was provided:
- error 1373
error: Verifying a signature, but no certificate was provided:
- error 1374
error: Verifying a signature, but no certificate was provided:
- error 1375
error: Verifying a signature, but no certificate was provided:
- error 1376
error: Verifying a signature, but no certificate was provided:
- error 1377
error: Verifying a signature, but no certificate was provided:
- error 1378
error: Verifying a signature, but no certificate was provided:
- error 1379
error: Verifying a signature, but no certificate was provided:
- error 1380
error: Verifying a signature, but no certificate was provided:
- error 1381
error: Verifying a signature, but no certificate was provided:
- error 1382
error: Verifying a signature, but no certificate was provided:
- error 1383
error: Verifying a signature, but no certificate was provided:
- error 1384
error: Verifying a signature, but no certificate was provided:
- error 1385
error: Verifying a signature, but no certificate was provided:
- error 1386
error: Verifying a signature, but no certificate was provided:
- error 1387
error: Verifying a signature, but no certificate was provided:
- error 1388
error: Verifying a signature, but no certificate was provided:
- error 1389
error: Verifying a signature, but no certificate was provided:
- error 1390
error: Verifying a signature, but no certificate was provided:
- error 1391
error: Verifying a signature, but no certificate was provided:
- error 1392
error: Verifying a signature, but no certificate was provided:
- error 1393
error: Verifying a signature, but no certificate was provided:
- error 1394
error: Verifying a signature, but no certificate was provided:
- error 1395
error: Verifying a signature, but no certificate was provided:
- error 1396
error: Verifying a signature, but no certificate was provided:
- error 1397
error: Verifying a signature, but no certificate was provided:
- error 1398
error: Verifying a signature, but no certificate was provided:
- error 1399
error: Verifying a signature, but no certificate was provided:
- error 1400
error: Verifying a signature, but no certificate was provided:
- error 1401
error: Verifying a signature, but no certificate was provided:
- error 1402
error: Verifying a signature, but no certificate was provided:
- error 1403
error: Verifying a signature, but no certificate was provided:
- error 1404
error: Verifying a signature, but no certificate was provided:
- error 1405
error: Verifying a signature, but no certificate was provided:
- error 1406
error: Verifying a signature, but no certificate was provided:
- error 1407
error: Verifying a signature, but no certificate was provided:
- error 1408
error: Verifying a signature, but no certificate was provided:
- error 1409
error: Verifying a signature, but no certificate was provided:
- error 1410
error: Verifying a signature, but no certificate was provided:
- error 1411
error: Verifying a signature, but no certificate was provided:
- error 1412
error: Verifying a signature, but no certificate was provided:
- error 1413
error: Verifying a signature, but no certificate was provided:
- error 1414
error: Verifying a signature, but no certificate was provided:
- error 1415
error: Verifying a signature, but no certificate was provided:
- error 1416
error: Verifying a signature, but no certificate was provided:
- error 1417
error: Verifying a signature, but no certificate was provided:
- error 1418
error: Verifying a signature, but no certificate was provided:
- error 1419
error: Verifying a signature, but no certificate was provided:
- error 1420
error: Verifying a signature, but no certificate was provided:
- error 1421
error: Verifying a signature, but no certificate was provided:
- error 1422
error: Verifying a signature, but no certificate was provided:
- error 1423
error: Verifying a signature, but no certificate was provided:
- error 1424
error: Verifying a signature, but no certificate was provided:
- error 1425
error: Verifying a signature, but no certificate was provided:
- error 1426
error: Verifying a signature, but no certificate was provided:
- error 1427
error: Verifying a signature, but no certificate was provided:
- error 1428
error: Verifying a signature, but no certificate was provided:
- error 1429
error: Verifying a signature, but no certificate was provided:
- error 1430
error: Verifying a signature, but no certificate was provided:
- error 1431
error: Verifying a signature, but no certificate was provided:
- error 1432
error: Verifying a signature, but no certificate was provided:
- error 1433
error: Verifying a signature, but no certificate was provided:
- error 1434
error: Verifying a signature, but no certificate was provided:
- error 1435
error: Verifying a signature, but no certificate was provided:
- error 1436
error: Verifying a signature, but no certificate was provided:
- error 1437
error: Verifying a signature, but no certificate was provided:
- error 1438
error: Verifying a signature, but no certificate was provided:
- error 1439
error: Verifying a signature, but no certificate was provided:
- error 1440
error: Verifying a signature, but no certificate was provided:
- error 1441
error: Verifying a signature, but no certificate was provided:
- error 1442
error: Verifying a signature, but no certificate was provided:
- error 1443
error: Verifying a signature, but no certificate was provided:
- error 1444
error: Verifying a signature, but no certificate was provided:
- error 1445
error: Verifying a signature, but no certificate was provided:
- error 1446
error: Verifying a signature, but no certificate was provided:
- error 1447
error: Verifying a signature, but no certificate was provided:
- error 1448
error: Verifying a signature, but no certificate was provided:
- error 1449
error: Verifying a signature, but no certificate was provided:
- error 1450
error: Verifying a signature, but no certificate was provided:
- error 1451
error: Verifying a signature, but no certificate was provided:
- error 1452
error: Verifying a signature, but no certificate was provided:
- error 1453
error: Verifying a signature, but no certificate was provided:
- error 1454
error: Verifying a signature, but no certificate was provided:
- error 1455
error: Verifying a signature, but no certificate was provided:
- error 1456
error: Verifying a signature, but no certificate was provided:
- error 1457
error: Verifying a signature, but no certificate was provided:
- error 1458
error: Verifying a signature, but no certificate was provided:
- error 1459
error: Verifying a signature, but no certificate was provided:
- error 1460
error: Verifying a signature, but no certificate was provided:
- error 1461
error: Verifying a signature, but no certificate was provided:
- error 1462
error: Verifying a signature, but no certificate was provided:
- error 1463
error: Verifying a signature, but no certificate was provided:
- error 1464
error: Verifying a signature, but no certificate was provided:
- error 1465
error: Verifying a signature, but no certificate was provided:
- error 1466
error: Verifying a signature, but no certificate was provided:
- error 1467
error: Verifying a signature, but no certificate was provided:
- error 1468
error: Verifying a signature, but no certificate was provided:
- error 1469
error: Verifying a signature, but no certificate was provided:
- error 1470
error: Verifying a signature, but no certificate was provided:
- error 1471
error: Verifying a signature, but no certificate was provided:
- error 1472
error: Verifying a signature, but no certificate was provided:
- error 1473
error: Verifying a signature, but no certificate was provided:
- error 1474
error: Verifying a signature, but no certificate was provided:
- error 1475
error: Verifying a signature, but no certificate was provided:
- error 1476
error: Verifying a signature, but no certificate was provided:
- error 1477
error: Verifying a signature, but no certificate was provided:
- error 1478
error: Verifying a signature, but no certificate was provided:
- error 1479
error: Verifying a signature, but no certificate was provided:
- error 1480
error: Verifying a signature, but no certificate was provided:
- error 1481
error: Verifying a signature, but no certificate was provided:
- error 1482
error: Verifying a signature, but no certificate was provided:
- error 1483
error: Verifying a signature, but no certificate was provided:
- error 1484
error: Verifying a signature, but no certificate was provided:
- error 1485
error: Verifying a signature, but no certificate was provided:
- error 1486
error: Verifying a signature, but no certificate was provided:
- error 1487
error: Verifying a signature, but no certificate was provided:
- error 1488
error: Verifying a signature, but no certificate was provided:
- error 1489
error: Verifying a signature, but no certificate was provided:
- error 1490
error: Verifying a signature, but no certificate was provided:
- error 1491
error: Verifying a signature, but no certificate was provided:
- error 1492
error: Verifying a signature, but no certificate was provided:
- error 1493
error: Verifying a signature, but no certificate was provided:
- error 1494
error: Verifying a signature, but no certificate was provided:
- error 1495
error: Verifying a signature, but no certificate was provided:
- error 1496
error: Verifying a signature, but no certificate was provided:
- error 1497
error: Verifying a signature, but no certificate was provided:
- error 1498
error: Verifying a signature, but no certificate was provided:
- error 1499
error: Verifying a signature, but no certificate was provided:
- error 1500
error: Verifying a signature, but no certificate was provided:
- error 1501
error: Verifying a signature, but no certificate was provided:
- error 1502
error: Verifying a signature, but no certificate was provided:
- error 1503
error: Verifying a signature, but no certificate was provided:
- error 1504
error: Verifying a signature, but no certificate was provided:
- error 1505
error: Verifying a signature, but no certificate was provided:
- error 1506
error: Verifying a signature, but no certificate was provided:
- error 1507
error: Verifying a signature, but no certificate was provided:
- error 1508
error: Verifying a signature, but no certificate was provided:
- error 1509
error: Verifying a signature, but no certificate was provided:
- error 1510
error: Verifying a signature, but no certificate was provided:
- error 1511
error: Verifying a signature, but no certificate was provided:
- error 1512
error: Verifying a signature, but no certificate was provided:
- error 1513
error: Verifying a signature, but no certificate was provided:
- error 1514
error: Verifying a signature, but no certificate was provided:
- error 1515
error: Verifying a signature, but no certificate was provided:
- error 1516
error: Verifying a signature, but no certificate was provided:
- error 1517
error: Verifying a signature, but no certificate was provided:
- error 1518
error: Verifying a signature, but no certificate was provided:
- error 1519
error: Verifying a signature, but no certificate was provided:
- error 1520
error: Verifying a signature, but no certificate was provided:
- error 1521
error: Verifying a signature, but no certificate was provided:
- error 1522
error: Verifying a signature, but no certificate was provided:
- error 1523
error: Verifying a signature, but no certificate was provided:
- error 1524
error: Verifying a signature, but no certificate was provided:
- error 1525
error: Verifying a signature, but no certificate was provided:
- error 1526
error: Verifying a signature, but no certificate was provided:
- error 1527
error: Verifying a signature, but no certificate was provided:
- error 1528
error: Verifying a signature, but no certificate was provided:
- error 1529
error: Verifying a signature, but no certificate was provided:
- error 1530
error: Verifying a signature, but no certificate was provided:
- error 1531
error: Verifying a signature, but no certificate was provided:
- error 1532
error: Verifying a signature, but no certificate was provided:
- error 1533
error: Verifying a signature, but no certificate was provided:
- error 1534
error: Verifying a signature, but no certificate was provided:
- error 1535
error: Verifying a signature, but no certificate was provided:
- error 1536
error: Verifying a signature, but no certificate was provided:
- error 1537
error: Verifying a signature, but no certificate was provided:
- error 1538
error: Verifying a signature, but no certificate was provided:
- error 1539
error: Verifying a signature, but no certificate was provided:
- error 1540
error: Verifying a signature, but no certificate was provided:
- error 1541
error: Verifying a signature, but no certificate was provided:
- error 1542
error: Verifying a signature, but no certificate was provided:
- error 1543
error: Verifying a signature, but no certificate was provided:
- error 1544
error: Verifying a signature, but no certificate was provided:
- error 1545
error: Verifying a signature, but no certificate was provided:
- error 1546
error: Verifying a signature, but no certificate was provided:
- error 1547
error: Verifying a signature, but no certificate was provided:
- error 1548
error: Verifying a signature, but no certificate was provided:
- error 1549
error: Verifying a signature, but no certificate was provided:
- error 1550
error: Verifying a signature, but no certificate was provided:
- error 1551
error: Verifying a signature, but no certificate was provided:
- error 1552
error: Verifying a signature, but no certificate was provided:
- error 1553
error: Verifying a signature, but no certificate was provided:
- error 1554
error: Verifying a signature, but no certificate was provided:
- error 1555
error: Verifying a signature, but no certificate was provided:
- error 1556
error: Verifying a signature, but no certificate was provided:
- error 1557
error: Verifying a signature, but no certificate was provided:
- error 1558
error: Verifying a signature, but no certificate was provided:
- error 1559
error: Verifying a signature, but no certificate was provided:
- error 1560
error: Verifying a signature, but no certificate was provided:
- error 1561
error: Verifying a signature, but no certificate was provided:
- error 1562
error: Verifying a signature, but no certificate was provided:
- error 1563
error: Verifying a signature, but no certificate was provided:
- error 1564
error: Verifying a signature, but no certificate was provided:
- error 1565
error: Verifying a signature, but no certificate was provided:
- error 1566
error: Verifying a signature, but no certificate was provided:
- error 1567
error: Verifying a signature, but no certificate was provided:
- error 1568
error: Verifying a signature, but no certificate was provided:
- error 1569
error: Verifying a signature, but no certificate was provided:
- error 1570
error: Verifying a signature, but no certificate was provided:
- error 1571
error: Verifying a signature, but no certificate was provided:
- error 1572
error: Verifying a signature, but no certificate was provided:
- error 1573
error: Verifying a signature, but no certificate was provided:
- error 1574
error: Verifying a signature, but no certificate was provided:
- error 1575
error: Verifying a signature, but no certificate was provided:
- error 1576
error: Verifying a signature, but no certificate was provided:
- error 1577
error: Verifying a signature, but no certificate was provided:
- error 1578
error: Verifying a signature, but no certificate was provided:
- error 1579
error: Verifying a signature, but no certificate was provided:
- error 1580
error: Verifying a signature, but no certificate was provided:
- error 1581
error: Verifying a signature, but no certificate was provided:
- error 1582
error: Verifying a signature, but no certificate was provided:
- error 1583
error: Verifying a signature, but no certificate was provided:
- error 1584
error: Verifying a signature, but no certificate was provided:
- error 1585
error: Verifying a signature, but no certificate was provided:
- error 1586
error: Verifying a signature, but no certificate was provided:
- error 1587
error: Verifying a signature, but no certificate was provided:
- error 1588
error: Verifying a signature, but no certificate was provided:
- error 1589
error: Verifying a signature, but no certificate was provided:
- error 1590
error: Verifying a signature, but no certificate was provided:
- error 1591
error: Verifying a signature, but no certificate was provided:
- error 1592
error: Verifying a signature, but no certificate was provided:
- error 1593
error: Verifying a signature, but no certificate was provided:
- error 1594
error: Verifying a signature, but no certificate was provided:
- error 1595
error: Verifying a signature, but no certificate was provided:
- error 1596
error: Verifying a signature, but no certificate was provided:
- error 1597
error: Verifying a signature, but no certificate was provided:
- error 1598
error: Verifying a signature, but no certificate was provided:
- error 1599
error: Verifying a signature, but no certificate was provided:
- error 1600
error: Verifying a signature, but no certificate was provided:
- error 1601
error: Verifying a signature, but no certificate was provided:
- error 1602
error: Verifying a signature, but no certificate was provided:
- error 1603
error: Verifying a signature, but no certificate was provided:
- error 1604
error: Verifying a signature, but no certificate was provided:
- error 1605
error: Verifying a signature, but no certificate was provided:
- error 1606
error: Verifying a signature, but no certificate was provided:
- error 1607
error: Verifying a signature, but no certificate was provided:
- error 1608
error: Verifying a signature, but no certificate was provided:
- error 1609
error: Verifying a signature, but no certificate was provided:
- error 1610
error: Verifying a signature, but no certificate was provided:
- error 1611
error: Verifying a signature, but no certificate was provided:
- error 1612
error: Verifying a signature, but no certificate was provided:
- error 1613
error: Verifying a signature, but no certificate was provided:
- error 1614
error: Verifying a signature, but no certificate was provided:
- error 1615
error: Verifying a signature, but no certificate was provided:
- error 1616
error: Verifying a signature, but no certificate was provided:
- error 1617
error: Verifying a signature, but no certificate was provided:
- error 1618
error: Verifying a signature, but no certificate was provided:
- error 1619
error: Verifying a signature, but no certificate was provided:
- error 1620
error: Verifying a signature, but no certificate was provided:
- error 1621
error: Verifying a signature, but no certificate was provided:
- error 1622
error: Verifying a signature, but no certificate was provided:
- error 1623
error: Verifying a signature, but no certificate was provided:
- error 1624
error: Verifying a signature, but no certificate was provided:
- error 1625
error: Verifying a signature, but no certificate was provided:
- error 1626
error: Verifying a signature, but no certificate was provided:
- error 1627
error: Verifying a signature, but no certificate was provided:
- error 1628
error: Verifying a signature, but no certificate was provided:
- error 1629
error: Verifying a signature, but no certificate was provided:
- error 1630
error: Verifying a signature, but no certificate was provided:
- error 1631
error: Verifying a signature, but no certificate was provided:
- error 1632
error: Verifying a signature, but no certificate was provided:
- error 1633
error: Verifying a signature, but no certificate was provided:
- error 1634
error: Verifying a signature, but no certificate was provided:
- error 1635
error: Verifying a signature, but no certificate was provided:
- error 1636
error: Verifying a signature, but no certificate was provided:
- error 1637
error: Verifying a signature, but no certificate was provided:
- error 1638
error: Verifying a signature, but no certificate was provided:
- error 1639
error: Verifying a signature, but no certificate was provided:
- error 1640
error: Verifying a signature, but no certificate was provided:
- error 1641
error: Verifying a signature, but no certificate was provided:
- error 1642
error: Verifying a signature, but no certificate was provided:
- error 1643
error: Verifying a signature, but no certificate was provided:
- error 1644
error: Verifying a signature, but no certificate was provided:
- error 1645
error: Verifying a signature, but no certificate was provided:
- error 1646
error: Verifying a signature, but no certificate was provided:
- error 1647
error: Verifying a signature, but no certificate was provided:
- error 1648
error: Verifying a signature, but no certificate was provided:
- error 1649
error: Verifying a signature, but no certificate was provided:
- error 1650
error: Verifying a signature, but no certificate was provided:
- error 1651
error: Verifying a signature, but no certificate was provided:
- error 1652
error: Verifying a signature, but no certificate was provided:
- error 1653
error: Verifying a signature, but no certificate was provided:
- error 1654
error: Verifying a signature, but no certificate was provided:
- error 1655
error: Verifying a signature, but no certificate was provided:
- error 1656
error: Verifying a signature, but no certificate was provided:
- error 1657
error: Verifying a signature, but no certificate was provided:
- error 1658
error: Verifying a signature, but no certificate was provided:
- error 1659
error: Verifying a signature, but no certificate was provided:
- error 1660
error: Verifying a signature, but no certificate was provided:
- error 1661
error: Verifying a signature, but no certificate was provided:
- error 1662
error: Verifying a signature, but no certificate was provided:
- error 1663
error: Verifying a signature, but no certificate was provided:
- error 1664
error: Verifying a signature, but no certificate was provided:
- error 1665
error: Verifying a signature, but no certificate was provided:
- error 1666
error: Verifying a signature, but no certificate was provided:
- error 1667
error: Verifying a signature, but no certificate was provided:
- error 1668
error: Verifying a signature, but no certificate was provided:
- error 1669
error: Verifying a signature, but no certificate was provided:
- error 1670
error: Verifying a signature, but no certificate was provided:
- error 1671
error: Verifying a signature, but no certificate was provided:
- error 1672
error: Verifying a signature, but no certificate was provided:
- error 1673
error: Verifying a signature, but no certificate was provided:
- error 1674
error: Verifying a signature, but no certificate was provided:
- error 1675
error: Verifying a signature, but no certificate was provided:
- error 1676
error: Verifying a signature, but no certificate was provided:
- error 1677
error: Verifying a signature, but no certificate was provided:
- error 1678
error: Verifying a signature, but no certificate was provided:
- error 1679
error: Verifying a signature, but no certificate was provided:
- error 1680
error: Verifying a signature, but no certificate was provided:
- error 1681
error: Verifying a signature, but no certificate was provided:
- error 1682
error: Verifying a signature, but no certificate was provided:
- error 1683
error: Verifying a signature, but no certificate was provided:
- error 1684
error: Verifying a signature, but no certificate was provided:
- error 1685
error: Verifying a signature, but no certificate was provided:
- error 1686
error: Verifying a signature, but no certificate was provided:
- error 1687
error: Verifying a signature, but no certificate was provided:
- error 1688
error: Verifying a signature, but no certificate was provided:
- error 1689
error: Verifying a signature, but no certificate was provided:
- error 1690
error: Verifying a signature, but no certificate was provided:
- error 1691
error: Verifying a signature, but no certificate was provided:
- error 1692
error: Verifying a signature, but no certificate was provided:
- error 1693
error: Verifying a signature, but no certificate was provided:
- error 1694
error: Verifying a signature, but no certificate was provided:
- error 1695
error: Verifying a signature, but no certificate was provided:
- error 1696
error: Verifying a signature, but no certificate was provided:
- error 1697
error: Verifying a signature, but no certificate was provided:
- error 1698
error: Verifying a signature, but no certificate was provided:
- error 1699
error: Verifying a signature, but no certificate was provided:
- error 1700
error: Verifying a signature, but no certificate was provided:
- error 1701
error: Verifying a signature, but no certificate was provided:
- error 1702
error: Verifying a signature, but no certificate was provided:
- error 1703
error: Verifying a signature, but no certificate was provided:
- error 1704
error: Verifying a signature, but no certificate was provided:
- error 1705
error: Verifying a signature, but no certificate was provided:
- error 1706
error: Verifying a signature, but no certificate was provided:
- error 1707
error: Verifying a signature, but no certificate was provided:
- error 1708
error: Verifying a signature, but no certificate was provided:
- error 1709
error: Verifying a signature, but no certificate was provided:
- error 1710
error: Verifying a signature, but no certificate was provided:
- error 1711
error: Verifying a signature, but no certificate was provided:
- error 1712
error: Verifying a signature, but no certificate was provided:
- error 1713
error: Verifying a signature, but no certificate was provided:
- error 1714
error: Verifying a signature, but no certificate was provided:
- error 1715
error: Verifying a signature, but no certificate was provided:
- error 1716
error: Verifying a signature, but no certificate was provided:
- error 1717
error: Verifying a signature, but no certificate was provided:
- error 1718
error: Verifying a signature, but no certificate was provided:
- error 1719
error: Verifying a signature, but no certificate was provided:
- error 1720
error: Verifying a signature, but no certificate was provided:
- error 1721
error: Verifying a signature, but no certificate was provided:
- error 1722
error: Verifying a signature, but no certificate was provided:
- error 1723
error: Verifying a signature, but no certificate was provided:
- error 1724
error: Verifying a signature, but no certificate was provided:
- error 1725
error: Verifying a signature, but no certificate was provided:
- error 1726
error: Verifying a signature, but no certificate was provided:
- error 1727
error: Verifying a signature, but no certificate was provided:
- error 1728
error: Verifying a signature, but no certificate was provided:
- error 1729
error: Verifying a signature, but no certificate was provided:
- error 1730
error: Verifying a signature, but no certificate was provided:
- error 1731
error: Verifying a signature, but no certificate was provided:
- error 1732
error: Verifying a signature, but no certificate was provided:
- error 1733
error: Verifying a signature, but no certificate was provided:
- error 1734
error: Verifying a signature, but no certificate was provided:
- error 1735
error: Verifying a signature, but no certificate was provided:
- error 1736
error: Verifying a signature, but no certificate was provided:
- error 1737
error: Verifying a signature, but no certificate was provided:
- error 1738
error: Verifying a signature, but no certificate was provided:
- error 1739
error: Verifying a signature, but no certificate was provided:
- error 1740
error: Verifying a signature, but no certificate was provided:
- error 1741
error: Verifying a signature, but no certificate was provided:
- error 1742
error: Verifying a signature, but no certificate was provided:
- error 1743
error: Verifying a signature, but no certificate was provided:
- error 1744
error: Verifying a signature, but no certificate was provided:
- error 1745
error: Verifying a signature, but no certificate was provided:
- error 1746
error: Verifying a signature, but no certificate was provided:
- error 1747
error: Verifying a signature, but no certificate was provided:
- error 1748
error: Verifying a signature, but no certificate was provided:
- error 1749
error: Verifying a signature, but no certificate was provided:
- error 1750
error: Verifying a signature, but no certificate was provided:
- error 1751
error: Verifying a signature, but no certificate was provided:
- error 1752
error: Verifying a signature, but no certificate was provided:
- error 1753
error: Verifying a signature, but no certificate was provided:
- error 1754
error: Verifying a signature, but no certificate was provided:
- error 1755
error: Verifying a signature, but no certificate was provided:
- error 1756
error: Verifying a signature, but no certificate was provided:
- error 1757
error: Verifying a signature, but no certificate was provided:
- error 1758
error: Verifying a signature, but no certificate was provided:
- error 1759
error: Verifying a signature, but no certificate was provided:
- error 1760
error: Verifying a signature, but no certificate was provided:
- error 1761
error: Verifying a signature, but no certificate was provided:
- error 1762
error: Verifying a signature, but no certificate was provided:
- error 1763
error: Verifying a signature, but no certificate was provided:
- error 1764
error: Verifying a signature, but no certificate was provided:
- error 1765
error: Verifying a signature, but no certificate was provided:
- error 1766
error: Verifying a signature, but no certificate was provided:
- error 1767
error: Verifying a signature, but no certificate was provided:
- error 1768
error: Verifying a signature, but no certificate was provided:
- error 1769
error: Verifying a signature, but no certificate was provided:
- error 1770
error: Verifying a signature, but no certificate was provided:
- error 1771
error: Verifying a signature, but no certificate was provided:
- error 1772
error: Verifying a signature, but no certificate was provided:
- error 1773
error: Verifying a signature, but no certificate was provided:
- error 1774
error: Verifying a signature, but no certificate was provided:
- error 1775
error: Verifying a signature, but no certificate was provided:
- error 1776
error: Verifying a signature, but no certificate was provided:
- error 1777
error: Verifying a signature, but no certificate was provided:
- error 1778
error: Verifying a signature, but no certificate was provided:
- error 1779
error: Verifying a signature, but no certificate was provided:
- error 1780
error: Verifying a signature, but no certificate was provided:
- error 1781
error: Verifying a signature, but no certificate was provided:
- error 1782
error: Verifying a signature, but no certificate was provided:
- error 1783
error: Verifying a signature, but no certificate was provided:
- error 1784
error: Verifying a signature, but no certificate was provided:
- error 1785
error: Verifying a signature, but no certificate was provided:
- error 1786
error: Verifying a signature, but no certificate was provided:
- error 1787
error: Verifying a signature, but no certificate was provided:
- error 1788
error: Verifying a signature, but no certificate was provided:
- error 1789
error: Verifying a signature, but no certificate was provided:
- error 1790
error: Verifying a signature, but no certificate was provided:
- error 1791
error: Verifying a signature, but no certificate was provided:
- error 1792
error: Verifying a signature, but no certificate was provided:
- error 1793
error: Verifying a signature, but no certificate was provided:
- error 1794
error: Verifying a signature, but no certificate was provided:
- error 1795
error: Verifying a signature, but no certificate was provided:
- error 1796
error: Verifying a signature, but no certificate was provided:
- error 1797
error: Verifying a signature, but no certificate was provided:
- error 1798
error: Verifying a signature, but no certificate was provided:
- error 1799
error: Verifying a signature, but no certificate was provided:
- error 1800
error: Verifying a signature, but no certificate was provided:
- error 1801
error: Verifying a signature, but no certificate was provided:
- error 1802
error: Verifying a signature, but no certificate was provided:
- error 1803
error: Verifying a signature, but no certificate was provided:
- error 1804
error: Verifying a signature, but no certificate was provided:
- error 1805
error: Verifying a signature, but no certificate was provided:
- error 1806
error: Verifying a signature, but no certificate was provided:
- error 1807
error: Verifying a signature, but no certificate was provided:
- error 1808
error: Verifying a signature, but no certificate was provided:
- error 1809
error: Verifying a signature, but no certificate was provided:
- error 1810
error: Verifying a signature, but no certificate was provided:
- error 1811
error: Verifying a signature, but no certificate was provided:
- error 1812
error: Verifying a signature, but no certificate was provided:
- error 1813
error: Verifying a signature, but no certificate was provided:
- error 1814
error: Verifying a signature, but no certificate was provided:
- error 1815
error: Verifying a signature, but no certificate was provided:
- error 1816
error: Verifying a signature, but no certificate was provided:
- error 1817
error: Verifying a signature, but no certificate was provided:
- error 1818
error: Verifying a signature, but no certificate was provided:
- error 1819
error: Verifying a signature, but no certificate was provided:
- error 1820
error: Verifying a signature, but no certificate was provided:
- error 1821
error: Verifying a signature, but no certificate was provided:
- error 1822
error: Verifying a signature, but no certificate was provided:
- error 1823
error: Verifying a signature, but no certificate was provided:
- error 1824
error: Verifying a signature, but no certificate was provided:
- error 1825
error: Verifying a signature, but no certificate was provided:
- error 1826
error: Verifying a signature, but no certificate was provided:
- error 1827
error: Verifying a signature, but no certificate was provided:
- error 1828
error: Verifying a signature, but no certificate was provided:
- error 1829
error: Verifying a signature, but no certificate was provided:
- error 1830
error: Verifying a signature, but no certificate was provided:
- error 1831
error: Verifying a signature, but no certificate was provided:
- error 1832
error: Verifying a signature, but no certificate was provided:
- error 1833
error: Verifying a signature, but no certificate was provided:
- error 1834
error: Verifying a signature, but no certificate was provided:
- error 1835
error: Verifying a signature, but no certificate was provided:
- error 1836
error: Verifying a signature, but no certificate was provided:
- error 1837
error: Verifying a signature, but no certificate was provided:
- error 1838
error: Verifying a signature, but no certificate was provided:
- error 1839
error: Verifying a signature, but no certificate was provided:
- error 1840
error: Verifying a signature, but no certificate was provided:
- error 1841
error: Verifying a signature, but no certificate was provided:
- error 1842
error: Verifying a signature, but no certificate was provided:
- error 1843
error: Verifying a signature, but no certificate was provided:
- error 1844
error: Verifying a signature, but no certificate was provided:
- error 1845
error: Verifying a signature, but no certificate was provided:
- error 1846
error: Verifying a signature, but no certificate was provided:
- error 1847
error: Verifying a signature, but no certificate was provided:
- error 1848
error: Verifying a signature, but no certificate was provided:
- error 1849
error: Verifying a signature, but no certificate was provided:
- error 1850
error: Verifying a signature, but no certificate was provided:
- error 1851
error: Verifying a signature, but no certificate was provided:
- error 1852
error: Verifying a signature, but no certificate was provided:
- error 1853
error: Verifying a signature, but no certificate was provided:
- error 1854
error: Verifying a signature, but no certificate was provided:
- error 1855
error: Verifying a signature, but no certificate was provided:
- error 1856
error: Verifying a signature, but no certificate was provided:
- error 1857
error: Verifying a signature, but no certificate was provided:
- error 1858
error: Verifying a signature, but no certificate was provided:
- error 1859
error: Verifying a signature, but no certificate was provided:
- error 1860
error: Verifying a signature, but no certificate was provided:
- error 1861
error: Verifying a signature, but no certificate was provided:
- error 1862
error: Verifying a signature, but no certificate was provided:
- error 1863
error: Verifying a signature, but no certificate was provided:
- error 1864
error: Verifying a signature, but no certificate was provided:
- error 1865
error: Verifying a signature, but no certificate was provided:
- error 1866
error: Verifying a signature, but no certificate was provided:
- error 1867
error: Verifying a signature, but no certificate was provided:
- error 1868
error: Verifying a signature, but no certificate was provided:
- error 1869
error: Verifying a signature, but no certificate was provided:
- error 1870
error: Verifying a signature, but no certificate was provided:
- error 1871
error: Verifying a signature, but no certificate was provided:
- error 1872
error: Verifying a signature, but no certificate was provided:
- error 1873
error: Verifying a signature, but no certificate was provided:
- error 1874
error: Verifying a signature, but no certificate was provided:
- error 1875
error: Verifying a signature, but no certificate was provided:
- error 1876
error: Verifying a signature, but no certificate was provided:
- error 1877
error: Verifying a signature, but no certificate was provided:
- error 1878
error: Verifying a signature, but no certificate was provided:
- error 1879
error: Verifying a signature, but no certificate was provided:
- error 1880
error: Verifying a signature, but no certificate was provided:
- error 1881
error: Verifying a signature, but no certificate was provided:
- error 1882
error: Verifying a signature, but no certificate was provided:
- error 1883
error: Verifying a signature, but no certificate was provided:
- error 1884
error: Verifying a signature, but no certificate was provided:
- error 1885
error: Verifying a signature, but no certificate was provided:
- error 1886
error: Verifying a signature, but no certificate was provided:
- error 1887
error: Verifying a signature, but no certificate was provided:
- error 1888
error: Verifying a signature, but no certificate was provided:
- error 1889
error: Verifying a signature, but no certificate was provided:
- error 1890
error: Verifying a signature, but no certificate was provided:
- error 1891
error: Verifying a signature, but no certificate was provided:
- error 1892
error: Verifying a signature, but no certificate was provided:
- error 1893
error: Verifying a signature, but no certificate was provided:
- error 1894
error: Verifying a signature, but no certificate was provided:
- error 1895
error: Verifying a signature, but no certificate was provided:
- error 1896
error: Verifying a signature, but no certificate was provided:
- error 1897
error: Verifying a signature, but no certificate was provided:
- error 1898
error: Verifying a signature, but no certificate was provided:
- error 1899
error: Verifying a signature, but no certificate was provided:
- error 1900
error: Verifying a signature, but no certificate was provided:
- error 1901
error: Verifying a signature, but no certificate was provided:
- error 1902
error: Verifying a signature, but no certificate was provided:
- error 1903
error: Verifying a signature, but no certificate was provided:
- error 1904
error: Verifying a signature, but no certificate was provided:
- error 1905
error: Verifying a signature, but no certificate was provided:
- error 1906
error: Verifying a signature, but no certificate was provided:
- error 1907
error: Verifying a signature, but no certificate was provided:
- error 1908
error: Verifying a signature, but no certificate was provided:
- error 1909
error: Verifying a signature, but no certificate was provided:
- error 1910
error: Verifying a signature, but no certificate was provided:
- error 1911
error: Verifying a signature, but no certificate was provided:
- error 1912
error: Verifying a signature, but no certificate was provided:
- error 1913
error: Verifying a signature, but no certificate was provided:
- error 1914
error: Verifying a signature, but no certificate was provided:
- error 1915
error: Verifying a signature, but no certificate was provided:
- error 1916
error: Verifying a signature, but no certificate was provided:
- error 1917
error: Verifying a signature, but no certificate was provided:
- error 1918
error: Verifying a signature, but no certificate was provided:
- error 1919
error: Verifying a signature, but no certificate was provided:
- error 1920
error: Verifying a signature, but no certificate was provided:
- error 1921
error: Verifying a signature, but no certificate was provided:
- error 1922
error: Verifying a signature, but no certificate was provided:
- error 1923
error: Verifying a signature, but no certificate was provided:
- error 1924
error: Verifying a signature, but no certificate was provided:
- error 1925
error: Verifying a signature, but no certificate was provided:
- error 1926
error: Verifying a signature, but no certificate was provided:
- error 1927
error: Verifying a signature, but no certificate was provided:
- error 1928
error: Verifying a signature, but no certificate was provided:
- error 1929
error: Verifying a signature, but no certificate was provided:
- error 1930
error: Verifying a signature, but no certificate was provided:
- error 1931
error: Verifying a signature, but no certificate was provided:
- error 1932
error: Verifying a signature, but no certificate was provided:
- error 1933
error: Verifying a signature, but no certificate was provided:
- error 1934
error: Verifying a signature, but no certificate was provided:
- error 1935
error: Verifying a signature, but no certificate was provided:
- error 1936
error: Verifying a signature, but no certificate was provided:
- error 1937
error: Verifying a signature, but no certificate was provided:
- error 1938
error: Verifying a signature, but no certificate was provided:
- error 1939
error: Verifying a signature, but no certificate was provided:
- error 1940
error: Verifying a signature, but no certificate was provided:
- error 1941
error: Verifying a signature, but no certificate was provided:
- error 1942
error: Verifying a signature, but no certificate was provided:
- error 1943
error: Verifying a signature, but no certificate was provided:
- error 1944
error: Verifying a signature, but no certificate was provided:
- error 1945
error: Verifying a signature, but no certificate was provided:
- error 1946
error: Verifying a signature, but no certificate was provided:
- error 1947
error: Verifying a signature, but no certificate was provided:
- error 1948
error: Verifying a signature, but no certificate was provided:
- error 1949
error: Verifying a signature, but no certificate was provided:
- error 1950
error: Verifying a signature, but no certificate was provided:
- error 1951
error: Verifying a signature, but no certificate was provided:
- error 1952
error: Verifying a signature, but no certificate was provided:
- error 1953
error: Verifying a signature, but no certificate was provided:
- error 1954
error: Verifying a signature, but no certificate was provided:
- error 1955
error: Verifying a signature, but no certificate was provided:
- error 1956
error: Verifying a signature, but no certificate was provided:
- error 1957
error: Verifying a signature, but no certificate was provided:
- error 1958
error: Verifying a signature, but no certificate was provided:
- error 1959
error: Verifying a signature, but no certificate was provided:
- error 1960
error: Verifying a signature, but no certificate was provided:
- error 1961
error: Verifying a signature, but no certificate was provided:
- error 1962
error: Verifying a signature, but no certificate was provided:
- error 1963
error: Verifying a signature, but no certificate was provided:
- error 1964
error: Verifying a signature, but no certificate was provided:
- error 1965
error: Verifying a signature, but no certificate was provided:
- error 1966
error: Verifying a signature, but no certificate was provided:
- error 1967
error: Verifying a signature, but no certificate was provided:
- error 1968
error: Verifying a signature, but no certificate was provided:
- error 1969
error: Verifying a signature, but no certificate was provided:
- error 1970
error: Verifying a signature, but no certificate was provided:
- error 1971
error: Verifying a signature, but no certificate was provided:
- error 1972
error: Verifying a signature, but no certificate was provided:
- error 1973
error: Verifying a signature, but no certificate was provided:
- error 1974
error: Verifying a signature, but no certificate was provided:
- error 1975
error: Verifying a signature, but no certificate was provided:
- error 1976
error: Verifying a signature, but no certificate was provided:
- error 1977
error: Verifying a signature, but no certificate was provided:
- error 1978
error: Verifying a signature, but no certificate was provided:
- error 1979
error: Verifying a signature, but no certificate was provided:
- error 1980
error: Verifying a signature, but no certificate was provided:
- error 1981
error: Verifying a signature, but no certificate was provided:
- error 1982
error: Verifying a signature, but no certificate was provided:
- error 1983
error: Verifying a signature, but no certificate was provided:
- error 1984
error: Verifying a signature, but no certificate was provided:
- error 1985
error: Verifying a signature, but no certificate was provided:
- error 1986
error: Verifying a signature, but no certificate was provided:
- error 1987
error: Verifying a signature, but no certificate was provided:
- error 1988
error: Verifying a signature, but no certificate was provided:
- error 1989
error: Verifying a signature, but no certificate was provided:
- error 1990
error: Verifying a signature, but no certificate was provided:
- error 1991
error: Verifying a signature, but no certificate was provided:
- error 1992
error: Verifying a signature, but no certificate was provided:
- error 1993
error: Verifying a signature, but no certificate was provided:
- error 1994
error: Verifying a signature, but no certificate was provided:
- error 1995
error: Verifying a signature, but no certificate was provided:
- error 1996
error: Verifying a signature, but no certificate was provided:
- error 1997
error: Verifying a signature, but no certificate was provided:
- error 1998
error: Verifying a signature, but no certificate was provided:
- error 1999
error: Verifying a signature, but no certificate was provided:
- error 2000
error: Verifying a signature, but no certificate was provided:
- error 2001
error: Verifying a signature, but no certificate was provided:
- error 2002
error: Verifying a signature, but no certificate was provided:
- error 2003
error: Verifying a signature, but no certificate was provided:
- error 2004
error: Verifying a signature, but no certificate was provided:
- error 2005
error: Verifying a signature, but no certificate was provided:
- error 2006
error: Verifying a signature, but no certificate was provided:
- error 2007
error: Verifying a signature, but no certificate was provided:
- error 2008
error: Verifying a signature, but no certificate was provided:
- error 2009
error: Verifying a signature, but no certificate was provided:
- error 2010
error: Verifying a signature, but no certificate was provided:
- error 2011
error: Verifying a signature, but no certificate was provided:
- error 2012
error: Verifying a signature, but no certificate was provided:
- error 2013
error: Verifying a signature, but no certificate was provided:
- error 2014
error: Verifying a signature, but no certificate was provided:
- error 2015
error: Verifying a signature, but no certificate was provided:
- error 2016
error: Verifying a signature, but no certificate was provided:
- error 2017
error: Verifying a signature, but no certificate was provided:
- error 2018
error: Verifying a signature, but no certificate was provided:
- error 2019
error: Verifying a signature, but no certificate was provided:
- error 2020
error: Verifying a signature, but no certificate was provided:
- error 2021
error: Verifying a signature, but no certificate was provided:
- error 2022
error: Verifying a signature, but no certificate was provided:
- error 2023
error: Verifying a signature, but no certificate was provided:
- error 2024
error: Verifying a signature, but no certificate was provided:
- error 2025
error: Verifying a signature, but no certificate was provided:
- error 2026
error: Verifying a signature, but no certificate was provided:
- error 2027
error: Verifying a signature, but no certificate was provided:
- error 2028
error: Verifying a signature, but no certificate was provided:
- error 2029
error: Verifying a signature, but no certificate was provided:
- error 2030
error: Verifying a signature, but no certificate was provided:
- error 2031
error: Verifying a signature, but no certificate was provided:
- error 2032
error: Verifying a signature, but no certificate was provided:
- error 2033
error: Verifying a signature, but no certificate was provided:
- error 2034
error: Verifying a signature, but no certificate was provided:
- error 2035
error: Verifying a signature, but no certificate was provided:
- error 2036
error: Verifying a signature, but no certificate was provided:
- error 2037
error: Verifying a signature, but no certificate was provided:
- error 2038
error: Verifying a signature, but no certificate was provided:
- error 2039
error: Verifying a signature, but no certificate was provided:
- error 2040
error: Verifying a signature, but no certificate was provided:
- error 2041
error: Verifying a signature, but no certificate was provided:
- error 2042
error: Verifying a signature, but no certificate was provided:
- error 2043
error: Verifying a signature, but no certificate was provided:
- error 2044
error: Verifying a signature, but no certificate was provided:
- error 2045
error: Verifying a signature, but no certificate was provided:
- error 2046
error: Verifying a signature, but no certificate was provided:
- error 2047
error: Verifying a signature, but no certificate was provided:
- error 2048
error: Verifying a signature, but no certificate was provided:
- error 2049
error: Verifying a signature, but no certificate was provided:
- error 2050
error: Verifying a signature, but no certificate was provided:
- error 2051
error: Verifying a signature, but no certificate was provided:
- error 2052
error: Verifying a signature, but no certificate was provided:
- error 2053
error: Verifying a signature, but no certificate was provided:
- error 2054
error: Verifying a signature, but no certificate was provided:
- error 2055
error: Verifying a signature, but no certificate was provided:
- error 2056
error: Verifying a signature, but no certificate was provided:
- error 2057
error: Verifying a signature, but no certificate was provided:
- error 2058
error: Verifying a signature, but no certificate was provided:
- error 2059
error: Verifying a signature, but no certificate was provided:
- error 2060
error: Verifying a signature, but no certificate was provided:
- error 2061
error: Verifying a signature, but no certificate was provided:
- error 2062
error: Verifying a signature, but no certificate was provided:
- error 2063
error: Verifying a signature, but no certificate was provided:
- error 2064
error: Verifying a signature, but no certificate was provided:
- error 2065
error: Verifying a signature, but no certificate was provided:
- error 2066
error: Verifying a signature, but no certificate was provided:
- error 2067
error: Verifying a signature, but no certificate was provided:
- error 2068
error: Verifying a signature, but no certificate was provided:
- error 2069
error: Verifying a signature, but no certificate was provided:
- error 2070
error: Verifying a signature, but no certificate was provided:
- error 2071
error: Verifying a signature, but no certificate was provided:
- error 2072
error: Verifying a signature, but no certificate was provided:
- error 2073
error: Verifying a signature, but no certificate was provided:
- error 2074
error: Verifying a signature, but no certificate was provided:
- error 2075
error: Verifying a signature, but no certificate was provided:
- error 2076
error: Verifying a signature, but no certificate was provided:
- error 2077
error: Verifying a signature, but no certificate was provided:
- error 2078
error: Verifying a signature, but no certificate was provided:
- error 2079
error: Verifying a signature, but no certificate was provided:
- error 2080
error: Verifying a signature, but no certificate was provided:
- error 2081
error: Verifying a signature, but no certificate was provided:
- error 2082
error: Verifying a signature, but no certificate was provided:
- error 2083
error: Verifying a signature, but no certificate was provided:
- error 2084
error: Verifying a signature, but no certificate was provided:
- error 2085
error: Verifying a signature, but no certificate was provided:
- error 2086
error: Verifying a signature, but no certificate was provided:
- error 2087
error: Verifying a signature, but no certificate was provided:
- error 2088
error: Verifying a signature, but no certificate was provided:
- error 2089
error: Verifying a signature, but no certificate was provided:
- error 2090
error: Verifying a signature, but no certificate was provided:
- error 2091
error: Verifying a signature, but no certificate was provided:
- error 2092
error: Verifying a signature, but no certificate was provided:
- error 2093
error: Verifying a signature, but no certificate was provided:
- error 2094
error: Verifying a signature, but no certificate was provided:
- error 2095
error: Verifying a signature, but no certificate was provided:
- error 2096
error: Verifying a signature, but no certificate was provided:
- error 2097
error: Verifying a signature, but no certificate was provided:
- error 2098
error: Verifying a signature, but no certificate was provided:
- error 2099
error: Verifying a signature, but no certificate was provided:
- error 2100
error: Verifying a signature, but no certificate was provided:
- error 2101
error: Verifying a signature, but no certificate was provided:
- error 2102
error: Verifying a signature, but no certificate was provided:
- error 2103
error: Verifying a signature, but no certificate was provided:
- error 2104
error: Verifying a signature, but no certificate was provided:
- error 2105
error: Verifying a signature, but no certificate was provided:
- error 2106
error: Verifying a signature, but no certificate was provided:
- error 2107
error: Verifying a signature, but no certificate was provided:
- error 2108
error: Verifying a signature, but no certificate was provided:
- error 2109
error: Verifying a signature, but no certificate was provided:
- error 2110
error: Verifying a signature, but no certificate was provided:
- error 2111
error: Verifying a signature, but no certificate was provided:
- error 2112
error: Verifying a signature, but no certificate was provided:
- error 2113
error: Verifying a signature, but no certificate was provided:
- error 2114
error: Verifying a signature, but no certificate was provided:
- error 2115
error: Verifying a signature, but no certificate was provided:
- error 2116
error: Verifying a signature, but no certificate was provided:
- error 2117
error: Verifying a signature, but no certificate was provided:
- error 2118
error: Verifying a signature, but no certificate was provided:
- error 2119
error: Verifying a signature, but no certificate was provided:
- error 2120
error: Verifying a signature, but no certificate was provided:
- error 2121
error: Verifying a signature, but no certificate was provided:
- error 2122
error: Verifying a signature, but no certificate was provided:
- error 2123
error: Verifying a signature, but no certificate was provided:
- error 2124
error: Verifying a signature, but no certificate was provided:
- error 2125
error: Verifying a signature, but no certificate was provided:
- error 2126
error: Verifying a signature, but no certificate was provided:
- error 2127
error: Verifying a signature, but no certificate was provided:
- error 2128
error: Verifying a signature, but no certificate was provided:
- error 2129
error: Verifying a signature, but no certificate was provided:
- error 2130
error: Verifying a signature, but no certificate was provided:
- error 2131
error: Verifying a signature, but no certificate was provided:
- error 2132
error: Verifying a signature, but no certificate was provided:
- error 2133
error: Verifying a signature, but no certificate was provided:
- error 2134
error: Verifying a signature, but no certificate was provided:
- error 2135
error: Verifying a signature, but no certificate was provided:
- error 2136
error: Verifying a signature, but no certificate was provided:
- error 2137
error: Verifying a signature, but no certificate was provided:
- error 2138
error: Verifying a signature, but no certificate was provided:
- error 2139
error: Verifying a signature, but no certificate was provided:
- error 2140
error: Verifying a signature, but no certificate was provided:
- error 2141
error: Verifying a signature, but no certificate was provided:
- error 2142
error: Verifying a signature, but no certificate was provided:
- error 2143
error: Verifying a signature, but no certificate was provided:
- error 2144
error: Verifying a signature, but no certificate was provided:
- error 2145
error: Verifying a signature, but no certificate was provided:
- error 2146
error: Verifying a signature, but no certificate was provided:
- error 2147
error: Verifying a signature, but no certificate was provided:
- error 2148
error: Verifying a signature, but no certificate was provided:
- error 2149
error: Verifying a signature, but no certificate was provided:
- error 2150
error: Verifying a signature, but no certificate was provided:
- error 2151
error: Verifying a signature, but no certificate was provided:
- error 2152
error: Verifying a signature, but no certificate was provided:
- error 2153
error: Verifying a signature, but no certificate was provided:
- error 2154
error: Verifying a signature, but no certificate was provided:
- error 2155
error: Verifying a signature, but no certificate was provided:
- error 2156
error: Verifying a signature, but no certificate was provided:
- error 2157
error: Verifying a signature, but no certificate was provided:
- error 2158
error: Verifying a signature, but no certificate was provided:
- error 2159
error: Verifying a signature, but no certificate was provided:
- error 2160
error: Verifying a signature, but no certificate was provided:
- error 2161
error: Verifying a signature, but no certificate was provided:
- error 2162
error: Verifying a signature, but no certificate was provided:
- error 2163
error: Verifying a signature, but no certificate was provided:
- error 2164
error: Verifying a signature, but no certificate was provided:
- error 2165
error: Verifying a signature, but no certificate was provided:
- error 2166
error: Verifying a signature, but no certificate was provided:
- error 2167
error: Verifying a signature, but no certificate was provided:
- error 2168
error: Verifying a signature, but no certificate was provided:
- error 2169
error: Verifying a signature, but no certificate was provided:
- error 2170
error: Verifying a signature, but no certificate was provided:
- error 2171
error: Verifying a signature, but no certificate was provided:
- error 2172
error: Verifying a signature, but no certificate was provided:
- error 2173
error: Verifying a signature, but no certificate was provided:
- error 2174
error: Verifying a signature, but no certificate was provided:
- error 2175
error: Verifying a signature, but no certificate was provided:
- error 2176
error: Verifying a signature, but no certificate was provided:
- error 2177
error: Verifying a signature, but no certificate was provided:
- error 2178
error: Verifying a signature, but no certificate was provided:
- error 2179
error: Verifying a signature, but no certificate was provided:
- error 2180
error: Verifying a signature, but no certificate was provided:
- error 2181
error: Verifying a signature, but no certificate was provided:
- error 2182
error: Verifying a signature, but no certificate was provided:
- error 2183
error: Verifying a signature, but no certificate was provided:
- error 2184
error: Verifying a signature, but no certificate was provided:
- error 2185
error: Verifying a signature, but no certificate was provided:
- error 2186
error: Verifying a signature, but no certificate was provided:
- error 2187
error: Verifying a signature, but no certificate was provided:
- error 2188
error: Verifying a signature, but no certificate was provided:
- error 2189
error: Verifying a signature, but no certificate was provided:
- error 2190
error: Verifying a signature, but no certificate was provided:
- error 2191
error: Verifying a signature, but no certificate was provided:
- error 2192
error: Verifying a signature, but no certificate was provided:
- error 2193
error: Verifying a signature, but no certificate was provided:
- error 2194
error: Verifying a signature, but no certificate was provided:
- error 2195
error: Verifying a signature, but no certificate was provided:
- error 2196
error: Verifying a signature, but no certificate was provided:
- error 2197
error: Verifying a signature, but no certificate was provided:
- error 2198
error: Verifying a signature, but no certificate was provided:
- error 2199
error: Verifying a signature, but no certificate was provided:
- error 2200
error: Verifying a signature, but no certificate was provided:
- error 2201
error: Verifying a signature, but no certificate was provided:
- error 2202
error: Verifying a signature, but no certificate was provided:
- error 2203
error: Verifying a signature, but no certificate was provided:
- error 2204
error: Verifying a signature, but no certificate was provided:
- error 2205
error: Verifying a signature, but no certificate was provided:
- error 2206
error: Verifying a signature, but no certificate was provided:
- error 2207
error: Verifying a signature, but no certificate was provided:
- error 2208
error: Verifying a signature, but no certificate was provided:
- error 2209
error: Verifying a signature, but no certificate was provided:
- error 2210
error: Verifying a signature, but no certificate was provided:
- error 2211
error: Verifying a signature, but no certificate was provided:
- error 2212
error: Verifying a signature, but no certificate was provided:
- error 2213
error: Verifying a signature, but no certificate was provided:
- error 2214
error: Verifying a signature, but no certificate was provided:
- error 2215
error: Verifying a signature, but no certificate was provided:
- error 2216
error: Verifying a signature, but no certificate was provided:
- error 2217
error: Verifying a signature, but no certificate was provided:
- error 2218
error: Verifying a signature, but no certificate was provided:
- error 2219
error: Verifying a signature, but no certificate was provided:
- error 2220
error: Verifying a signature, but no certificate was provided:
- error 2221
error: Verifying a signature, but no certificate was provided:
- error 2222
error: Verifying a signature, but no certificate was provided:
- error 2223
error: Verifying a signature, but no certificate was provided:
- error 2224
error: Verifying a signature, but no certificate was provided:
- error 2225
error: Verifying a signature, but no certificate was provided:
- error 2226
error: Verifying a signature, but no certificate was provided:
- error 2227
error: Verifying a signature, but no certificate was provided:
- error 2228
error: Verifying a signature, but no certificate was provided:
- error 2229
error: Verifying a signature, but no certificate was provided:
- error 2230
error: Verifying a signature, but no certificate was provided:
- error 2231
error: Verifying a signature, but no certificate was provided:
- error 2232
error: Verifying a signature, but no certificate was provided:
- error 2233
error: Verifying a signature, but no certificate was provided:
- error 2234
error: Verifying a signature, but no certificate was provided:
- error 2235
error: Verifying a signature, but no certificate was provided:
- error 2236
error: Verifying a signature, but no certificate was provided:
- error 2237
error: Verifying a signature, but no certificate was provided:
- error 2238
error: Verifying a signature, but no certificate was provided:
- error 2239
error: Verifying a signature, but no certificate was provided:
- error 2240
error: Verifying a signature, but no certificate was provided:
- error 2241
error: Verifying a signature, but no certificate was provided:
- error 2242
error: Verifying a signature, but no certificate was provided:
- error 2243
error: Verifying a signature, but no certificate was provided:
- error 2244
error: Verifying a signature, but no certificate was provided:
- error 2245
error: Verifying a signature, but no certificate was provided:
- error 2246
error: Verifying a signature, but no certificate was provided:
- error 2247
error: Verifying a signature, but no certificate was provided:
- error 2248
error: Verifying a signature, but no certificate was provided:
- error 2249
error: Verifying a signature, but no certificate was provided:
- error 2250
error: Verifying a signature, but no certificate was provided:
- error 2251
error: Verifying a signature, but no certificate was provided:
- error 2252
error: Verifying a signature, but no certificate was provided:
- error 2253
error: Verifying a signature, but no certificate was provided:
- error 2254
error: Verifying a signature, but no certificate was provided:
- error 2255
error: Verifying a signature, but no certificate was provided:
- error 2256
error: Verifying a signature, but no certificate was provided:
- error 2257
error: Verifying a signature, but no certificate was provided:
- error 2258
error: Verifying a signature, but no certificate was provided:
- error 2259
error: Verifying a signature, but no certificate was provided:
- error 2260
error: Verifying a signature, but no certificate was provided:
- error 2261
error: Verifying a signature, but no certificate was provided:
- error 2262
error: Verifying a signature, but no certificate was provided:
- error 2263
error: Verifying a signature, but no certificate was provided:
- error 2264
error: Verifying a signature, but no certificate was provided:
- error 2265
error: Verifying a signature, but no certificate was provided:
- error 2266
error: Verifying a signature, but no certificate was provided:
- error 2267
error: Verifying a signature, but no certificate was provided:
- error 2268
error: Verifying a signature, but no certificate was provided:
- error 2269
error: Verifying a signature, but no certificate was provided:
- error 2270
error: Verifying a signature, but no certificate was provided:
- error 2271
error: Verifying a signature, but no certificate was provided:
- error 2272
error: Verifying a signature, but no certificate was provided:
- error 2273
error: Verifying a signature, but no certificate was provided:
- error 2274
error: Verifying a signature, but no certificate was provided:
- error 2275
error: Verifying a signature, but no certificate was provided:
- error 2276
error: Verifying a signature, but no certificate was provided:
- error 2277
error: Verifying a signature, but no certificate was provided:
- error 2278
error: Verifying a signature, but no certificate was provided:
- error 2279
error: Verifying a signature, but no certificate was provided:
- error 2280
error: Verifying a signature, but no certificate was provided:
- error 2281
error: Verifying a signature, but no certificate was provided:
- error 2282
error: Verifying a signature, but no certificate was provided:
- error 2283
error: Verifying a signature, but no certificate was provided:
- error 2284
error: Verifying a signature, but no certificate was provided:
- error 2285
error: Verifying a signature, but no certificate was provided:
- error 2286
error: Verifying a signature, but no certificate was provided:
- error 2287
error: Verifying a signature, but no certificate was provided:
- error 2288
error: Verifying a signature, but no certificate was provided:
- error 2289
error: Verifying a signature, but no certificate was provided:
- error 2290
error: Verifying a signature, but no certificate was provided:
- error 2291
error: Verifying a signature, but no certificate was provided:
- error 2292
error: Verifying a signature, but no certificate was provided:
- error 2293
error: Verifying a signature, but no certificate was provided:
- error 2294
error: Verifying a signature, but no certificate was provided:
- error 2295
error: Verifying a signature, but no certificate was provided:
- error 2296
error: Verifying a signature, but no certificate was provided:
- error 2297
error: Verifying a signature, but no certificate was provided:
- error 2298
error: Verifying a signature, but no certificate was provided:
- error 2299
error: Verifying a signature, but no certificate was provided:
- error 2300
error: Verifying a signature, but no certificate was provided:
- error 2301
error: Verifying a signature, but no certificate was provided:
- error 2302
error: Verifying a signature, but no certificate was provided:
- error 2303
error: Verifying a signature, but no certificate was provided:
- error 2304
error: Verifying a signature, but no certificate was provided:
- error 2305
error: Verifying a signature, but no certificate was provided:
- error 2306
error: Verifying a signature, but no certificate was provided:
- error 2307
error: Verifying a signature, but no certificate was provided:
- error 2308
error: Verifying a signature, but no certificate was provided:
- error 2309
error: Verifying a signature, but no certificate was provided:
- error 2310
error: Verifying a signature, but no certificate was provided:
- error 2311
error: Verifying a signature, but no certificate was provided:
- error 2312
error: Verifying a signature, but no certificate was provided:
- error 2313
error: Verifying a signature, but no certificate was provided:
- error 2314
error: Verifying a signature, but no certificate was provided:
- error 2315
error: Verifying a signature, but no certificate was provided:
- error 2316
error: Verifying a signature, but no certificate was provided:
- error 2317
error: Verifying a signature, but no certificate was provided:
- error 2318
error: Verifying a signature, but no certificate was provided:
- error 2319
error: Verifying a signature, but no certificate was provided:
- error 2320
error: Verifying a signature, but no certificate was provided:
- error 2321
error: Verifying a signature, but no certificate was provided:
- error 2322
error: Verifying a signature, but no certificate was provided:
- error 2323
error: Verifying a signature, but no certificate was provided:
- error 2324
error: Verifying a signature, but no certificate was provided:
- error 2325
error: Verifying a signature, but no certificate was provided:
- error 2326
error: Verifying a signature, but no certificate was provided:
- error 2327
error: Verifying a signature, but no certificate was provided:
- error 2328
error: Verifying a signature, but no certificate was provided:
- error 2329
error: Verifying a signature, but no certificate was provided:
- error 2330
error: Verifying a signature, but no certificate was provided:
- error 2331
error: Verifying a signature, but no certificate was provided:
- error 2332
error: Verifying a signature, but no certificate was provided:
- error 2333
error: Verifying a signature, but no certificate was provided:
- error 2334
error: Verifying a signature, but no certificate was provided:
- error 2335
error: Verifying a signature, but no certificate was provided:
- error 2336
error: Verifying a signature, but no certificate was provided:
- error 2337
error: Verifying a signature, but no certificate was provided:
- error 2338
error: Verifying a signature, but no certificate was provided:
- error 2339
error: Verifying a signature, but no certificate was provided:
- error 2340
error: Verifying a signature, but no certificate was provided:
- error 2341
error: Verifying a signature, but no certificate was provided:
- error 2342
error: Verifying a signature, but no certificate was provided:
- error 2343
error: Verifying a signature, but no certificate was provided:
- error 2344
error: Verifying a signature, but no certificate was provided:
- error 2345
error: Verifying a signature, but no certificate was provided:
- error 2346
error: Verifying a signature, but no certificate was provided:
- error 2347
error: Verifying a signature, but no certificate was provided:
- error 2348
error: Verifying a signature, but no certificate was provided:
- error 2349
error: Verifying a signature, but no certificate was provided:
- error 2350
error: Verifying a signature, but no certificate was provided:
- error 2351
error: Verifying a signature, but no certificate was provided:
- error 2352
error: Verifying a signature, but no certificate was provided:
- error 2353
error: Verifying a signature, but no certificate was provided:
- error 2354
error: Verifying a signature, but no certificate was provided:
- error 2355
error: Verifying a signature, but no certificate was provided:
- error 2356
error: Verifying a signature, but no certificate was provided:
- error 2357
error: Verifying a signature, but no certificate was provided:
- error 2358
error: Verifying a signature, but no certificate was provided:
- error 2359
error: Verifying a signature, but no certificate was provided:
- error 2360
error: Verifying a signature, but no certificate was provided:
- error 2361
error: Verifying a signature, but no certificate was provided:
- error 2362
error: Verifying a signature, but no certificate was provided:
- error 2363
error: Verifying a signature, but no certificate was provided:
- error 2364
error: Verifying a signature, but no certificate was provided:
- error 2365
error: Verifying a signature, but no certificate was provided:
- error 2366
error: Verifying a signature, but no certificate was provided:
- error 2367
error: Verifying a signature, but no certificate was provided:
- error 2368
error: Verifying a signature, but no certificate was provided:
- error 2369
error: Verifying a signature, but no certificate was provided:
- error 2370
error: Verifying a signature, but no certificate was provided:
- error 2371
error: Verifying a signature, but no certificate was provided:
- error 2372
error: Verifying a signature, but no certificate was provided:
- error 2373
error: Verifying a signature, but no certificate was provided:
- error 2374
error: Verifying a signature, but no certificate was provided:
- error 2375
error: Verifying a signature, but no certificate was provided:
- error 2376
error: Verifying a signature, but no certificate was provided:
- error 2377
error: Verifying a signature, but no certificate was provided:
- error 2378
error: Verifying a signature, but no certificate was provided:
- error 2379
error: Verifying a signature, but no certificate was provided:
- error 2380
error: Verifying a signature, but no certificate was provided:
- error 2381
error: Verifying a signature, but no certificate was provided:
- error 2382
error: Verifying a signature, but no certificate was provided:
- error 2383
error: Verifying a signature, but no certificate was provided:
- error 2384
error: Verifying a signature, but no certificate was provided:
- error 2385
error: Verifying a signature, but no certificate was provided:
- error 2386
error: Verifying a signature, but no certificate was provided:
- error 2387
error: Verifying a signature, but no certificate was provided:
- error 2388
error: Verifying a signature, but no certificate was provided:
- error 2389
error: Verifying a signature, but no certificate was provided:
- error 2390
error: Verifying a signature, but no certificate was provided:
- error 2391
error: Verifying a signature, but no certificate was provided:
- error 2392
error: Verifying a signature, but no certificate was provided:
- error 2393
error: Verifying a signature, but no certificate was provided:
- error 2394
error: Verifying a signature, but no certificate was provided:
- error 2395
error: Verifying a signature, but no certificate was provided:
- error 2396
error: Verifying a signature, but no certificate was provided:
- error 2397
error: Verifying a signature, but no certificate was provided:
- error 2398
error: Verifying a signature, but no certificate was provided:
- error 2399
error: Verifying a signature, but no certificate was provided:
- error 2400
error: Verifying a signature, but no certificate was provided:
- error 2401
error: Verifying a signature, but no certificate was provided:
- error 2402
error: Verifying a signature, but no certificate was provided:
- error 2403
error: Verifying a signature, but no certificate was provided:
- error 2404
error: Verifying a signature, but no certificate was provided:
- error 2405
error: Verifying a signature, but no certificate was provided:
- error 2406
error: Verifying a signature, but no certificate was provided:
- error 2407
error: Verifying a signature, but no certificate was provided:
- error 2408
error: Verifying a signature, but no certificate was provided:
- error 2409
error: Verifying a signature, but no certificate was provided:
- error 2410
error: Verifying a signature, but no certificate was provided:
- error 2411
error: Verifying a signature, but no certificate was provided:
- error 2412
error: Verifying a signature, but no certificate was provided:
- error 2413
error: Verifying a signature, but no certificate was provided:
- error 2414
error: Verifying a signature, but no certificate was provided:
- error 2415
error: Verifying a signature, but no certificate was provided:
- error 2416
error: Verifying a signature, but no certificate was provided:
- error 2417
error: Verifying a signature, but no certificate was provided:
- error 2418
error: Verifying a signature, but no certificate was provided:
- error 2419
error: Verifying a signature, but no certificate was provided:
- error 2420
error: Verifying a signature, but no certificate was provided:
- error 2421
error: Verifying a signature, but no certificate was provided:
- error 2422
error: Verifying a signature, but no certificate was provided:
- error 2423
error: Verifying a signature, but no certificate was provided:
- error 2424
error: Verifying a signature, but no certificate was provided:
- error 2425
error: Verifying a signature, but no certificate was provided:
- error 2426
error: Verifying a signature, but no certificate was provided:
- error 2427
error: Verifying a signature, but no certificate was provided:
- error 2428
error: Verifying a signature, but no certificate was provided:
- error 2429
error: Verifying a signature, but no certificate was provided:
- error 2430
error: Verifying a signature, but no certificate was provided:
- error 2431
error: Verifying a signature, but no certificate was provided:
- error 2432
error: Verifying a signature, but no certificate was provided:
- error 2433
error: Verifying a signature, but no certificate was provided:
- error 2434
error: Verifying a signature, but no certificate was provided:
- error 2435
error: Verifying a signature, but no certificate was provided:
- error 2436
error: Verifying a signature, but no certificate was provided:
- error 2437
error: Verifying a signature, but no certificate was provided:
- error 2438
error: Verifying a signature, but no certificate was provided:
- error 2439
error: Verifying a signature, but no certificate was provided:
- error 2440
error: Verifying a signature, but no certificate was provided:
- error 2441
error: Verifying a signature, but no certificate was provided:
- error 2442
error: Verifying a signature, but no certificate was provided:
- error 2443
error: Verifying a signature, but no certificate was provided:
- error 2444
error: Verifying a signature, but no certificate was provided:
- error 2445
error: Verifying a signature, but no certificate was provided:
- error 2446
error: Verifying a signature, but no certificate was provided:
- error 2447
error: Verifying a signature, but no certificate was provided:
- error 2448
error: Verifying a signature, but no certificate was provided:
- error 2449
error: Verifying a signature, but no certificate was provided:
- error 2450
error: Verifying a signature, but no certificate was provided:
- error 2451
error: Verifying a signature, but no certificate was provided:
- error 2452
error: Verifying a signature, but no certificate was provided:
- error 2453
error: Verifying a signature, but no certificate was provided:
- error 2454
error: Verifying a signature, but no certificate was provided:
- error 2455
error: Verifying a signature, but no certificate was provided:
- error 2456
error: Verifying a signature, but no certificate was provided:
- error 2457
error: Verifying a signature, but no certificate was provided:
- error 2458
error: Verifying a signature, but no certificate was provided:
- error 2459
error: Verifying a signature, but no certificate was provided:
- error 2460
error: Verifying a signature, but no certificate was provided:
- error 2461
error: Verifying a signature, but no certificate was provided:
- error 2462
error: Verifying a signature, but no certificate was provided:
- error 2463
error: Verifying a signature, but no certificate was provided:
- error 2464
error: Verifying a signature, but no certificate was provided:
- error 2465
error: Verifying a signature, but no certificate was provided:
- error 2466
error: Verifying a signature, but no certificate was provided:
- error 2467
error: Verifying a signature, but no certificate was provided:
- error 2468
error: Verifying a signature, but no certificate was provided:
- error 2469
error: Verifying a signature, but no certificate was provided:
- error 2470
error: Verifying a signature, but no certificate was provided:
- error 2471
error: Verifying a signature, but no certificate was provided:
- error 2472
error: Verifying a signature, but no certificate was provided:
- error 2473
error: Verifying a signature, but no certificate was provided:
- error 2474
error: Verifying a signature, but no certificate was provided:
- error 2475
error: Verifying a signature, but no certificate was provided:
- error 2476
error: Verifying a signature, but no certificate was provided:
- error 2477
error: Verifying a signature, but no certificate was provided:
- error 2478
error: Verifying a signature, but no certificate was provided:
- error 2479
error: Verifying a signature, but no certificate was provided:
- error 2480
error: Verifying a signature, but no certificate was provided:
- error 2481
error: Verifying a signature, but no certificate was provided:
- error 2482
error: Verifying a signature, but no certificate was provided:
- error 2483
error: Verifying a signature, but no certificate was provided:
- error 2484
error: Verifying a signature, but no certificate was provided:
- error 2485
error: Verifying a signature, but no certificate was provided:
- error 2486
error: Verifying a signature, but no certificate was provided:
- error 2487
error: Verifying a signature, but no certificate was provided:
- error 2488
error: Verifying a signature, but no certificate was provided:
- error 2489
error: Verifying a signature, but no certificate was provided:
- error 2490
error: Verifying a signature, but no certificate was provided:
- error 2491
error: Verifying a signature, but no certificate was provided:
- error 2492
error: Verifying a signature, but no certificate was provided:
- error 2493
error: Verifying a signature, but no certificate was provided:
- error 2494
error: Verifying a signature, but no certificate was provided:
- error 2495
error: Verifying a signature, but no certificate was provided:
- error 2496
error: Verifying a signature, but no certificate was provided:
- error 2497
error: Verifying a signature, but no certificate was provided:
- error 2498
error: Verifying a signature, but no certificate was provided:
- error 2499
error: Verifying a signature, but no certificate was provided:
- error 2500
error: Verifying a signature, but no certificate was provided:
- error 2501
error: Verifying a signature, but no certificate was provided:
- error 2502
error: Verifying a signature, but no certificate was provided:
- error 2503
error: Verifying a signature, but no certificate was provided:
- error 2504
error: Verifying a signature, but no certificate was provided:
- error 2505
error: Verifying a signature, but no certificate was provided:
- error 2506
error: Verifying a signature, but no certificate was provided:
- error 2507
error: Verifying a signature, but no certificate was provided:
- error 2508
error: Verifying a signature, but no certificate was provided:
- error 2509
error: Verifying a signature, but no certificate was provided:
- error 2510
error: Verifying a signature, but no certificate was provided:
- error 2511
error: Verifying a signature, but no certificate was provided:
- error 2512
error: Verifying a signature, but no certificate was provided:
- error 2513
error: Verifying a signature, but no certificate was provided:
- error 2514
error: Verifying a signature, but no certificate was provided:
- error 2515
error: Verifying a signature, but no certificate was provided:
- error 2516
error: Verifying a signature, but no certificate was provided:
- error 2517
error: Verifying a signature, but no certificate was provided:
- error 2518
error: Verifying a signature, but no certificate was provided:
- error 2519
error: Verifying a signature, but no certificate was provided:
- error 2520
error: Verifying a signature, but no certificate was provided:
- error 2521
error: Verifying a signature, but no certificate was provided:
- error 2522
error: Verifying a signature, but no certificate was provided:
- error 2523
error: Verifying a signature, but no certificate was provided:
- error 2524
error: Verifying a signature, but no certificate was provided:
- error 2525
error: Verifying a signature, but no certificate was provided:
- error 2526
error: Verifying a signature, but no certificate was provided:
- error 2527
error: Verifying a signature, but no certificate was provided:
- error 2528
error: Verifying a signature, but no certificate was provided:
- error 2529
error: Verifying a signature, but no certificate was provided:
- error 2530
error: Verifying a signature, but no certificate was provided:
- error 2531
error: Verifying a signature, but no certificate was provided:
- error 2532
error: Verifying a signature, but no certificate was provided:
- error 2533
error: Verifying a signature, but no certificate was provided:
- error 2534
error: Verifying a signature, but no certificate was provided:
- error 2535
error: Verifying a signature, but no certificate was provided:
- error 2536
error: Verifying a signature, but no certificate was provided:
- error 2537
error: Verifying a signature, but no certificate was provided:
- error 2538
error: Verifying a signature, but no certificate was provided:
- error 2539
error: Verifying a signature, but no certificate was provided:
- error 2540
error: Verifying a signature, but no certificate was provided:
- error 2541
error: Verifying a signature, but no certificate was provided:
- error 2542
error: Verifying a signature, but no certificate was provided:
- error 2543
error: Verifying a signature, but no certificate was provided:
- error 2544
error: Verifying a signature, but no certificate was provided:
- error 2545
error: Verifying a signature, but no certificate was provided:
- error 2546
error: Verifying a signature, but no certificate was provided:
- error 2547
error: Verifying a signature, but no certificate was provided:
- error 2548
error: Verifying a signature, but no certificate was provided:
- error 2549
error: Verifying a signature, but no certificate was provided:
- error 2550
error: Verifying a signature, but no certificate was provided:
- error 2551
error: Verifying a signature, but no certificate was provided:
- error 2552
error: Verifying a signature, but no certificate was provided:
- error 2553
error: Verifying a signature, but no certificate was provided:
- error 2554
error: Verifying a signature, but no certificate was provided:
- error 2555
error: Verifying a signature, but no certificate was provided:
- error 2556
error: Verifying a signature, but no certificate was provided:
- error 2557
error: Verifying a signature, but no certificate was provided:
- error 2558
error: Verifying a signature, but no certificate was provided:
- error 2559
error: Verifying a signature, but no certificate was provided:
- error 2560
error: Verifying a signature, but no certificate was provided:
- error 2561
error: Verifying a signature, but no certificate was provided:
- error 2562
error: Verifying a signature, but no certificate was provided:
- error 2563
error: Verifying a signature, but no certificate was provided:
- error 2564
error: Verifying a signature, but no certificate was provided:
- error 2565
error: Verifying a signature, but no certificate was provided:
- error 2566
error: Verifying a signature, but no certificate was provided:
- error 2567
error: Verifying a signature, but no certificate was provided:
- error 2568
error: Verifying a signature, but no certificate was provided:
- error 2569
error: Verifying a signature, but no certificate was provided:
- error 2570
error: Verifying a signature, but no certificate was provided:
- error 2571
error: Verifying a signature, but no certificate was provided:
- error 2572
error: Verifying a signature, but no certificate was provided:
- error 2573
error: Verifying a signature, but no certificate was provided:
- error 2574
error: Verifying a signature, but no certificate was provided:
- error 2575
error: Verifying a signature, but no certificate was provided:
- error 2576
error: Verifying a signature, but no certificate was provided:
- error 2577
error: Verifying a signature, but no certificate was provided:
- error 2578
error: Verifying a signature, but no certificate was provided:
- error 2579
error: Verifying a signature, but no certificate was provided:
- error 2580
error: Verifying a signature, but no certificate was provided:
- error 2581
error: Verifying a signature, but no certificate was provided:
- error 2582
error: Verifying a signature, but no certificate was provided:
- error 2583
error: Verifying a signature, but no certificate was provided:
- error 2584
error: Verifying a signature, but no certificate was provided:
- error 2585
error: Verifying a signature, but no certificate was provided:
- error 2586
error: Verifying a signature, but no certificate was provided:
- error 2587
error: Verifying a signature, but no certificate was provided:
- error 2588
error: Verifying a signature, but no certificate was provided:
- error 2589
error: Verifying a signature, but no certificate was provided:
- error 2590
error: Verifying a signature, but no certificate was provided:
- error 2591
error: Verifying a signature, but no certificate was provided:
- error 2592
error: Verifying a signature, but no certificate was provided:
- error 2593
error: Verifying a signature, but no certificate was provided:
- error 2594
error: Verifying a signature, but no certificate was provided:
- error 2595
error: Verifying a signature, but no certificate was provided:
- error 2596
error: Verifying a signature, but no certificate was provided:
- error 2597
error: Verifying a signature, but no certificate was provided:
- error 2598
error: Verifying a signature, but no certificate was provided:
- error 2599
error: Verifying a signature, but no certificate was provided:
- error 2600
error: Verifying a signature, but no certificate was provided:
- error 2601
error: Verifying a signature, but no certificate was provided:
- error 2602
error: Verifying a signature, but no certificate was provided:
- error 2603
error: Verifying a signature, but no certificate was provided:
- error 2604
error: Verifying a signature, but no certificate was provided:
- error 2605
error: Verifying a signature, but no certificate was provided:
- error 2606
error: Verifying a signature, but no certificate was provided:
Content: Signature f6b5 created at Sun Sep 13 18:33: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
rpm-whiteout-1.41-4.noarch
error: Verifying a signature, but no certificate was provided:
Signature 7e0c created at Sat Mar 28 17:41:18 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 1238 created at Wed Dec 23 00:48: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 799d created at Sat Mar 28 17:41: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 a329 created at Mon Mar 28 02:14:45 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 59ed created at Mon Nov 9 21:07:53 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 66a2 created at Fri Feb 26 07:39:31 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 b617 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 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 c491 created at Tue Jun 12 18:34:14 2018 invalid: signature is not alive
because: Expired on 2018-07-12T18:34:14Z
error: rpmdbNextIterator: skipping h# 14
Header V4 DSA/SHA1 Signature, key ID d16b468a: BAD
Header SHA1 digest: OK
error: Verifying a signature, but no certificate was provided:
Signature fea4 created at Sat Mar 28 20:43: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 da75 created at Sat Mar 28 17:37: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 5c7a created at Sat Mar 28 17:41: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 2ec4 created at Wed Mar 29 06:20:29 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 d8ec created at Sat Mar 28 18:59: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: Verifying a signature, but no certificate was provided:
Signature fe18 created at Sat Mar 28 19:38: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 0059 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 72e0 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 38d6 created at Sun Apr 17 12:22: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 11d1 created at Sun Apr 17 12:22: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 b48d created at Mon Mar 28 02:12:45 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 d780 created at Sat Jan 2 18:30:01 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 1da6 created at Sat Jan 28 08:12:13 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 c9c3 created at Wed Dec 23 00:48: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 d320 created at Sat Mar 28 17:41:18 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 5a9e created at Sat Mar 28 17:41: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 7f4b created at Sat Mar 28 20:44:11 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 d1cb created at Sun Apr 17 12:38:58 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 ab65 created at Sat Mar 28 17:46:45 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 b814 created at Tue Aug 8 21:29:46 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 c0c9 created at Mon Jun 1 06:46: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 2fb1 created at Wed Dec 27 09:32:13 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 5666 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 77c7 created at Wed Dec 27 09:28: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 d9f6 created at Wed Dec 27 09:34:37 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 84ac created at Wed Dec 23 00:39: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 a12b created at Sat Mar 28 19:59: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 943c created at Sat Mar 28 17:44: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 f295 created at Wed Dec 27 09:03:46 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 2586 created at Sat Mar 28 20:44:11 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 1dc3 created at Sun Apr 17 12:38:58 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 0c65 created at Sat Mar 28 19:41:20 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 ee75 created at Sat Mar 28 19:41: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 984c created at Sat Mar 28 17:46:45 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 afed created at Tue Aug 8 21:29:46 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 e182 created at Mon Jun 1 06:46: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 d652 created at Wed Dec 27 09:32:13 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 dfad created at Wed Dec 27 09:28: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 5931 created at Wed Dec 27 09:34:36 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 1966 created at Wed Dec 27 09:05: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 e59e created at Sat Mar 28 19:41:20 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 62c5 created at Sat Mar 28 19:41: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 2594 created at Sat Mar 28 20:43: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 592c created at Wed Dec 27 09:04: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 e05f created at Fri Feb 26 07:39:31 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 3982 created at Wed Dec 23 00:39:24 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 0e47 created at Wed Dec 23 00:39:24 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 87cb created at Thu Jul 9 20:46:10 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 f3d1 created at Thu Jul 9 20:46:10 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 56e3 created at Wed Dec 23 00:54: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 67fa created at Wed Dec 23 00:54: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 9087 created at Sat Mar 28 17:37: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 56f5 created at Thu Apr 20 21:12:59 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 b5de created at Thu Apr 20 21:12:59 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 5060 created at Sat Mar 28 18:00: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 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: Verifying a signature, but no certificate was provided:
Signature 38b8 created at Tue Aug 23 05:40:45 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 926e created at Sat Mar 28 17:54: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 9dc3 created at Thu Jun 22 00:54: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 fba6 created at Sat Mar 28 19:00:59 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 2b9e created at Sat Mar 28 19:26:11 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 f100 created at Sat Mar 28 17:59:11 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 3914 created at Sat Mar 28 17:38:45 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 7e38 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 26f8 created at Sat Mar 28 19:26:11 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 347f 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: Verifying a signature, but no certificate was provided:
Signature 3dce created at Sun Mar 5 11:06:46 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 44c1 created at Sun Mar 5 11:06:46 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 da99 created at Sat Mar 28 17:41: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 143f created at Sun Jul 2 15:32:07 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 172f created at Sun Jul 2 15:32:07 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 988b created at Sat Mar 28 17:53:47 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 7a83 created at Sat Mar 28 17:53:47 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 913c created at Tue Aug 8 21:23:50 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 5c6c created at Sat Mar 28 18:34:33 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 207e created at Sat Mar 28 18:34: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 2f2f created at Sat Mar 28 19:41:22 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 8710 created at Sat Mar 28 19:41:22 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 bea5 created at Mon Nov 9 21:13: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 a0f4 created at Mon Nov 9 21:13: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 6678 created at Sat Mar 28 18:36: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 831a created at Sat Mar 28 17:59:11 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 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 f75a created at Sun Mar 5 11:18:18 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 a3c3 created at Sat Mar 28 18:00: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 34f7 created at Sat Mar 28 18:00: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 e1d7 created at Thu May 24 11:59:34 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 9363 created at Thu May 24 12:30:28 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 9d4f created at Fri Mar 9 23:24:37 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 652e created at Fri Mar 9 23:24:37 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 6cc5 created at Sat Mar 28 17:55: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 486c created at Sat Mar 28 20:23:07 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 ba77 created at Wed Dec 23 01: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 10d4 created at Sat Mar 28 20:23:07 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 3b6c created at Wed Dec 23 01: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 305d 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 abf4 created at Wed Dec 23 00:58:09 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 74a9 created at Wed Dec 23 00:58:09 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 63ac created at Sat Mar 28 19:46: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 4d38 created at Sat Mar 28 19:46: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 2273 created at Sat Mar 28 18:00:45 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 a235 created at Thu Jul 9 20:52: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 0fce created at Thu Jul 9 20:52: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 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: Verifying a signature, but no certificate was provided:
Signature 32fc created at Sat Mar 28 20:44: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 96f2 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 ccdd 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 99b4 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 d790 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 f5f2 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 f7c1 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 2f6d 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 b2f4 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 7aa3 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 1c99 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 a7c2 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 15d1 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 2083 created at Mon Nov 9 21:03: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 4338 created at Sat Mar 28 17:43: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 4161 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 3034 created at Sat Mar 28 20:44:18 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 f2bd created at Sat Mar 28 17:56: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 3a41 created at Sat Mar 28 17:50: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 3ef6 created at Sat Oct 15 20:40:57 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 639d created at Sat May 27 06:32: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 fd05 created at Sat Mar 28 19:10:59 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 ab52 created at Sat Mar 28 20:41:18 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 4c22 created at Mon Mar 26 09:44:50 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 bfae created at Sat May 27 06:36:55 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 fba2 created at Sat Mar 28 19:49:16 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 c779 created at Sat Mar 28 17:54:24 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 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: Verifying a signature, but no certificate was provided:
Signature e91a created at Wed Dec 23 00:03: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 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 61a7 created at Sat Mar 28 19:02:54 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 2faf created at Sat Mar 28 18:00: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 28f7 created at Sat Mar 28 18:00: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 7150 created at Sat Mar 28 17:36: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: Verifying a signature, but no certificate was provided:
Signature 7fb4 created at Sat Mar 28 17:36: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: Verifying a signature, but no certificate was provided:
Signature a0cc created at Sat Mar 28 17:49: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 01d2 created at Sat Mar 28 17:49: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 ff61 created at Sat Jan 28 08:12:13 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 4bf8 created at Sat Mar 28 19:37: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 c463 created at Sat Mar 28 19:37: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 aa2d created at Sun Nov 26 22:01: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 31df created at Sun Nov 26 22:01: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 4b7a created at Sun Apr 22 11:45:36 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 8505 created at Sun May 10 11:56: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 60b3 created at Sun Apr 17 12:30:15 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 65de created at Sun Apr 17 12:30:15 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 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: Verifying a signature, but no certificate was provided:
Signature baa8 created at Sun Feb 11 16: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 e3a6 created at Sun Jul 17 09:29: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: Verifying a signature, but no certificate was provided:
Signature fd88 created at Sun Jul 17 09:29: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: Verifying a signature, but no certificate was provided:
Signature eaa8 created at Mon Mar 28 02:12:45 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 3825 created at Thu Jul 9 20:44: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 b25f created at Thu Jul 9 20:44: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 fcd8 created at Sat Jan 28 08:17:42 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 6cff created at Sat Jan 28 08:17:42 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 6d59 created at Tue Dec 22 23:57: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 5776 created at Tue Dec 22 23:57: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 264f created at Sat Mar 28 18:49: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 aedd created at Sat Mar 28 18:49: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 a72d created at Mon Mar 28 02:14:45 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 94f8 created at Sun Sep 18 21:03:30 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 aab9 created at Sun Sep 18 21:03:30 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 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 8ac6 created at Sun May 15 08:48: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 364a 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: Verifying a signature, but no certificate was provided:
Signature 2235 created at Sat Mar 28 17:39: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 843d created at Sat Mar 28 17:39: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: rpmdbNextIterator: skipping h# 382
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 385
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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 0285 created at Sun May 15 08:44:00 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 2de9 created at Sun Jul 17 09:31:48 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 6a77 created at Sun Jul 17 09:31:48 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 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 10d3 created at Sat Mar 28 17:39: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 380b created at Sat Mar 28 17:39: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 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 5d2c created at Tue Dec 20 18:09: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 c960 created at Tue Dec 20 18:09: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 234e created at Sat Mar 28 18:36: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 2346 created at Sat Mar 28 18:36: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: 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 <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 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 <https://github.com/rpm-software-management/rpm/issues/2351>.
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 e4a2 created at Mon Feb 26 15:04: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 1fdd created at Sun Apr 17 12:40: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 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 1138 created at Mon Jun 11 18:54:53 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 32bf created at Sat Mar 28 18:59: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: Verifying a signature, but no certificate was provided:
Signature 3c61 created at Sat Mar 28 17:59:11 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 6117 created at Sat Mar 28 20:29: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 80f3 created at Thu Jul 9 20:45:24 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 3085 created at Thu Jul 9 20:45:24 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 fda7 created at Thu Jun 22 01: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 671f created at Sat Mar 28 17:50:07 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 4e09 created at Sat Mar 15 12:15:52 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 e6be created at Sat Mar 28 18:57: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 975f created at Sat Mar 28 18:57:16 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 3bd2 created at Sat Mar 28 17:39: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 3873 created at Sat Mar 28 17:39: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# 470
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 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 <https://github.com/rpm-software-management/rpm/issues/2351>.
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 cc67 created at Sun Jul 29 14:47:50 2018 invalid: signature is not alive
because: Expired on 2018-08-28T14:47:50Z
error: rpmdbNextIterator: skipping h# 472
Header V4 DSA/SHA1 Signature, key ID da8b7bbb: BAD
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 <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 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 <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 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 <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 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 <https://github.com/rpm-software-management/rpm/issues/2351>.
because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110111 (77))
Header SHA1 digest: OK
error: Verifying a signature, but no certificate was provided:
Signature 0d57 created at Sat Mar 28 19:46: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 de78 created at Sat Mar 28 19:46: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 29bc created at Mon Nov 9 21:30: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 cc98 created at Sat Mar 28 19:11: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 003b created at Sat May 27 06:32: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 3092 created at Sat Oct 15 20:40:57 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 179b created at Sat Mar 28 17:56: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 9cf8 created at Sat Mar 28 17:50: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 fe73 created at Sat Mar 28 17:43: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: 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 <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 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 <https://github.com/rpm-software-management/rpm/issues/2351>.
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 602f created at Sat Mar 28 19:38: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 b175 created at Thu Jul 9 21:00: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 334f created at Sat Mar 28 19:50: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 1df0 created at Sat Mar 28 19:50: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 5f59 created at Mon Nov 9 21:17: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 1242 created at Mon Nov 9 21:17: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 1349 created at Mon Nov 9 21:04: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 2b46 created at Mon Nov 9 21:04: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 e139 created at Sun Sep 18 21:01:45 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 42c8 created at Mon Mar 26 09:52: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 8e15 created at Mon Mar 26 09:52: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 e98b created at Sun May 15 08:46:25 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 6eb9 created at Sun May 15 08:46:25 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 7d11 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: Verifying a signature, but no certificate was provided:
Signature 2ba8 created at Sat Mar 28 17:42: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 053b created at Sat Mar 28 17:42: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 396d created at Wed Dec 23 00:39: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 6669 created at Sat Oct 22 21:55:48 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 e614 created at Fri Feb 26 07:28:43 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 b9df created at Fri Feb 26 07:28:43 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 9202 created at Sat Mar 28 20:31: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 55f7 created at Sat Mar 28 20:31: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 0c7b created at Sat Mar 28 17:46: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 a731 created at Sat Mar 28 17:46: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 0fec created at Wed Jul 22 08:16: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 9e07 created at Sun Apr 22 11:45:30 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 ca61 created at Sun Apr 22 11:45:30 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 e497 created at Sat Aug 1 14:37: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 7585 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 7fe2 created at Sat Mar 28 20:46:47 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 859f created at Sat Mar 28 20:46:47 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 f41a created at Fri Feb 26 07:39:31 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 7a41 created at Sun May 15 08:46:25 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# 554
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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 7834 created at Sat Mar 28 17:36:15 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 82a4 created at Sat Mar 28 17:36:15 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 dcb3 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: Verifying a signature, but no certificate was provided:
Signature af01 created at Tue Aug 21 21:51: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 3072 created at Tue Aug 21 21:51: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 36cf created at Sun Jul 2 15:33: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 8615 created at Tue Oct 6 15:27: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# 587
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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 cdcf created at Sat Apr 18 17:00: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 cb98 created at Sat Apr 18 17:00: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 aba8 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: Verifying a signature, but no certificate was provided:
Signature 9387 created at Sun Jul 17 09:29: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 7c3d created at Sat Jan 21 19:23:47 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 724b created at Sun Sep 13 18:28:33 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 2125 created at Sun Sep 13 18:28:33 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 bec4 created at Sat Mar 28 17:45: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 6111 created at Wed Dec 27 09:31:07 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 bf10 created at Sat Mar 28 18:01: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 62fd created at Sat May 27 06:39:04 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 c178 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 c037 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 a604 created at Sun Jul 2 15:35:55 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 f894 created at Sun Jul 2 15:35: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 6673 created at Sat Mar 28 17:54: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 f924 created at Sat Mar 28 17:54: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 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: Verifying a signature, but no certificate was provided:
Signature 4b9a created at Sat Mar 28 17:53:45 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 e757 created at Sat Mar 28 17:53:45 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 5026 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 5e95 created at Sat Mar 28 18:56: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: Verifying a signature, but no certificate was provided:
Signature 64d2 created at Sat Mar 28 20:23: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 bc9a created at Sat Mar 28 18:38: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 b4eb created at Sat Mar 28 18:52: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 50c9 created at Sat Mar 28 18:52: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 932b created at Sat Mar 28 18:52: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 a27b created at Thu Jun 22 01:38:29 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 6044 created at Thu Jun 22 01:38:29 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 9076 created at Thu Jul 9 21:00: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 acd7 created at Thu Jul 9 21:00: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 a6b1 created at Mon Nov 9 21:29: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 02f4 created at Tue Aug 21 22:14: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 4589 created at Wed Dec 23 00:39:54 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 0a8b created at Wed Dec 23 00:39: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 043e created at Sat Mar 28 17:36: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 181b created at Sat Mar 28 17:36: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 f4c8 created at Wed Dec 23 00:58: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 486d created at Wed Dec 23 00:58: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 bd62 created at Tue Dec 13 06:44: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: Verifying a signature, but no certificate was provided:
Signature 6b62 created at Tue Dec 13 06:44: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: Verifying a signature, but no certificate was provided:
Signature d825 created at Tue Dec 13 06:44: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: Verifying a signature, but no certificate was provided:
Signature 5ab7 created at Sat Mar 28 19:02: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 3716 created at Sat Mar 28 19:02: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 e691 created at Sat Mar 28 19: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 8544 created at Sat Mar 28 19: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 a496 created at Sat Mar 28 20: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 d73e created at Sat Mar 28 20: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 9079 created at Wed Dec 27 09:28: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 20f4 created at Wed Dec 23 00:46: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 2c5d created at Sat Mar 28 20:41:11 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 a80b created at Sat Mar 28 20: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 ba5e created at Sat Mar 28 17:42: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 cffe created at Sat Mar 28 17:42: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 8e28 created at Mon Nov 9 21:30: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 4260 created at Thu May 7 20:28: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 8bae created at Tue Oct 6 15:34: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 e171 created at Sat Mar 28 20:45:20 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 d278 created at Sat Mar 28 20:45:20 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 bdbd 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 15bb created at Sat Mar 28 19:06: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 91b8 created at Sat Mar 28 19:06: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 156e created at Mon Jun 1 06:45: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 22c9 created at Mon Jun 1 06:45: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 938d created at Wed May 4 11:31:03 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 cb81 created at Wed May 4 11:31:03 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 a07d created at Wed Dec 27 09:29:53 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 b46b created at Wed Dec 27 09:29:53 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 ab61 created at Sat Mar 28 18:35: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 d86d created at Sat Mar 28 18:35: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 7087 created at Sat Mar 28 20:40: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 0ae8 created at Sat Mar 28 20:40: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 603c created at Sun May 10 11:58: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 c349 created at Sun Jan 22 10:32:16 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 ef33 created at Sun Sep 18 20:58: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 9041 created at Sun Sep 18 20:58: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 699b created at Sat Mar 28 20:38:16 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 e20d created at Sat Mar 28 20:38:16 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 58e4 created at Sun Jul 17 09:28: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 7a67 created at Thu Jul 9 20:45: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 8d93 created at Thu Jul 9 20:45: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 fab0 created at Sun Apr 22 11:52: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 d4e8 created at Thu May 7 20:25: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 2c60 created at Thu May 7 20:25: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 7b67 created at Sat Jan 2 18:24:38 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 5968 created at Sat Jan 2 18:24:38 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# 751
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 10100 (14))
Header SHA1 digest: OK
error: Verifying a signature, but no certificate was provided:
Signature af47 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 d5dc created at Sun Sep 18 21:06: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 ec23 created at Tue Dec 5 07:46:16 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 26ae created at Sat Mar 28 20:17: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 8b0a created at Tue Dec 5 07:46:16 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 6672 created at Sat May 27 06:41:53 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 a3da created at Sat Mar 28 20:47: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 4249 created at Sat Mar 28 20:47: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: rpmdbNextIterator: skipping h# 777
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 778
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 779
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 11101 (1d))
Header SHA1 digest: OK
error: Verifying a signature, but no certificate was provided:
Signature 0eba created at Wed Jul 22 08:16: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: rpmdbNextIterator: skipping h# 796
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 797
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 798
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 799
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 800
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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 441c created at Mon Oct 1 18:01:38 2018 invalid: signature is not alive
because: Expired on 2018-10-31T18:01:38Z
error: rpmdbNextIterator: skipping h# 801
Header V4 DSA/SHA1 Signature, key ID e08e6058: BAD
Header SHA1 digest: OK
error: rpmdbNextIterator: skipping h# 802
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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 e78b created at Sat Oct 15 20:41: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: Verifying a signature, but no certificate was provided:
Signature 0eee created at Wed Dec 27 09:04: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 9e6b created at Sun May 10 12:00: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 efcb created at Sun May 10 12:00: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 b5ff created at Thu Jul 9 21:01: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# 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 <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 818
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 819
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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 52ff created at Sat Mar 28 17:42: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 c389 created at Sat Mar 28 17:42: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 5037 created at Sun Apr 22 11:56: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 004c created at Sun Apr 22 11:56:03 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# 832
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 833
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111010 (3a))
Header SHA1 digest: OK
error: Verifying a signature, but no certificate was provided:
Signature 7c90 created at Wed Oct 17 19:30:38 2018 invalid: signature is not alive
because: Expired on 2018-11-16T19:30:38Z
error: rpmdbNextIterator: skipping h# 834
Header V4 DSA/SHA1 Signature, key ID ce0cf106: BAD
Header SHA1 digest: OK
error: rpmdbNextIterator: skipping h# 842
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 100011 (23))
Header SHA1 digest: OK
error: Verifying a signature, but no certificate was provided:
Signature 9184 created at Sat Feb 27 19:06:29 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 c9c2 created at Wed Dec 27 09:16:46 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 89d0 created at Sat Feb 27 19:06:31 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 8b09 created at Sat Feb 27 19:06:29 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 ee7b created at Wed Dec 27 09:16: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 9ee3 created at Sat Mar 28 18:49: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 076c created at Sat Mar 28 18:49: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 6f8d created at Sat Mar 28 17:57: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 ac6f created at Sat Mar 28 17:57: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 e182 created at Fri Feb 15 20:24:50 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 c2d2 created at Fri Feb 15 20:24:50 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 c2ce created at Sat Mar 28 18:50: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 dc09 created at Sat Mar 28 18:50: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: rpmdbNextIterator: skipping h# 863
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 864
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 865
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 866
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 871
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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 bcfa created at Sun Apr 17 11:26:17 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 fdf5 created at Sun Apr 17 11:26:17 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 4213 created at Mon Nov 9 21:09: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 001e created at Mon Nov 9 21:09: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 e0c7 created at Thu May 24 12:37:24 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 95dc created at Thu May 24 12:37:24 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 8a05 created at Sun May 10 11:54: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 cb1a created at Sun Feb 11 16:51:03 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# 912
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 913
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 10 (2))
Header SHA1 digest: OK
error: Verifying a signature, but no certificate was provided:
Signature 9103 created at Fri Feb 26 07:31:37 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# 919
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 920
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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 0062 created at Sat Dec 1 22:37:49 2018 invalid: signature is not alive
because: Expired on 2018-12-31T22:37:49Z
error: rpmdbNextIterator: skipping h# 921
Header V4 DSA/SHA1 Signature, key ID f795f425: BAD
Header SHA1 digest: OK
error: Verifying a signature, but no certificate was provided:
Signature 8171 created at Sun Mar 5 11:02:10 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 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: Verifying a signature, but no certificate was provided:
Signature f85a created at Mon Dec 10 07:33:59 2018 invalid: signature is not alive
because: Expired on 2019-01-09T07:33:59Z
error: rpmdbNextIterator: skipping h# 928
Header V4 DSA/SHA1 Signature, key ID f177d5f6: BAD
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 <https://github.com/rpm-software-management/rpm/issues/2351>.
because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 101011 (2b))
Header SHA1 digest: OK
error: Verifying a signature, but no certificate was provided:
Signature 79e8 created at Sun Jul 27 22:27:16 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 e67e created at Sun Jul 27 22:27:16 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 7977 created at Sun Apr 17 12:31:30 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 cbae created at Sun Apr 17 12:31:30 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 fcb9 created at Sun Apr 17 11:50:05 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 3e5c created at Sun Apr 17 11:50:05 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 3d78 created at Fri Dec 21 05:52:45 2018 invalid: signature is not alive
because: Expired on 2019-01-20T05:52:45Z
error: rpmdbNextIterator: skipping h# 942
Header V4 DSA/SHA1 Signature, key ID 1aed3b19: BAD
Header SHA1 digest: OK
error: rpmdbNextIterator: skipping h# 949
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 11101 (1d))
Header SHA1 digest: OK
error: Verifying a signature, but no certificate was provided:
Signature 7aaf created at Mon Dec 24 14:13:44 2018 invalid: signature is not alive
because: Expired on 2019-01-23T14:13:44Z
error: rpmdbNextIterator: skipping h# 950
Header V4 DSA/SHA1 Signature, key ID ed079bf4: BAD
Header SHA1 digest: OK
error: rpmdbNextIterator: skipping h# 951
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 955
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 956
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 961
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 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 <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 977
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 978
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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 f0f1 created at Sat Mar 28 17:38:45 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 a5ec created at Mon Jun 1 06:52: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 ccb2 created at Mon Jun 1 06:52: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 d53b 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 c538 created at Sat Mar 28 17:59: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 5138 created at Sat Apr 18 17:17: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 2f25 created at Sat May 27 06:43:33 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 2b22 created at Sat May 27 06:43:33 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 6ef6 created at Sat Apr 18 17:17: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 6418 created at Sat Apr 18 17:02:24 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 dd10 created at Sat Apr 18 17:02:24 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 7ec2 created at Thu Jul 9 20:53: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 eca7 created at Sat Apr 18 17:18: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 4049 created at Wed Dec 23 00:08:24 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 b00d created at Sat Mar 28 20:40: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 c877 created at Sat Mar 28 20:40: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 e4cd created at Wed Feb 13 18:15:55 2019 invalid: signature is not alive
because: Expired on 2019-03-15T18:15:55Z
error: rpmdbNextIterator: skipping h# 1028
Header V4 DSA/SHA1 Signature, key ID eb40a8fc: BAD
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 <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 1030
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 1031
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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 cc60 created at Sat Mar 28 17:42:53 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 c624 created at Tue Dec 5 07:46:33 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# 1041
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 1042
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 1046
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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 c353 created at Mon Mar 26 09:09:28 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 40c6 created at Mon Mar 26 09:09:28 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# 1055
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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 581d created at Sat Oct 22 21:49:11 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 dadb created at Sat Oct 22 21:49:11 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 2cea created at Fri Feb 26 07:32:52 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 d5d7 created at Fri Feb 26 07:32:52 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 e2a2 created at Sat Mar 28 20:38:26 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 08df created at Sun Aug 9 10:18: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 a906 created at Sun Aug 9 10:18: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 cda1 created at Sun Aug 9 10:18: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 2f06 created at Sun Aug 9 10:18: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 3d99 created at Tue Oct 6 15:34: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 b97c created at Sun May 29 11:46:47 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 1e18 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 464a created at Fri Mar 15 00:22:05 2019 invalid: signature is not alive
because: Expired on 2019-04-14T00:22:05Z
error: rpmdbNextIterator: skipping h# 1080
Header V4 DSA/SHA1 Signature, key ID b7791bc3: BAD
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 <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 1086
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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 ed73 created at Sat Mar 28 20:42:16 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 43f3 created at Wed Mar 20 17:13:45 2019 invalid: signature is not alive
because: Expired on 2019-04-19T17:13:45Z
error: rpmdbNextIterator: skipping h# 1103
Header V4 DSA/SHA1 Signature, key ID 6d28ab32: 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 <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 1107
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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 992f created at Sat Mar 30 20:48:09 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 78d5 created at Tue Aug 21 22:17:58 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 6750 created at Thu Jul 9 20:54: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 8afb created at Thu Jul 9 20:54: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 c125 created at Wed Dec 23 00:49: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 b828 created at Sat Mar 30 20:28:48 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 21b9 created at Sat Mar 30 20:25:04 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 bb8f created at Sat Mar 30 20:25:04 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 1228 created at Thu Jul 9 21:00: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 a4db created at Wed May 4 11:40:03 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 d9ab created at Sun Jul 16 15:03:06 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 d8dd created at Sat Mar 28 17:40:34 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 e2ee created at Sat Mar 28 19:49: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 fe2e created at Sat Mar 28 17:40:34 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 66cf created at Sat Mar 28 20:17: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 16f0 created at Tue Aug 8 21:27: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 fb3e created at Tue Aug 8 21:27: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: rpmdbNextIterator: skipping h# 1173
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 1174
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 1175
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 1176
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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 70b6 created at Fri Apr 19 20:07:09 2019 invalid: signature is not alive
because: Expired on 2019-05-19T20:07:09Z
error: rpmdbNextIterator: skipping h# 1177
Header V4 DSA/SHA1 Signature, key ID 4518f43e: BAD
Header SHA1 digest: OK
error: rpmdbNextIterator: skipping h# 1178
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110011 (33))
Header SHA1 digest: OK
error: Verifying a signature, but no certificate was provided:
Signature df8d created at Sat Apr 18 17:20: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# 1180
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 1181
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 1182
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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 be08 created at Sat Apr 20 17:49:42 2019 invalid: signature is not alive
because: Expired on 2019-05-20T17:49:42Z
error: rpmdbNextIterator: skipping h# 1183
Header V4 DSA/SHA1 Signature, key ID 1f156bbf: BAD
Header SHA1 digest: OK
error: rpmdbNextIterator: skipping h# 1186
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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 82bb created at Sun Apr 21 18:45:45 2019 invalid: signature is not alive
because: Expired on 2019-05-21T18:45:45Z
error: rpmdbNextIterator: skipping h# 1187
Header V4 DSA/SHA1 Signature, key ID 43dba08d: BAD
Header SHA1 digest: OK
error: Verifying a signature, but no certificate was provided:
Signature 5bbe created at Wed Oct 24 06:56:28 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# 1198
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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 1dff created at Sat Apr 18 17:18: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 8a69 created at Sat Apr 18 17:18: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 728e 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 6daf 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 d3bf created at Sun Jul 16 15:03: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: 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 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 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: Verifying a signature, but no certificate was provided:
Signature ada0 created at Sat Apr 27 23:02:22 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# 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 <https://github.com/rpm-software-management/rpm/issues/2351>.
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 e12e created at Wed Oct 24 08:01:25 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 05a1 created at Sun Apr 17 11:32:12 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# 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 <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 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 <https://github.com/rpm-software-management/rpm/issues/2351>.
because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1111000 (78))
Header SHA1 digest: OK
error: Verifying a signature, but no certificate was provided:
Signature 238f created at Wed May 4 11:27:51 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 eaee created at Wed May 4 11:29:10 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 61c0 created at Wed May 4 11:29:10 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 80fc created at Sat Apr 18 17:04: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 aabf created at Sat Apr 18 17:04: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 86cf 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 be48 created at Sun Jul 15 19:04:36 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 77a3 created at Sat Mar 28 19:19: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 2136 created at Sat Mar 28 19:19: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 984c 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# 1282
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 1290
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 1291
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111010 (3a))
Header SHA1 digest: OK
error: Verifying a signature, but no certificate was provided:
Signature 528a created at Sun Jun 9 22:25:43 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# 1293
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 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 <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 1295
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 1296
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 1297
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 1298
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 1305
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 1306
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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 232f created at Sun May 10 11:59: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 b960 created at Thu Jul 9 21:22: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 52b8 created at Thu Jul 9 21:22: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: rpmdbNextIterator: skipping h# 1356
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 1357
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 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 <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 1373
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 10100 (14))
Header SHA1 digest: OK
error: Verifying a signature, but no certificate was provided:
Signature 4d39 created at Wed Oct 24 07:35: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 5c7e created at Wed Oct 24 07:35: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# 1383
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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 7d99 created at Sun Jun 30 17:53:02 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# 1393
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 1394
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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 90eb created at Sun Mar 5 11:07:21 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 a51f created at Mon Oct 2 11:25:04 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 dc5b created at Mon Nov 9 21:07: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 1ab4 created at Mon Nov 9 21:07: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 3568 created at Sat Mar 30 20:29:34 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 b972 created at Fri Sep 13 03:52:14 2019 invalid: signature is not alive
because: Expired on 2019-10-13T03:52:14Z
error: rpmdbNextIterator: skipping h# 1424
Header V4 DSA/SHA1 Signature, key ID e4e424d3: BAD
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 <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 1433
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 1434
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 1435
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 1444
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 1445
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111010 (3a))
Header SHA1 digest: OK
error: Verifying a signature, but no certificate was provided:
Signature ae65 created at Sun Sep 13 18:29: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: Verifying a signature, but no certificate was provided:
Signature 1a0d created at Sun Sep 13 18:29: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: Verifying a signature, but no certificate was provided:
Signature 281e created at Sat Mar 30 20:29:34 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 c078 created at Sat Mar 28 19:38: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 ee5d created at Sat Mar 28 19:38: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 587f created at Sat Apr 18 17:19: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 52b0 created at Sat Mar 28 19:46: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 6fdb created at Sat Mar 28 19:46: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 a9cb 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 c703 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: rpmdbNextIterator: skipping h# 1493
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 1507
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 1508
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 1509
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 1510
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 1511
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 1515
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 1516
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 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 <https://github.com/rpm-software-management/rpm/issues/2351>.
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 81c8 created at Tue Aug 28 16:46:37 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 5178 created at Sat Oct 22 21:55:17 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 4cb9 created at Sat Oct 22 21:55:17 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 4e0f created at Sat Mar 28 18:49: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: rpmdbNextIterator: skipping h# 1538
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 1543
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 1544
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 1547
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 1548
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 1549
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 100000 (20))
Header SHA1 digest: OK
error: Verifying a signature, but no certificate was provided:
Signature 59bd 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 ed1d 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 64f7 created at Sat Mar 28 17:59: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 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: Verifying a signature, but no certificate was provided:
Signature 314d created at Mon Jun 1 06:50:45 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 8f9c created at Mon Jun 1 06:50:45 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# 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 <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 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 <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 1581
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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 7668 created at Tue Aug 8 21:23:50 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# 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 <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 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 <https://github.com/rpm-software-management/rpm/issues/2351>.
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 7d71 created at Wed Oct 23 19:03:07 2019 invalid: signature is not alive
because: Expired on 2019-11-22T19:03:07Z
error: rpmdbNextIterator: skipping h# 1588
Header V4 DSA/SHA1 Signature, key ID ed150c45: BAD
Header SHA1 digest: OK
error: rpmdbNextIterator: skipping h# 1589
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 1594
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 1595
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 1606
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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 d137 created at Mon Oct 28 19:14:51 2019 invalid: signature is not alive
because: Expired on 2019-11-27T19:14:51Z
error: rpmdbNextIterator: skipping h# 1661
Header V4 DSA/SHA1 Signature, key ID 2c926445: BAD
Header SHA1 digest: OK
error: rpmdbNextIterator: skipping h# 1687
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 1737
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 1738
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 1739
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 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 <https://github.com/rpm-software-management/rpm/issues/2351>.
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 559c created at Wed Dec 23 00:37: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 310f created at Sun Mar 5 11:08: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 947e created at Sun Mar 5 11:08: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 7e5c created at Mon Nov 9 21:06:21 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 34e8 created at Mon Nov 9 21:09: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 297f created at Wed Oct 24 07:51:15 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# 1830
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 1862
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 1863
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 1868
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 1869
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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 1b5e created at Tue Jan 5 17:35:06 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# 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 <https://github.com/rpm-software-management/rpm/issues/2351>.
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 3e68 created at Sat Mar 28 17:40: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 e735 created at Mon Nov 9 21:17:34 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# 1891
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 1904
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 1905
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 1907
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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 b963 created at Sun Dec 1 08:42:22 2019 invalid: signature is not alive
because: Expired on 2019-12-31T08:42:22Z
error: rpmdbNextIterator: skipping h# 1908
Header V4 DSA/SHA1 Signature, key ID 12ff6eeb: BAD
Header SHA1 digest: OK
error: rpmdbNextIterator: skipping h# 1909
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 1910
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1000110 (46))
Header SHA1 digest: OK
error: Verifying a signature, but no certificate was provided:
Signature ee62 created at Sun Dec 1 15:26:54 2019 invalid: signature is not alive
because: Expired on 2019-12-31T15:26:54Z
error: rpmdbNextIterator: skipping h# 1911
Header V4 DSA/SHA1 Signature, key ID 7e7f36e6: BAD
Header SHA1 digest: OK
error: Verifying a signature, but no certificate was provided:
Signature 2790 created at Sun May 15 08:49: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 1bd7 created at Sun May 15 08:49: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: rpmdbNextIterator: skipping h# 2211
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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 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: Verifying a signature, but no certificate was provided:
Signature dffa created at Wed Dec 23 01:41: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 3e4a created at Sat Mar 28 17:51:24 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 6dda created at Sat Mar 28 17:51:24 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 1f93 created at Sat Mar 28 18:00: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 f677 created at Sat Mar 28 18:00: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: rpmdbNextIterator: skipping h# 2373
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 2374
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 2375
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 2393
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1111100 (7c))
Header SHA1 digest: OK
error: Verifying a signature, but no certificate was provided:
Signature d4d2 created at Wed May 4 11:31:20 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 1d6e created at Wed May 4 11:31:20 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 047e created at Sat Apr 18 19:23: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# 2462
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 2463
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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 54b0 created at Sat Apr 18 19:23: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 dee4 created at Sat Mar 28 20:44: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: rpmdbNextIterator: skipping h# 2486
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1011 (b))
Header SHA1 digest: OK
error: Verifying a signature, but no certificate was provided:
Signature 1213 created at Wed Mar 4 16:06:50 2020 invalid: signature is not alive
because: Expired on 2020-04-03T16:06:50Z
error: rpmdbNextIterator: skipping h# 2487
Header V4 DSA/SHA1 Signature, key ID 40e4c83f: BAD
Header SHA1 digest: OK
error: rpmdbNextIterator: skipping h# 2488
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 2489
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1 (1))
Header SHA1 digest: OK
error: Verifying a signature, but no certificate was provided:
Signature 4391 created at Wed Mar 4 16:06:50 2020 invalid: signature is not alive
because: Expired on 2020-04-03T16:06:50Z
error: rpmdbNextIterator: skipping h# 2490
Header V4 DSA/SHA1 Signature, key ID 40e4c83f: BAD
Header SHA1 digest: OK
error: rpmdbNextIterator: skipping h# 2491
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 2493
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 2494
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1011 (b))
Header SHA1 digest: OK
error: Verifying a signature, but no certificate was provided:
Signature 77af created at Wed Mar 4 16:06:50 2020 invalid: signature is not alive
because: Expired on 2020-04-03T16:06:50Z
error: rpmdbNextIterator: skipping h# 2495
Header V4 DSA/SHA1 Signature, key ID 40e4c83f: BAD
Header SHA1 digest: OK
error: Verifying a signature, but no certificate was provided:
Signature a962 created at Tue Mar 10 16:58:59 2020 invalid: signature is not alive
because: Expired on 2020-04-09T16:58:59Z
error: rpmdbNextIterator: skipping h# 2507
Header V4 DSA/SHA1 Signature, key ID eaa7ef8d: BAD
Header SHA1 digest: OK
error: rpmdbNextIterator: skipping h# 2515
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 2516
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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 5ef2 created at Sat Mar 14 14:38:58 2020 invalid: signature is not alive
because: Expired on 2020-04-13T14:38:58Z
error: rpmdbNextIterator: skipping h# 2517
Header V4 DSA/SHA1 Signature, key ID 3e35a271: BAD
Header SHA1 digest: OK
error: rpmdbNextIterator: skipping h# 2518
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 2527
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 2530
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 2535
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 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 <https://github.com/rpm-software-management/rpm/issues/2351>.
because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1101010 (6a))
Header SHA1 digest: OK
error: Verifying a signature, but no certificate was provided:
Signature 4911 created at Fri Mar 20 21:46:49 2020 invalid: signature is not alive
because: Expired on 2020-04-19T21:46:49Z
error: rpmdbNextIterator: skipping h# 2585
Header V4 DSA/SHA1 Signature, key ID 1a10f44e: BAD
Header SHA1 digest: OK
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 4636 created at Sun Apr 17 11:18:31 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 a25e created at Sun Apr 17 11:18:31 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# 2592
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 2593
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111000 (38))
Header SHA1 digest: OK
error: Verifying a signature, but no certificate was provided:
Signature 4dac created at Sat Mar 21 15:37:34 2020 invalid: signature is not alive
because: Expired on 2020-04-20T15:37:34Z
error: rpmdbNextIterator: skipping h# 2594
Header V4 DSA/SHA1 Signature, key ID e96f6943: BAD
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 <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 2631
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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 3206 created at Sun Apr 17 11:51: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: Verifying a signature, but no certificate was provided:
Signature 93db created at Sun Apr 17 11:51: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: Verifying a signature, but no certificate was provided:
Signature 30a1 created at Sun Nov 24 18:10:42 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# 2707
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 2708
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 2709
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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 2361 created at Fri Mar 27 00:54:03 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 9a1f created at Fri Mar 27 00:54:03 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 364a created at Fri Mar 27 00:37:30 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 6811 created at Sun Mar 29 19:34:29 2020 invalid: signature is not alive
because: Expired on 2020-04-28T19:34:29Z
error: rpmdbNextIterator: skipping h# 2725
Header V4 DSA/SHA1 Signature, key ID 2d01081f: BAD
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 <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 2746
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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 b00e created at Fri Sep 6 21:35: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: rpmdbNextIterator: skipping h# 2819
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1000110 (46))
Header SHA1 digest: OK
error: Verifying a signature, but no certificate was provided:
Signature a34c created at Sat Mar 14 12:04:29 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 443b created at Sat Mar 14 12:04:29 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 e871 created at Fri Apr 24 18:03:52 2020 invalid: signature is not alive
because: Expired on 2020-05-24T18:03:52Z
error: rpmdbNextIterator: skipping h# 2896
Header V4 DSA/SHA1 Signature, key ID efe14a6c: BAD
Header SHA1 digest: OK
error: rpmdbNextIterator: skipping h# 2897
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 2912
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 2913
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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 ffec created at Sun Apr 26 19:18:12 2020 invalid: signature is not alive
because: Expired on 2020-05-26T19:18:12Z
error: rpmdbNextIterator: skipping h# 2916
Header V4 DSA/SHA1 Signature, key ID 23fba33e: BAD
Header SHA1 digest: OK
error: rpmdbNextIterator: skipping h# 2917
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 2918
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 2928
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 2929
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 2938
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 111010 (3a))
Header SHA1 digest: OK
error: Verifying a signature, but no certificate was provided:
Signature 692b created at Fri May 1 19:21:38 2020 invalid: signature is not alive
because: Expired on 2020-05-31T19:21:38Z
error: rpmdbNextIterator: skipping h# 2939
Header V4 DSA/SHA1 Signature, key ID b2093c91: BAD
Header SHA1 digest: OK
error: rpmdbNextIterator: skipping h# 2941
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 2942
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 3030
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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 72e8 created at Wed May 6 22:09:40 2020 invalid: signature is not alive
because: Expired on 2020-06-05T22:09:40Z
error: rpmdbNextIterator: skipping h# 3031
Header V4 DSA/SHA1 Signature, key ID c2a66ba7: BAD
Header SHA1 digest: OK
error: Verifying a signature, but no certificate was provided:
Signature c309 created at Wed May 6 22:09:40 2020 invalid: signature is not alive
because: Expired on 2020-06-05T22:09:40Z
error: rpmdbNextIterator: skipping h# 3032
Header V4 DSA/SHA1 Signature, key ID c2a66ba7: BAD
Header SHA1 digest: OK
error: rpmdbNextIterator: skipping h# 3033
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 3041
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 3076
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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 e684 created at Mon May 18 20:16:33 2020 invalid: signature is not alive
because: Expired on 2020-06-17T20:16:33Z
error: rpmdbNextIterator: skipping h# 3121
Header V4 DSA/SHA1 Signature, key ID 9b9d9215: BAD
Header SHA1 digest: OK
error: rpmdbNextIterator: skipping h# 3122
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 3125
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 3126
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 3127
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 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 <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 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 <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 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 <https://github.com/rpm-software-management/rpm/issues/2351>.
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 7630 created at Sat Jan 2 18:14:11 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 f06a created at Sun Jun 9 23:29:13 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# 3146
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 3147
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 3187
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 3188
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 3189
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 3190
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 3206
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 3207
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 3242
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 3243
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 3260
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 3261
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 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 <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 3446
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 3463
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1001 (9))
Header SHA1 digest: OK
error: Verifying a signature, but no certificate was provided:
Signature 6008 created at Mon Jun 1 14:28:21 2020 invalid: signature is not alive
because: Expired on 2020-07-01T14:28:21Z
error: rpmdbNextIterator: skipping h# 3464
Header V4 DSA/SHA1 Signature, key ID 8c404846: BAD
Header SHA1 digest: OK
error: rpmdbNextIterator: skipping h# 3469
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 3470
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 3478
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 100101 (25))
Header SHA1 digest: OK
error: Verifying a signature, but no certificate was provided:
Signature 246f created at Tue Jun 2 17:29:32 2020 invalid: signature is not alive
because: Expired on 2020-07-02T17:29:32Z
error: rpmdbNextIterator: skipping h# 3479
Header V4 DSA/SHA1 Signature, key ID 1e9dccef: BAD
Header SHA1 digest: OK
error: rpmdbNextIterator: skipping h# 3481
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 3482
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 3488
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 3489
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 3517
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 3670
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1010000 (50))
Header SHA1 digest: OK
error: Verifying a signature, but no certificate was provided:
Signature 559a created at Fri Apr 14 16:43:06 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# 3725
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 3726
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 3774
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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 94d3 created at Sun Jul 12 18:42:20 2020 invalid: signature is not alive
because: Expired on 2020-08-11T18:42:20Z
error: rpmdbNextIterator: skipping h# 3775
Header V4 DSA/SHA1 Signature, key ID d3176614: BAD
Header SHA1 digest: OK
error: rpmdbNextIterator: skipping h# 3829
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 3830
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 3902
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 3903
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1011111 (5f))
Header SHA1 digest: OK
error: Verifying a signature, but no certificate was provided:
Signature 623f created at Sun Jun 26 21:52: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 b8d5 created at Sun Jun 26 21:49:52 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 22a4 created at Sat Mar 28 17:45: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 5357 created at Sat Mar 28 17:42: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 c371 created at Sat Mar 28 17:42: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: rpmdbNextIterator: skipping h# 3948
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 3949
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 3979
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 4005
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 4055
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 4058
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 4059
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 4086
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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 8419 created at Wed Sep 2 19:51:44 2020 invalid: signature is not alive
because: Expired on 2020-10-02T19:51:44Z
error: rpmdbNextIterator: skipping h# 4087
Header V4 DSA/SHA1 Signature, key ID c9ca9051: BAD
Header SHA1 digest: OK
error: rpmdbNextIterator: skipping h# 4088
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 4137
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 4138
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 4267
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 4269
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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 7db7 created at Sat Sep 19 01:47:40 2020 invalid: signature is not alive
because: Expired on 2020-10-19T01:47:40Z
error: rpmdbNextIterator: skipping h# 4270
Header V4 DSA/SHA1 Signature, key ID ab791cbb: BAD
Header SHA1 digest: OK
error: rpmdbNextIterator: skipping h# 4273
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 4291
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 4293
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 4343
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 4364
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 4365
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 4398
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 4606
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 4607
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 4632
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 4633
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 11101 (1d))
Header SHA1 digest: OK
error: Verifying a signature, but no certificate was provided:
Signature 18d6 created at Mon Oct 19 07:30:55 2020 invalid: signature is not alive
because: Expired on 2020-11-18T07:30:55Z
error: rpmdbNextIterator: skipping h# 4638
Header V4 DSA/SHA1 Signature, key ID 1ba6baee: BAD
Header SHA1 digest: OK
error: Verifying a signature, but no certificate was provided:
Signature dea2 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# 4652
Header V4 DSA/SHA1 Signature, key ID 59dffd72: BAD
Header SHA1 digest: OK
error: rpmdbNextIterator: skipping h# 4653
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 4656
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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 aae0 created at Mon Oct 26 20:08:07 2020 invalid: signature is not alive
because: Expired on 2020-11-25T20:08:07Z
error: rpmdbNextIterator: skipping h# 4686
Header V4 DSA/SHA1 Signature, key ID 48a50eb8: BAD
Header SHA1 digest: OK
error: Verifying a signature, but no certificate was provided:
Signature 5d12 created at Mon Oct 26 20:08:07 2020 invalid: signature is not alive
because: Expired on 2020-11-25T20:08:07Z
error: rpmdbNextIterator: skipping h# 4691
Header V4 DSA/SHA1 Signature, key ID 48a50eb8: BAD
Header SHA1 digest: OK
error: rpmdbNextIterator: skipping h# 4692
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 4708
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 4776
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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 3d05 created at Sun Sep 18 21:10:43 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 057f created at Thu Nov 12 19:54:34 2020 invalid: signature is not alive
because: Expired on 2020-12-12T19:54:34Z
error: rpmdbNextIterator: skipping h# 4797
Header V4 DSA/SHA1 Signature, key ID 18cb6619: BAD
Header SHA1 digest: OK
error: rpmdbNextIterator: skipping h# 4798
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 4801
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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 9057 created at Sat Nov 14 16:59:22 2020 invalid: signature is not alive
because: Expired on 2020-12-14T16:59:22Z
error: rpmdbNextIterator: skipping h# 4802
Header V4 DSA/SHA1 Signature, key ID 25da038d: BAD
Header SHA1 digest: OK
error: Verifying a signature, but no certificate was provided:
Signature e8a7 created at Sat Mar 28 20:29: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# 4865
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 4866
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 110100 (34))
Header SHA1 digest: OK
error: Verifying a signature, but no certificate was provided:
Signature 7f46 created at Fri Feb 26 07:32:18 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 b21f created at Fri Feb 26 07:32:18 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# 4870
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 4903
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 5019
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 5029
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 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 <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 5059
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 5060
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 5170
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 5171
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 5193
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1111101 (7d))
Header SHA1 digest: OK
error: Verifying a signature, but no certificate was provided:
Signature 0aa3 created at Sun Dec 13 23:56: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 7122 created at Sun Dec 13 23:56: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 2b8f created at Sat Jan 2 09:58: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: rpmdbNextIterator: skipping h# 5259
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 5260
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 5263
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 5264
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 5313
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 5427
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 5428
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 5429
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 5430
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 5431
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1111101 (7d))
Header SHA1 digest: OK
error: Verifying a signature, but no certificate was provided:
Signature 253f created at Sun Jan 17 10:50:04 2021 invalid: signature is not alive
because: Expired on 2021-02-16T10:50:04Z
error: rpmdbNextIterator: skipping h# 5434
Header V4 DSA/SHA1 Signature, key ID 7a900d31: BAD
Header SHA1 digest: OK
error: Verifying a signature, but no certificate was provided:
Signature a3a6 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# 5463
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 5464
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1110110 (76))
Header SHA1 digest: OK
error: Verifying a signature, but no certificate was provided:
Signature fa82 created at Wed Oct 24 07:31:09 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 05db created at Wed Oct 24 07:00:29 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 1cdc 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 805f created at Sat Aug 1 14:32: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: 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 <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 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 <https://github.com/rpm-software-management/rpm/issues/2351>.
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# 5721
Header DSA signature: BAD (header tag 267: invalid OpenPGP signature: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
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 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 a7c1 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 22ea 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 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: Verifying a signature, but no certificate was provided:
Signature 339b 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 c5fd created at Thu Mar 29 06:30:40 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 4026 created at Wed Mar 17 21:21: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: Verifying a signature, but no certificate was provided:
Signature 2f28 created at Wed Mar 17 21:21: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: Verifying a signature, but no certificate was provided:
Signature 7cf1 created at Wed Dec 27 09:26: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 696c created at Wed Dec 27 09:26: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 16c5 created at Thu Mar 29 06:30:40 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 a7fd created at Thu Mar 29 06:44:45 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 9b83 created at Thu Mar 29 06:44:46 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 a16b created at Thu Mar 29 06:44:46 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 10aa created at Sun May 10 11:59: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 1f3f created at Sat Oct 15 20:40:13 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 8e4b created at Sat Oct 15 20:38: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 2f6b created at Wed Dec 23 01:36: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 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 47a1 created at Sun Feb 9 09:35:49 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 8c10 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 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 c350 created at Sat Oct 22 07:58:38 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 9988 created at Sat Oct 22 18:04:08 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 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 f162 created at Sat Oct 22 07:58:36 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 7bab created at Sat Oct 22 07:58:37 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 4d04 created at Sat Oct 22 07:58:37 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 f3af created at Wed Oct 26 16:20:21 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 2b63 created at Sat Oct 22 18:04:08 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 a728 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 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 a956 created at Wed Oct 26 16:20:18 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 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 3499 created at Wed Apr 28 17:46:55 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 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 6c82 created at Thu Mar 19 21:23:18 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 3ebb created at Thu Mar 19 21:23:18 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 c91f created at Sun Apr 17 11:49:25 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 3803 created at Sun Apr 17 11:49:25 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 9328 created at Sun Apr 17 11:49:25 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 b746 created at Sun May 17 10:03: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 8b35 created at Sun May 17 10:03: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 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 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 b8ee created at Mon Mar 26 09:01:34 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 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 7b38 created at Fri Mar 27 00:54: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 b402 created at Fri Mar 27 00:53:15 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 b606 created at Thu May 7 20:28:59 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 3b0e created at Thu May 7 20:28:59 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 d00f created at Fri Sep 4 08:43: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 b7de created at Sat Mar 28 17:47: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 1177 created at Mon Sep 30 16:26:44 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 9c1c created at Mon Sep 30 16:26:44 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 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
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 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 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 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 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 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 27f1 created at Sat Jan 2 10:00:34 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 4134 created at Thu Apr 1 20:00: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 c307 created at Thu Apr 1 20:00: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 452d created at Wed Oct 26 16:20:17 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 07aa created at Wed Oct 26 16:20:18 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 4f96 created at Wed Oct 26 16:20:20 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 de9d created at Wed Oct 26 16:20:21 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 8862 created at Wed Oct 26 16:20:21 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 f986 created at Wed Oct 26 16:20:19 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 a2e0 created at Sun Aug 23 18:53: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 4e99 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 f1c1 created at Sat Oct 30 09:33: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 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 bb74 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 0472 created at Wed Mar 2 19:20: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 dc42 created at Wed Mar 2 19: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 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 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 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 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 79f9 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 90bf created at Sun Apr 10 01:24: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 0b99 created at Sun Apr 10 01:24: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 fd0e created at Sat Mar 28 20:38: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 31a6 created at Sat Mar 28 20:38: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 615f created at Sat Mar 28 17:53: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 8a05 created at Sat Mar 28 17:53: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 c5d2 created at Sun Dec 13 23:52:44 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 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 f28b created at Sun Apr 10 01:41: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 35aa created at Sun Apr 10 01:25: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 55d7 created at Sun Apr 10 00: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 e91f created at Sun Apr 10 00:38: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 bdea created at Sun Apr 10 00:38: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 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 aca3 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 45df created at Tue Aug 21 22:27: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 318a created at Sat Dec 11 01:09: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 deb1 created at Mon Jul 2 20:35:26 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 7542 created at Mon Jul 2 20:35:26 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 b1d0 created at Mon Oct 19 12:55: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 a773 created at Sat Mar 28 20:18: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 74c5 created at Sun Jun 12 21:26: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 280c created at Mon Jul 4 23:18: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 5cff created at Mon Jul 4 23:18: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 00e3 created at Sun Apr 10 00:31: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 531d created at Sun Aug 14 11:49: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 9532 created at Sun Aug 14 12:06: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 42db created at Sat Dec 11 01:09: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 a983 created at Mon Dec 31 18:41:12 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 e368 created at Sun May 17 10:02:24 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 2550 created at Sun Sep 18 21:06: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 44ee created at Sat Mar 28 17:44: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 57a1 created at Sat Mar 28 19:59: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 4719 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 716f created at Sat Mar 28 18:00: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 e4ab created at Wed Oct 24 08:03:23 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 c500 created at Wed Oct 24 08:03:23 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 4bc5 created at Sun Dec 13 23:35: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 ca2d created at Sun Dec 13 23:35: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 437c created at Sun Dec 13 23:41:42 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 0954 created at Sat Mar 28 18:00:45 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 8e6f created at Sat Mar 28 18:38: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 4ebe 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 69bf created at Thu Feb 17 23:47: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 e769 created at Sat Mar 28 19:02:54 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 1455 created at Mon Nov 9 21:29: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 54a7 created at Sat Jan 2 10:11:54 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 cff9 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 08ac created at Sun Dec 13 23:25: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 e94c created at Sun Aug 14 11:45: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 cbf9 created at Sat Jul 17 22:32:42 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 07b4 created at Wed Oct 24 08:07:02 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 210f created at Sat Dec 11 01:06: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 443c created at Mon Oct 19 13:12:49 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 158c created at Sun Dec 13 23:24: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 1600 created at Sun Dec 13 23:40:36 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 47ba created at Wed Oct 24 08:05:45 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 b47d created at Sun Aug 28 21:17: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 7859 created at Sat Mar 28 19:00:59 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 b105 created at Tue Aug 21 22:27:43 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 c60b created at Sun Dec 13 23:29: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 884f created at Sun Jun 9 23:06: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 34df created at Sat Mar 28 17:42:53 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 008e created at Sun Aug 29 00:21: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 df22 created at Sat Sep 28 17:55:26 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 2ac5 created at Sat Jul 25 11:20: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 b1a3 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 dc67 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 5b62 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 7df2 created at Wed May 4 11:27:51 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 4003 created at Sat Mar 28 20:44:18 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 655e created at Thu Mar 19 21:24:57 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 e007 created at Thu Mar 24 00:04: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 9283 created at Sat Mar 28 17:38:16 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 5021 created at Sat Mar 28 17:38:16 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 d862 created at Tue Apr 20 21:44: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 37b3 created at Tue Apr 20 21:44:54 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 48a8 created at Thu Mar 24 00:04: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 afb9 created at Sat Oct 26 15:36:05 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 1357 created at Wed Feb 17 07:51:42 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 738f created at Wed Feb 17 07:51: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 3472 created at Thu Mar 24 00:04: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 9859 created at Thu Mar 24 00:04: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 d85b 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 229d 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 9e49 created at Sun Jun 9 22:55:25 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 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 5635 created at Sun May 17 10:16: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: Verifying a signature, but no certificate was provided:
Signature c060 created at Fri Feb 26 07:41: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: Verifying a signature, but no certificate was provided:
Signature de6d created at Fri Feb 26 07:41: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: Verifying a signature, but no certificate was provided:
Signature f160 created at Mon May 24 10:06: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 66ba created at Sun Aug 28 20:51: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 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 7086 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 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 0c88 created at Sun Oct 30 10:15: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 d71d created at Sat Jul 25 11:08:03 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 5e55 created at Sun Aug 14 12:35: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 baf2 created at Mon Dec 31 18:41:58 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 8d01 created at Mon Oct 19 12:55: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 b247 created at Mon Oct 19 12:55: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 f69c created at Sun Mar 5 11:02:10 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 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 3ba5 created at Sun May 10 11:54: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 b7e3 created at Sun Dec 18 23:55:15 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 77bb created at Tue Sep 21 00:33: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 3167 created at Sun Aug 14 12:21: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 db7a created at Sun Aug 14 12:21: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 678c created at Thu May 7 20:27: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 43bd created at Thu May 7 20:27: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 74e8 created at Sun Jun 12 21:26: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 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 d456 created at Sun Dec 18 23:55: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 6af4 created at Thu May 24 11:59:34 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 6c3c created at Thu May 24 12:30:28 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 18be created at Sun Aug 14 12:06: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 507d created at Sun Nov 24 18:12: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: Verifying a signature, but no certificate was provided:
Signature 02cf created at Sat Oct 30 10:47:18 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 872f created at Sat Oct 30 10:47:18 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 4633 created at Sun Apr 22 11:52: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 00d0 created at Wed Dec 23 00:49: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 7db3 created at Wed Dec 23 00:49: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 6a1c created at Wed Dec 23 00:37: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 1524 created at Wed Dec 23 00:37: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 65a3 created at Thu Mar 24 00:30: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 ab6c created at Thu Mar 24 00:04: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 c9bc created at Thu Mar 24 00:20: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 4cd5 created at Thu Mar 24 00:11: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 f5c8 created at Thu Mar 24 00:19: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 8219 created at Thu Mar 24 00:02: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 21a3 created at Sat Mar 28 17:55: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 d178 created at Thu Mar 24 00:20: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 86a5 created at Thu Mar 24 00:20: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 ede0 created at Thu Mar 24 00:11:15 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 1fda created at Thu Mar 24 00:14: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 9d8e created at Thu Mar 24 00:11:15 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 5a64 created at Thu Mar 24 00:25: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 1964 created at Thu Mar 24 00:06: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 0776 created at Thu Mar 24 00:19: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 ceb9 created at Thu Mar 24 00:13: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 00fa created at Thu Mar 24 00:04: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 d832 created at Thu Mar 24 00:04: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 110d created at Thu Mar 24 00:03: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 6bfc created at Thu Mar 24 00:21: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 2798 created at Thu Mar 24 00:23: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 a54d created at Thu Mar 24 00:05: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 0e9d created at Thu Mar 24 00:19: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 a6c2 created at Thu Mar 24 00:18: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 0abe created at Thu Mar 24 00:20: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 0e88 created at Thu Mar 24 00:14: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 0dad created at Thu Mar 24 00:12: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 29d7 created at Thu Mar 24 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 5afa created at Thu Mar 24 00: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 47f7 created at Thu Mar 24 00:12: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 e0e3 created at Thu Mar 24 00:20: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 5383 created at Thu Mar 24 00:21: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 e7ad created at Thu Mar 24 00:23: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 d91e created at Thu Mar 24 00:05: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 e5fa created at Thu Mar 24 00:04: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 427f created at Thu Mar 24 00:04: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 7d57 created at Thu Mar 24 00:13: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 8378 created at Thu Mar 24 00:03: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 51de created at Thu Mar 24 00: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 15a3 created at Thu Mar 24 00:06: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 7bed created at Thu Mar 24 00:18: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 fe1e created at Thu Mar 24 00:18: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 5b87 created at Thu Mar 24 00:02: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 d57a created at Thu Mar 24 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 9996 created at Thu Mar 24 00:04: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 6018 created at Thu Mar 24 00: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 fca5 created at Thu Mar 24 00:18: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 d6f7 created at Thu Mar 24 00:21: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 4f72 created at Thu Mar 24 00:05: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 503b created at Thu Mar 24 00:05: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 c72e created at Thu Mar 24 00:30: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 f11e created at Thu Mar 24 00:28: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 a7b7 created at Thu Mar 24 00:22: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 e710 created at Thu Mar 24 00:20: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 88e2 created at Thu Mar 24 00:22: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 26dd created at Thu Mar 24 00:30: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 ed94 created at Thu Mar 24 00:28: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 e22f created at Thu Mar 24 00:29: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 1325 created at Thu Mar 24 00:03: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 5377 created at Thu Mar 24 00:03: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 360e created at Thu Mar 24 00:29: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 4597 created at Thu Mar 24 00:20: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 d189 created at Thu Mar 24 00:03: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 1932 created at Thu Mar 24 00:10: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 f659 created at Thu Mar 24 00:27: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 ad04 created at Thu Mar 24 00:30: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 0c03 created at Thu Mar 24 00:03:25 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 376b created at Thu Mar 24 00:14: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 fa65 created at Thu Mar 24 00:03: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 e65c created at Thu Mar 24 00:10: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 a1ea created at Thu Mar 24 00:23:44 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 8a1f created at Thu Mar 24 00:03:25 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 e4ae created at Thu Mar 24 00:14: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 5e64 created at Thu Mar 24 00:23:44 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 c9f0 created at Thu Mar 24 00:27: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 27d4 created at Thu Mar 24 00:19:44 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 cee8 created at Thu Mar 24 00:03: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 38c0 created at Thu Mar 24 00:26: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 2643 created at Thu Mar 24 00:09: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 f764 created at Thu Mar 24 00:12: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 fb48 created at Thu Mar 24 00:24: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 532d created at Thu Mar 24 00:04: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 a4ef created at Thu Mar 24 00:09: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 24fa created at Thu Mar 24 00: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 424c created at Thu Mar 24 00:03: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 2144 created at Thu Mar 24 00:23: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 a1a7 created at Thu Mar 24 00:10:25 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 3a7c created at Thu Mar 24 00:09: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 cec4 created at Thu Mar 24 00:25: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 4ca9 created at Thu Mar 24 00:20: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 db6f created at Thu Mar 24 00:10: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 3c15 created at Thu Mar 24 00:10: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 fe73 created at Thu Mar 24 00: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 f26b created at Thu Mar 24 00:21: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 12f4 created at Thu Mar 24 00:05: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 a30a created at Thu Mar 24 00:03: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 db14 created at Thu Mar 24 00:30: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 cfc1 created at Thu Mar 24 00:15: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 21e7 created at Thu Mar 24 00:06: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 ee91 created at Thu Mar 24 00:23: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 ac02 created at Thu Mar 24 00:23: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 2409 created at Thu Mar 24 00:13: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 8f1b created at Thu Mar 24 00:28: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 98ec created at Thu Mar 24 00:30: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 0b12 created at Thu Mar 24 00:09: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 17c2 created at Thu Mar 24 00:09: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 1c45 created at Thu Mar 24 00:09: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 7c07 created at Thu Mar 24 00:04: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 8f50 created at Thu Mar 24 00:14: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 b976 created at Thu Mar 24 00:24: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 f1f0 created at Thu Mar 24 00:20: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 dfd7 created at Thu Mar 24 00:03: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 5d27 created at Thu Mar 24 00:23: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 c169 created at Thu Mar 24 00:10:25 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 ebad created at Thu Mar 24 00:25: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 ba88 created at Thu Mar 24 00:20: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 e0c9 created at Thu Mar 24 00:21: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 e8a4 created at Thu Mar 24 00:05: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 4bfe created at Thu Mar 24 00:25: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 a3ad created at Thu Mar 24 00:27: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 5438 created at Thu Mar 24 00:21: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 93cd created at Thu Mar 24 00:04: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 1cda created at Thu Mar 24 00:21: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 9f90 created at Thu Mar 24 00:11: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 f2ea created at Thu Mar 24 00:17: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 1fbc created at Thu Mar 24 00:10: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 231c created at Thu Mar 24 00:28: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 66dd created at Thu Mar 24 00:13: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 15ac created at Thu Mar 24 00:15: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 c03b created at Thu Mar 24 00:23: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 cafc created at Thu Mar 24 00:27: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 646b created at Thu Mar 24 00:25: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 ffc4 created at Thu Mar 24 00:29: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 ffd3 created at Thu Mar 24 00:04: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 3964 created at Thu Mar 24 00:30: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 c91e created at Thu Mar 24 00:02: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 6fa7 created at Thu Mar 24 00:21: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 0443 created at Thu Mar 24 00:22: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 bc70 created at Thu Mar 24 00:04: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 cd67 created at Thu Mar 24 00:22: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 790f created at Thu Mar 24 00:15: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 d392 created at Thu Mar 24 00:30: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 7f8e created at Thu Mar 24 00:09: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 f30f created at Thu Mar 24 00:09: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 7e1e created at Thu Mar 24 00:30: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 eac5 created at Thu Mar 24 00:06: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 b2c2 created at Thu Mar 24 00:30: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 97f2 created at Thu Mar 24 00:19: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 8193 created at Thu Mar 24 00:15:44 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 26b1 created at Thu Mar 24 00:09: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 1084 created at Thu Mar 24 00:09: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 6887 created at Thu Mar 24 00:19: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 f756 created at Thu Mar 24 00:19: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 15a8 created at Thu Mar 24 00:25: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 52fd created at Thu Mar 24 00:12: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 e21c created at Thu Mar 24 00:09: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 7e1d created at Thu Mar 24 00:18: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 9bb5 created at Thu Mar 24 00:15:44 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 59b2 created at Thu Mar 24 00:30: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 4aa5 created at Thu Mar 24 00:06: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 ae7a created at Thu Mar 24 00:19: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 14c1 created at Thu Mar 24 00:30: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 7c34 created at Thu Mar 24 00:20: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 d609 created at Thu Mar 24 00:04: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 3ccf created at Thu Mar 24 00:10: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 ed7b created at Thu Mar 24 00:17: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 410e created at Thu Mar 24 00:06: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 eef8 created at Thu Mar 24 00:02: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 bc3e created at Thu Mar 24 00:30: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 fc5b created at Thu Mar 24 00:05: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 fdb5 created at Thu Mar 24 00: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 4efe created at Thu Mar 24 00:22: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 e152 created at Thu Mar 24 00:25: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 236e created at Thu Mar 24 00:21: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 06d6 created at Thu Mar 24 00:04: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 a519 created at Thu Mar 24 00:14: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 30a5 created at Thu Mar 24 00:11: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 2aa0 created at Thu Mar 24 00:25: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 f312 created at Thu Mar 24 00:21: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 9db8 created at Thu Mar 24 00: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 3043 created at Thu Mar 24 00:15: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 9727 created at Thu Mar 24 00:23: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 edcd created at Thu Mar 24 00:24: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 7f0d created at Thu Mar 24 00:21: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 47b8 created at Thu Mar 24 00:27: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 7621 created at Thu Mar 24 00:22: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 36b9 created at Thu Mar 24 00:25: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 0b83 created at Thu Mar 24 00:21: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 c47b created at Thu Mar 24 00:11: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 3e0a created at Thu Mar 24 00:20: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 eeed created at Thu Mar 24 00:04: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 348c created at Thu Mar 24 00:03: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 d395 created at Thu Mar 24 00:09: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 b863 created at Thu Mar 24 00:30: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 bb9f created at Thu Mar 24 00:16: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 4faa created at Thu Mar 24 00:15: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 aef2 created at Thu Mar 24 00:04:44 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 a477 created at Thu Mar 24 00:24: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 1aa7 created at Thu Mar 24 00:10: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 37d3 created at Thu Mar 24 00:19: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 d11b created at Thu Mar 24 00:19: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 9346 created at Thu Mar 24 00:10: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 834c created at Thu Mar 24 00:24: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 12a3 created at Thu Mar 24 00:04:44 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 1acd created at Thu Mar 24 00:15: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 153c created at Thu Mar 24 00:16: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 99e7 created at Thu Mar 24 00:03: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 38c1 created at Thu Mar 24 00:04: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 63c3 created at Thu Mar 24 00:19: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 3c80 created at Thu Mar 24 00:21: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 08ea created at Thu Mar 24 00:25: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 f3b3 created at Thu Mar 24 00:06: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 e64f created at Thu Mar 24 00:25: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 9365 created at Thu Mar 24 00:05: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 0264 created at Thu Mar 24 00:06: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 26c4 created at Thu Mar 24 00:30: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 5ca0 created at Thu Mar 24 00:18: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 5f14 created at Thu Mar 24 00:30: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 f8dc created at Thu Mar 24 00:03: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 dc23 created at Thu Mar 24 00:20: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 c885 created at Thu Mar 24 00:03: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 ebee created at Thu Mar 24 00:27: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 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 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 a8d4 created at Wed May 4 11:40:03 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 1745 created at Sat Apr 18 17: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 c165 created at Sat Apr 18 17:02: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 7fd1 created at Tue Oct 6 15:34: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 0eb4 created at Sat Oct 30 09:14:34 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 ccca created at Thu Jul 9 20:53: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 3468 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 ea85 created at Mon Mar 26 09:44:50 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 43b1 created at Mon Nov 4 08:15:36 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 a1fa created at Sun Jul 15 19:25: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 af60 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 aa0d created at Sat Dec 11 01:23: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 6f01 created at Sun May 17 10:12:25 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 1170 created at Fri Mar 27 00:37:30 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 6644 created at Mon Apr 25 21:32: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 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 f282 created at Sun Aug 28 21:17: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 10a6 created at Sun Aug 28 21:17: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 90b1 created at Wed Mar 15 08:09: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 d90d created at Wed Mar 15 08:06: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 273c created at Wed Mar 15 08:06: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 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 e3ad created at Thu Jul 14 06:52: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 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 1248 created at Wed Mar 15 07:55: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 88fb created at Wed Mar 15 08:26: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 2e1f created at Wed Mar 15 08:28: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 3452 created at Wed Mar 15 07:43: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 f604 created at Wed Mar 15 08:15: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 cfff created at Mon Dec 19 00:42: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 a7ba created at Mon Dec 19 00:42: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 f27e created at Thu Mar 24 00:02: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 38d5 created at Sun Feb 26 14:12: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 15c8 created at Sun Feb 26 14:12: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 8287 created at Wed Mar 15 08:06: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 28db created at Wed Mar 15 08:06: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 986f created at Wed Mar 15 07:58: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 f543 created at Wed Mar 15 07: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 e2ea created at Sun Feb 26 14:14: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 71df created at Sun Feb 26 14:14: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 e64c created at Wed Mar 15 08:18: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 8cc8 created at Wed Mar 15 08:18: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 3f2d created at Sat Sep 24 08:35: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 9049 created at Sun Feb 26 13:08: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 f304 created at Sun Feb 26 13:08: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 7f0b 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 2811 created at Sat Sep 24 08:27: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 181c created at Sat Apr 1 23:51: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 6857 created at Sat Apr 1 23:51: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 6fdb 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 6641 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 5523 created at Sun Oct 30 10:51: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 c6a2 created at Sun Oct 30 10:42: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 bb79 created at Sun Oct 30 10:32: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 37ee created at Sun Oct 30 10:16: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 0362 created at Sun Oct 30 10:16: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 0d6e created at Sun Oct 30 10:32: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 6cb1 created at Sun Oct 30 10:42: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 638f created at Sun Oct 30 10:51: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 a88d created at Wed Mar 15 08: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 1686 created at Mon Mar 14 08:43: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 3f2e created at Wed Mar 15 07:50: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 33f9 created at Wed Mar 15 07:41: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 94b9 created at Wed Mar 15 07:56: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 0604 created at Mon May 24 11:14: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 18a8 created at Mon Mar 14 08:43: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 5517 created at Wed Mar 15 08:34: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 3af8 created at Sun Oct 30 10:37: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 26e1 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 f8ec created at Wed Mar 15 08:19: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 210f created at Wed Mar 15 08:19: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 c4d2 created at Wed Mar 15 07:41: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 2a01 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 fc20 created at Sun Apr 10 01:13:44 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 9cfe created at Sun Feb 26 13:07: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 d38c created at Sat Dec 11 01:16: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 c5f0 created at Sun May 22 15:39: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 6c2e created at Wed Mar 15 08:20: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 3e19 created at Wed Mar 15 08:27: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 4e2e created at Wed Mar 15 07: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 3457 created at Sat Apr 1 23:53: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 df67 created at Wed Mar 15 08: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 7497 created at Wed Mar 15 08:36: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 a192 created at Wed Mar 15 07:40: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 0c6e created at Wed Mar 15 07:40: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 3cc5 created at Mon Dec 19 00:15: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 5fcc created at Sun Aug 29 00:16: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 d24b created at Sat Oct 30 10:56: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 4bc2 created at Sat Oct 30 10:56: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 ced5 created at Fri Jun 9 21:02: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 af0c created at Wed Mar 15 07:40: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 9bef created at Sat Sep 24 09:21: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 242b created at Sat Jun 10 23:36: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 1b95 created at Wed Mar 15 08:04: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 8dd8 created at Wed Mar 15 07:44: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 76c4 created at Wed Mar 15 07:59: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 62da created at Wed Mar 15 08:35: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 bb78 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 ef76 created at Sat Sep 24 08:46: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 6aee created at Wed Mar 15 07:51: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 451e created at Wed Mar 15 08:19: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 8b45 created at Wed Mar 15 08:18: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 e5e8 created at Sat Sep 24 09:21: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 790f created at Sat Dec 11 01:18:42 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 2c33 created at Sat Dec 11 01:18:43 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 c823 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 1ea4 created at Sat Apr 1 23:26: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 cc12 created at Sat Aug 28 23:31:43 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 5389 created at Sat Aug 28 23:31:43 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 55f8 created at Wed Mar 15 07:41: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 a5db created at Wed Mar 15 07:44: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 0053 created at Wed Mar 15 07:55: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 348d created at Sun Feb 26 13:06: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 f874 created at Sun Feb 26 13:06: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 5bbe created at Sat Apr 1 23:30: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 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 0e77 created at Sat Sep 24 08: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 fb4c created at Sat Sep 24 08: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 44fe created at Wed Mar 15 08:31: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 e01e created at Wed Mar 15 08:31: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 e7c7 created at Wed Mar 15 08: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 9823 created at Wed Mar 15 08: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 387e created at Wed Mar 15 08:00: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 fc2a created at Sun Apr 10 01:35: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 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 6264 created at Wed Mar 15 08:06: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 a1c8 created at Sun Apr 10 01:34: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 66ca created at Wed Mar 15 08: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 29d7 created at Wed Mar 15 08:25: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 082f created at Wed Mar 15 07:40: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 53e1 created at Mon Apr 25 21:55: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 6a1d 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 6297 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 b33a created at Sat Jul 17 22:41: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 f41d created at Wed Mar 15 08:27: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 c0b4 created at Wed Mar 15 08:40: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 d244 created at Wed Mar 15 07:51: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 bbff created at Wed Mar 15 07:49: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 5726 created at Wed Mar 15 07:54: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 61a3 created at Wed Mar 15 07:54: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 0b1d created at Wed Mar 15 08:02: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 38fb created at Wed Mar 15 08:27: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 bbec created at Wed Mar 15 08:25: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 9f82 created at Wed Mar 15 07:47: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 7ace created at Wed Mar 15 08:38: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 990a created at Wed Mar 15 08:38: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 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 8988 created at Wed Mar 15 07:59: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 025b created at Sun Feb 26 12:29: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 5f24 created at Mon Apr 25 21:38:15 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 51b8 created at Mon Apr 25 21:38: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 f471 created at Mon Apr 25 21:38:15 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 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 752d created at Wed Mar 15 08:26: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 03c7 created at Sun Aug 14 12:06: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 5143 created at Wed Mar 15 08:22: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 36e3 created at Wed Mar 15 08:22: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 f72c created at Sat Jun 10 23:35: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 d5c7 created at Sat Jun 10 23:36: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 2bd1 created at Sun Apr 10 01:09: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 0b7d created at Sat Apr 15 20:02: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 9091 created at Wed Mar 15 08:37: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 2b84 created at Wed Mar 15 08:37: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 e66d created at Sun Oct 30 10:37: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 f063 created at Sun Oct 30 10:37: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 1d39 created at Wed Mar 15 07:49: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 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 9444 created at Wed Mar 15 08:18: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 1d35 created at Sat Apr 1 23: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 12ea created at Sun Aug 14 12:09: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 4620 created at Sun Aug 14 12: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 8bc2 created at Sun Aug 28 21:50: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 79a6 created at Tue Nov 30 00:47: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 a89c created at Wed Mar 15 08:19: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 7178 created at Sun Feb 26 13:07: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 1e1e created at Sat Apr 1 23:53: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 fffc created at Sat Jun 10 20: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 0390 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 122a created at Wed Mar 15 07:59: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 ee33 created at Sun Jan 23 18:00: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 781b created at Sun Jan 23 18:00: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 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 7605 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 195b created at Wed Mar 15 08:18: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 33fd created at Wed Mar 15 08:13: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 166f created at Wed Mar 15 07: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 6314 created at Sun Apr 10 01:25: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 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 495a created at Sat Dec 11 01:05: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 faba created at Sat Dec 11 01:05: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 d00a created at Wed Mar 15 08:28: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 1a69 created at Wed Mar 15 08:40: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 2e04 created at Fri Dec 23 23:46: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 413b created at Wed Mar 15 08:05: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 ea66 created at Wed Mar 15 08:05: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 c9e0 created at Wed Mar 15 07:48: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 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 73de created at Sun Apr 10 01:10: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 6ba4 created at Wed Mar 15 08:00: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 2634 created at Wed Mar 15 08:25: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 d978 created at Sun Apr 10 01:43: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 8943 created at Sat Sep 24 08:17: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 5b78 created at Sat Sep 24 08:17: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 092d created at Wed Mar 15 08: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 ebfc created at Wed Mar 15 07:50: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 7a4c created at Wed Mar 15 08:21: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 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 a2cf created at Sat Dec 11 01:28: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 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 c1f2 created at Sun Feb 26 13:29: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 ec8a created at Sun Feb 26 13:29: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 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 5344 created at Sat Apr 1 23:51: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 5243 created at Sat Apr 1 23:51: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 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 7ef9 created at Wed Sep 13 13:07: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 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 0199 created at Wed Mar 15 08:08: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 6625 created at Wed Mar 15 07:51: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 3918 created at Fri Feb 18 00:19: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 a6c5 created at Fri Feb 18 00:19: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 0652 created at Wed Mar 15 08:37: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 94c0 created at Wed Mar 15 08:34: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 3034 created at Wed Mar 15 08:38: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 066a created at Wed Mar 15 07: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 a103 created at Wed Mar 15 08:30: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 9ed4 created at Wed Mar 15 08:26: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 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 6d4f created at Sat Oct 30 11: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 018e created at Wed Mar 15 08:16: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 786b created at Wed Mar 15 08:16: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 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 9a4e created at Wed Sep 13 13: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 b7aa created at Wed Sep 13 13: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 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 020a created at Sun Mar 14 20:59: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 132b created at Sat Dec 11 01:00: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 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 df30 created at Sun Apr 10 01:30: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 2bfe created at Sun Feb 26 13:37: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 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 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 5aee created at Sat Dec 11 01:37: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 9db0 created at Sat Dec 11 01:37:08 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 d056 created at Sat Jun 10 20:55: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 3b5a created at Wed Mar 15 07:41: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 3bff created at Tue Aug 1 22:05: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 523d created at Thu Mar 24 00:22: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 1982 created at Wed Mar 15 07:51: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 e851 created at Mon Dec 19 00:50: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 3db9 created at Wed Mar 15 08: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 c75e created at Mon May 24 11:14: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 6811 created at Sat Jun 10 22:58: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 c54b created at Sat Jun 10 22:58: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 1b17 created at Wed Mar 15 08: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 f6d3 created at Wed Mar 15 08:36: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 894c created at Tue Aug 1 21:45: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 b1cb created at Wed Mar 15 08:10: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 cff6 created at Wed Mar 15 09:25: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 e949 created at Sun Apr 10 00:18:25 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 5dc4 created at Wed Mar 15 08:20: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 fefe created at Wed Mar 15 07:40: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 992d created at Wed Mar 15 08:12: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 2830 created at Sun Oct 8 12:18: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 86eb created at Sat Apr 1 23:53: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 5784 created at Sun Aug 28 21:50: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 ef95 created at Wed Mar 15 08:18: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 c8bf created at Sat Apr 1 23: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 6500 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 d219 created at Mon Dec 19 00:15: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 1b6e created at Sun May 22 15: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 95e6 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 876e created at Wed Mar 15 08:40: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 6759 created at Wed Mar 15 07:59: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 2d22 created at Sun Feb 26 14:15: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 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 86f3 created at Wed Mar 15 08:04: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 65e7 created at Sun Apr 10 00:21: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 0557 created at Wed Nov 8 00:41: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 7933 created at Wed Nov 8 00:41: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 6288 created at Sat Oct 30 11:13: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 5426 created at Wed Mar 15 07:40: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 ba4e created at Sun Jun 11 00:22: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 793d created at Wed Mar 15 07:54: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 0df8 created at Wed Mar 15 07:54: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 4655 created at Wed Nov 8 00: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 e808 created at Wed Mar 15 07:41: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 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 acc0 created at Sat Aug 28 23:23: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 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 06e5 created at Sat Apr 1 23:26: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 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 b4d6 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 4e72 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 44b3 created at Wed Mar 2 07:09: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 51d9 created at Wed Mar 15 07:49: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 e441 created at Mon Dec 19 00:50: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 cb39 created at Mon Dec 19 00:50: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 a141 created at Sun Dec 18 23:53: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 76ab created at Sun Dec 18 23:53: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 9394 created at Wed Mar 15 07:50: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 2885 created at Wed Mar 15 07:49: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 5586 created at Sun Apr 10 00:28: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 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 39a7 created at Fri Sep 8 10:36: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 2124 created at Sun Jan 23 17:59: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 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 57bc created at Wed Mar 15 07:50: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 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 aeb2 created at Sat Dec 11 01:16: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 2fb5 created at Wed Nov 8 00:26: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 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 f3e6 created at Sun Apr 2 00:26: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 6f86 created at Sun Apr 2 00:25: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 41b8 created at Sun Apr 2 00:26: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 9d8c created at Sun Apr 2 00:25: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 c624 created at Sun Apr 2 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 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 fa9e created at Tue Aug 1 22:46: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 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 1bd7 created at Wed Mar 15 07: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 484c created at Tue Sep 21 00:08: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 d558 created at Tue Sep 21 00:08:18 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 58b6 created at Tue Sep 21 00:08: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 ed44 created at Tue Sep 21 00:08: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 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 04c0 created at Wed Mar 15 08:06: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 dd39 created at Wed Mar 15 07:40: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 f2a7 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 bdfa created at Sat Apr 15 19:59: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 46fb 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 a862 created at Wed Mar 15 08: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 ff96 created at Wed Mar 15 08: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 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 52d1 created at Sat Jun 10 23:08: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 2eb7 created at Sat Jun 10 23:08: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 3429 created at Sun Nov 12 22:50: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 8be2 created at Sun Nov 12 22:50: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 72e0 created at Wed Mar 15 07:41: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 bd81 created at Wed Mar 15 08:14: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 48a9 created at Sun Feb 26 13:38: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 4ec4 created at Sun Feb 26 12:17: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 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 6a94 created at Sun Jun 11 00:06: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 1099 created at Sun Jun 11 00:06: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 eabd created at Wed Mar 15 07:44: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 231b 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 6511 created at Sun Apr 10 00:21: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 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 0dad created at Wed Mar 15 08: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 5dae created at Wed Mar 15 08: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 1f18 created at Sat Apr 1 23:53: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 cb95 created at Sat Oct 30 10:20:59 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 7c42 created at Sat Oct 30 10:20:59 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 c215 created at Wed Dec 20 23:45: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 5bb2 created at Wed Mar 15 08:25: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 0cbe created at Wed Mar 15 08:25: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 fb2f created at Mon Apr 25 21:38: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 0411 created at Sun Apr 10 01:13:44 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 f821 created at Sat Dec 11 01:44: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 1b1c created at Mon Apr 29 21:11: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 47a4 created at Mon Apr 29 21:11: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 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 040f created at Wed Mar 15 07:53: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 9acf created at Sat Sep 24 08:35: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 b670 created at Sat Mar 9 10:30: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 24f8 created at Wed Mar 15 07: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 08f4 created at Wed Mar 15 07:51: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 c7fa created at Wed Mar 15 07:51: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 c645 created at Wed Mar 15 07:59: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 fcfb created at Wed Mar 15 08:19: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 ce1f created at Wed Mar 15 08: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 4064 created at Wed Mar 15 08:17: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 7918 created at Wed Mar 15 08: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 a80a created at Wed Mar 15 07:41: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 134f created at Wed Mar 15 08:09: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 cfef created at Wed Nov 8 00:53: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 472d created at Wed Mar 15 07:47: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 5c30 created at Sun Feb 26 13:55: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 63a8 created at Sun Feb 26 13:55: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 6ada created at Wed Nov 8 00:54: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 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 389e created at Wed Mar 15 08:13: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 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 2b46 created at Fri Jun 21 09:35: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 4252 created at Fri Jun 21 09:35: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 3df0 created at Sun Aug 14 11:36: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 6cd1 created at Sun Aug 14 11:36:25 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 93e9 created at Wed Mar 15 07:55: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 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 5165 created at Fri Jun 21 09:37: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 dff7 created at Sun Aug 14 12:00: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 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 6547 created at Wed Mar 15 08: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 a3e1 created at Wed Mar 15 08:22: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 22fe created at Wed Mar 15 07:47: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 a30b created at Wed Mar 15 08: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 bb89 created at Wed Mar 15 08:38: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 6b8b created at Wed Mar 15 08:19: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 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 1986 created at Wed Mar 15 08:16: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 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 cae4 created at Wed Mar 15 07:48: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 5d81 created at Sat Mar 9 10:12: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 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 7b67 created at Sun Jun 11 00: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 038a created at Sun Jun 11 00: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 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 2585 created at Sun Feb 26 13:45: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 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 6004 created at Wed Mar 15 08:18: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 32db created at Sat Jul 17 22:41: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 726c created at Wed Mar 15 07:47: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 7b06 created at Wed Mar 15 08: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 2410 created at Thu Jun 3 12:06: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 7c83 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 778d created at Mon May 24 11:02: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 ec8f created at Mon May 24 11:02: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 7099 created at Mon May 24 10:25: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 4208 created at Mon May 24 10:25: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 f991 created at Wed Mar 15 08:02: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 9160 created at Wed Mar 15 08:02: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 77d8 created at Wed Mar 15 07:51: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 83f6 created at Wed Mar 15 07:49: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 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 eb98 created at Wed Mar 15 07:42: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: Verifyin |
|