Closed gabriel closed 9 years ago
Ah, I think I know, let me check in a workaround. Try it now? (Workaround was in 3c585b0a8b2acf0f11dd30e22594d5afb4b32555)
yep thx!
Sorry about that. It's a a security feature introduced in #123 that wasn't intended to be backwards-compatible with some of the keys we've been generating in the clients. I disabled the check but we should come up with a plan to sunset the old keys. No sense in supporting the old system since it's less secure.
@gabriel in general I might need to make some changes that break our test users. I'll try to batch them all into one DB purge... (Site users aren't using any of these features, so they'll be unaffected.)
oh yeah np! I can regenerate test users easily (and from the client instead of web) and I very very often clear my state as I switch users and stuff so no biggie
Calling
keybase.1.track.track(gbrl27)
:Tried from a few accounts, same error. Looks like sigchain error in gbrl27 (I have a failing github proof on that account.)
I'll try to leave that test account alone.