Re: [Monotone-devel] key mismatch error

[Thomas Keller]

Joe Mason schrieb:
> address@hidden:~$ mtn --key="" --db=metatheme.db pull shorty.advel.cz
> "cz.advel.metatheme*"
> mtn: setting default server to shorty.advel.cz
> mtn: setting default branch include pattern to 'cz.advel.metatheme*'
> mtn: setting default branch exclude pattern to ''
> mtn: doing anonymous pull; use -kKEYNAME if you need authentication
> mtn: connecting to shorty.advel.cz
> mtn: first time connecting to server shorty.advel.cz
> mtn: I'll assume it's really them, but you might want to double-check
> mtn: their key's fingerprint: 73755a6abe40e8a2fb4052f9b90bf3a074e6f98a
> mtn: warning: key 'address@hidden' is not equal to key
> 'address@hidden' in database
> mtn: fatal: std::logic_error: netsync.cc:1,296: invariant
> 'I(app.db.public_key_exists(their_key_hash))' violated
> mtn: this is almost certainly a bug in monotone.
> mtn: please send this error message, the output of 'mtn --full-version',
> mtn: and a description of what you were doing to address@hidden
> mtn: failed to write debugging log to /home/jnc/.monotone/dump
>
> I'm using the Ubuntu package, 0.35-2ubuntu2, and I had no .monotone
> directory, which is why the dump failed.  I ran it again to get a dump
> file, which I've attached.  I've also attached the key that caused the
> problem.
>
> The project hasn't been updated since 2005, so maybe their server is
> out of date or something, but I thought I should report this anyway.

The problem here is that the server key you explicitely read in before 
you pulled from their server doesn't match the key which is sent to you:

Download file:

[pubkey address@hidden
MIGdMA0GCSqGSIb3DQEBAQUAA4GLADCBhwKBgQC3bQwy5T7JLf0E2IXCQisZvlrVN7IQAyWE
89gYdiBNiBUVPpm6E+1flOKyrjtlzu1gjQmDxTtPpmaLCHwQxeU0bvyF/XWMjl3qWy+s6T86
NoS4zTSFSFykSruONO7ZU6ZePPRgToYZjlcR8IOtn74+xVBf90fbHtFhTJkPW8BfCQIBEQ==
[end]


Send with pull:

[pubkey address@hidden
MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDTXwPHoiqH09y6Yc37/ckMNpmeW6ePO1bZ
hc95erIjqhyU2CDYmWXN8l+pJQrGVStcpvPYYDsUo/XJ7oSy7/qFXqZVJDczduLlERhOcUGe
Yzj5HhDgJ/p6b05ZIm7ar9wdvpvp55YYCf4m9fMWFUxB75LItyORI5MECHH/oJASZwIDAQAB
[end]

though both have the same key id. If you leave out the mtn read step, 
the pull should succeed.
In general its problematic to re-use key IDs in monotone, but people 
tend to lost their private keys and think its safe to just re-create a 
new one with the same ID.

I'll shortly commit a patch which gives the user a better error message 
and some guidance how to proceed (in your case you might just want to 
use mtn dropkey to drop the manually added key and pull again).

Thomas.

--
GPG-Key 0x160D1092 | address@hidden | http://thomaskeller.biz
Please note that according to the EU law on data retention, information
on every electronic information exchange might be retained for a period
of six months or longer: http://www.vorratsdatenspeicherung.de/?lang=en

signature.asc
Description: OpenPGP digital signature