Re: [Monotone-devel] Mainline DB migration breaks server keys?

[Derek Scherger]

Justin Patrin wrote:
> I haven't been following recent developments too close but just got a
> message to migrate my monotone DB using mainline. After backing up my
> DB I migrated and attempted to pull again. Now I'm getting a message
> about the server key changing:
>
> address@hidden ~/src/net.venge.monotone $ ./mtn pull && ./mtn up
> && make check
> mtn: doing anonymous pull; use -kKEYNAME if you need authentication
> mtn: connecting to monotone.ca
> mtn: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> mtn: @ WARNING: SERVER IDENTIFICATION HAS CHANGED              @
> mtn: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> mtn: IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY
> mtn: it is also possible that the server key has just been changed
> mtn: remote host sent key 3e6f5225bc2fffacbc20c9de37ff2dae1e20892e
> mtn: I expected
> 33653666353232356263326666666163626332306339646533376666326461653165323038393265
> mtn: 'mtn unset known-servers monotone.ca' overrides this check
> mtn: error: server key changed
> address@hidden ~/src/net.venge.monotone $ ./mtn --version
> monotone 0.39 (base revision: c4007197c145794b99ddaa2e6f7e2bc4c014714f)

Quoting Zack from yesterday:

As of rev d24f04c17774410058c7981a18da726748a3156e you don't have to
do that anymore. :-)

We went a little overboard with the binary hashes and tried to use
them for server fingerprints as well.  I've changed it back, because
the space hit is too small to worry about, and it's much better UI -
no need to drop all the variables on upgrade, "ls vars" doesn't dump
garbage to your screen (or need to have a special case for
known-server vars in order not to do that), etc.

So you just caught things at a bad moment.

Cheers,
Derek