Format/InPlace.c #12, remove reference in comment to "(likely an MS bug)" - changing this parenthetical should not be counted as canary, but removing it should Changing the published release date from "on " to "in " ģ. rc's language from "English (United States)" to "English (U.S.)" as it was in VC6 Ģ. Compiling with VC2010, and then not manually changing the. I still think that this was not done out of the Devs ownfree will, hackers/authorities/insider or canary, and not just because Win XP ceased to be supported !Īlas, one or more of the TrueCrypt devs (syncon?) have been located and are acting under duress, as a 'canary' previously agreed upon has been published:ġ. Maybe the encryption code was the canary ! You can't even consider it a genuine goodbye present when it does less than than the previous version. They leave a good by and thanks for the support type message. I've seen projects quit before and non produce death-bed releases, especially when not offering anything new and very untested and instantly. Why post 7.2 with 7.1a allows decryption (and is widely tested as reliable/stable) and you will have to have it installed already to of created the containers in the first place ? Why take down old versions and the repositories, but leave a migration message? Recommending Bitlocker over TC also seems very odd, is this hinting that TC 7.2 and possibly older (implied by their statement to migrate away rather than use old versions) is LESS trustworthy than Bitlocker ? I wonder if the reason for abandonment (not matter who instigated it) is around UEFI support ?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |