• Breaking News

    Sunday, December 31, 2017

    Cryptography TrueCrypt vs VeryCrypt?

    Cryptography TrueCrypt vs VeryCrypt?


    TrueCrypt vs VeryCrypt?

    Posted: 30 Dec 2017 01:26 PM PST

    Not looking to beat a dead horse here...but for simple everyday purposes (protecting a USB drive in case it's lost, using a container in case a laptop is stolen, etc.)...is TrueCrypt still acceptable? I know it's been years since they abandoned it, but from my understanding the actual encryption and implementation is still sound.

    Everyone seems to have jumped over to VeraCrypt, but I'm a bit leery. TrueCrypt passed a major audit without any major issues, was recommended by many security/computer experts and was even recommended by colleges and universities for their professors/students to use. VeraCrypt doesn't seem to really have any of that from what I have seen?

    I'm not looking for a battle here, just thoughts on whether a switch to VeraCrypt would be a good idea (and any benefits of it) or whether sticking with TrueCrypt would be acceptable for normal everyday purposes where the main threat is a device being lost/stolen?

    submitted by /u/bill422
    [link] [comments]

    visualise operations on the secp256k1 (bitcoin) elliptic curve

    Posted: 30 Dec 2017 08:47 AM PST

    What are the current viable options for a good proof of work algorithm?

    Posted: 30 Dec 2017 08:30 AM PST

    NOTE: This isn't about cryptocurrencies.

    So say I host a public service and I don't want to be DoSed. What mitigations can I use? Ideally I just would rate limit or just block those IPs, but I'm toying with the idea of using a challenge-response scenario.

    I'm thinking I'd just go with a simple challenge text and then hash response, or maybe even add additional work using partial hash inversion for difficulty adjustment. The difficulty adjustment is to account for future increase in computing power rather than amount of work verification like what Bitcoin does.

    Are there any other options even though they might be riskier? Like Cuckoo cycle? Something like this [PDF]?

    I'm not really aiming for 'ASIC-resistance' or something like that, so it being memory hard isn't a requirement either.

    What I want is a very fast verification no matter the how much the proof of work for client has been ramped up.

    submitted by /u/keepthethreadalive
    [link] [comments]

    Please help review my password manager database format!

    Posted: 30 Dec 2017 12:39 PM PST

    No comments:

    Post a Comment