This project has moved. For the latest updates, please go here.

CAUTION: VeraCrypt warrant Canary has expired

Topics: Users Discussion
Feb 3, 2016 at 3:49 PM
The last posted notice was dated January 24, 2016 - containing a pledge to update no later than January 31.

That was 3 days ago.

I am not making any conclusions; just posting the facts as I see them.
Feb 4, 2016 at 2:54 AM
Sang41 is correct, the last Canary is dated Jan. 24,2016, and was supposed to be updated no later than Jan. 31. Today is Feb. 3 where I am.

Unless the Canary is updated soon, with an explanation for the delay, I'll need to rethink using Veracrypt.
Coordinator
Feb 4, 2016 at 1:22 PM
Actually, there was a mistake in the canary text: it should have read "end of February" instead of "end of January". When updating the canary, I focused on the signing date but forgot to update the next signing date.

The canary is published once a month, around 24 of every month. Last one is 24 January and next one is supposed to be around 24 February.

I have corrected the canary to avoid any confusion: it was signed today.

Sorry for this mistake. I'll be more careful next time but updating both date fields but the canary signing schedule will remain the same: once a month around 24th.

PS: I always manually update the text to avoid any compromise of any tool that I may use.