This issue has reappeared in launcher version 1.2.7 (issue didn't exist with version 1.2.5). Also, I'm going to toss this in here because I don't know where else to put it, but the launcher download webpage <http://minecraft.net/download> has the wrong date for the launcher's release...so if/when someone is doing what they should (double-checking the download of an unsigned executable that is presenting warnings), they then encounter an inconsistency between what the downloaded executable's created date is and the webpage's claim of what it should be.
Lon R. Stockton, Jr.
This issue has reappeared in launcher version 1.2.7 (issue didn't exist with version 1.2.5). Also, I'm going to toss this in here because I don't know where else to put it, but the launcher download webpage <http://minecraft.net/download> has the wrong date for the launcher's release...so if/when someone is doing what they should (double-checking the download of an unsigned executable that is presenting warnings), they then encounter an inconsistency between what the downloaded executable's created date is and the webpage's claim of what it should be.