After commiting to the latest version, my *.macaroon files became invalid. I am geting the following error:
verification failed: signature mismatch after caveat verification
I tried to recreate them be deleting *.macaroons & macaroons.db , but no new files are created.
How to force the lnd to recreate all macaroon files with a valid ones?
I think the macaroon files got moved to be under the chain directory.
Earlier all chains used the same macaroons, now each chain can have
separate macaroons.
I got that error too. Then saw some discussion on slack clarifying the
problem.
Hope this helps.
@roasbeef - maybe we can delete the old macaroons to avoid this confusion?
On Sun, 26 Aug 2018, 09:38 PeerName, notifications@github.com wrote:
After commiting to the latest version, my *.macaroon files became invalid.
I am geting the following error:verification failed: signature mismatch after caveat verification
I tried to recreate them be deleting */macaroons & macaroons.db , but no
new files are created.How to force the lnd to recreate all macaroon files with a valid ones?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/lightningnetwork/lnd/issues/1791, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAzoEYFhNDUZ89laJQL_wwvEILL9sHlks5uUlBagaJpZM4WMrw7
.
Thanks, this new path solves my problem.
Where can we keep track of such changes in order to be prepared for them?
@peername I think keeping up with merged PRs and Slack activity is the way to go if you need to stay on latest master. For those who stay on tagged releases these kinds of changes will be documented in the release notes.
@peername slack is probably the best place for up to date info, but @erkarl is right that it would be documented in the release notes.
IIRC, the old ones were not deleted in case users wanted to revert or wanted to the keep them. You may delete them yourself if you don't need them.
Most helpful comment
@peername I think keeping up with merged PRs and Slack activity is the way to go if you need to stay on latest master. For those who stay on tagged releases these kinds of changes will be documented in the release notes.