Bug #2049
"Did not match" output
| Status: | New | Start date: | 10/10/2013 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | - | |||
| Target version: | 0.3 | |||
| Component: |
Description
Not sure if this is a bug, but..
Parsing pidgin
"fingerprint" values for "iamironrabbit@gmail.com" did not match:
"37cd1311e19bbf5c21f02c253706ccddf2d77d1e" != "5b209e67b895dfbc5bf3f0ef29ab79a2286d654c"
"fingerprint" values for "nathanfreitas@gmail.com" did not match:
"cec0e53bb142b943d4ceb2ea07d8c5b2463797a0" != "2de32c1f66aead36e3bf93947344c5ba55cacc28"
"fingerprint" values for "nathan@guardianproject.info" did not match:
"0b799387e66cc924b674fe3b985847b4e5eb2088" != "a325d16498f11597c822705097dbc092c7f0b506"
"fingerprint" values for "iamironrabbit@jabber.ccc.de" did not match:
"e5eba35870700014de90ce1594bcf7c82b1aaf90" != "e4696e48e923c40c5dbc8a614f319fddf2da8955"
"fingerprint" values for "nobodyknows@dukgo.com" did not match:
"fa024c964dc9c4169bbcbedb7f28b48765a014ba" != "d56803cf41717be00ec66a98ad5938e341aac2ad"
('', None)
Related issues
History
#1 Updated by hans over 4 years ago
- Target version set to 0.3
That means that keysync found more than one key for a given user id (email address). We have to work out what the correct behavior should be, but its not a bug in terms of how it currently works. It always uses the first key it finds for a given user id.