Wiktor Kwapisiewicz 0099c373d2
Fix reading signersUserId packet in signatures
This bug caused all signersUserIds strings to be prefixed with `"null"`
string. Changed to use only the last value for this packet type.

Previous implementation probably assumed that there will be more than one
signersUserId packet but I haven't been able to generate such signature
using gpg (only last user id was embedded). Moreover signature
serialization function `write_all_sub_packets` writes only one value of
this packet as a UTF-8 string.
2018-06-27 12:17:19 +02:00
..
2018-02-13 23:33:09 +01:00
2018-02-13 23:33:09 +01:00
2018-05-29 21:21:24 +02:00
2018-05-03 13:04:32 +02:00
2018-02-13 23:33:09 +01:00
2018-03-01 11:35:16 -08:00
2018-05-29 09:55:47 +02:00
2018-05-29 21:21:24 +02:00