hank
commented
10 years ago Oh. This is caused by the date associated with the private key being older than a certain date, since the app assumes it created the address. If you set the date to today's date and get the formatting just right (just dump a backup to see it), it should get rid of the warning. Cheers.
On Tue, Dec 17, 2013 at 10:08 PM, GottaGetmedat notifications@github.comwrote:
I imported a private key that was generated via FTCVanity and it reports that it has the vulnerability issue (on restart). I've attempted to make a comment to them there about it and I think it's their fault, but I thought I'd let people here hear about it and maybe assess the source of the problem, because it could I thought be a mistake here. I used the latest OpenSSL to encrypt/decrypt the Import/Export PrivKeys from here, in which it explains the problem and that that version it is resolved in, so it's likely not from OpenSSL. At least deleting these bogus private keys (addresses) should be possible, or importing the original backup wallet (over yet another one) would avoid reinstalling the app and rebuilding the entire data stream again etc.
— Reply to this email directly or view it on GitHubhttps://github.com/hank/feathercoin-wallet/issues/6 .
I imported a private key that was generated via FTCVanity and it reports that it has the vulnerability issue (on restart). I've attempted to make a comment to them there about it and I think it's their fault, but I thought I'd let people here hear about it and maybe assess the source of the problem, because it could I thought be a mistake here. I used the latest OpenSSL to encrypt/decrypt the Import/Export PrivKeys from here, in which it explains the problem and that that version it is resolved in, so it's likely not from OpenSSL. At least deleting these bogus private keys (addresses) should be possible, or importing the original backup wallet (over yet another one) would avoid reinstalling the app and rebuilding the entire data stream again etc.