• Breaking News

    Wednesday, April 24, 2019

    Home Unlabelled Cryptography NIST Lightweight Crypto Standardization - Round 1 Candidates

    Cryptography NIST Lightweight Crypto Standardization - Round 1 Candidates

    April 24, 2019

    Cryptography NIST Lightweight Crypto Standardization - Round 1 Candidates

    NIST Lightweight Crypto Standardization - Round 1 Candidates

    Posted: 23 Apr 2019 06:38 PM PDT

    You discover polynomial time factoring algorithm

    Posted: 23 Apr 2019 04:51 AM PDT

    What would you do? What implication could it have on society? Would Ec still be safe? Would you be safe ?

    Post here factors of RSA challenge number to prove ?

    Contact university, TV, NSA, sell it to underground ?

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

    PGP.to — A way to (opportunistically) shorten your public key

    Posted: 23 Apr 2019 11:29 AM PDT

    If you open https://pgp.to/#0x5200DF38, you will be redirected to a key server (currently Ubuntu; might adopt others or build my own) with "0x5200DF38" as the search criteria.

    As for https://pgp.to/#neruthes, you will see all public keys which are named after "Neruthes".

    This might be useful for length-sensitive scenarios like printing QR code on business cards — I do wonder would anyone (besides myself) really print QR for public key on business cards.

    Try it out: https://pgp.to/

    (Actually the jump link can include the full 40-digit hex fingerprint; I just have not figured out how to support both lengths in the input box.)

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

    digital signature - key exchange - asychronical en/decryption

    Posted: 23 Apr 2019 08:30 AM PDT

    Hi, I am currently studying for CCNA security and I wonder how encrypting/decryption using a pair of public and private keys works?

    When creating a digital signature, a hash for some data that will be sent is generated first. This hash is then encrypted using a private key.

    Then the data is sent together with the encrypted hash. The recipient first decrypts the encrypted hash (that is attached to the data) using the senders public key.
    Question: how is the decryption using the public key done? The keys are different but the result of the decrypted hash must be the same? How does this work?
    I would understand it if the encryption/decryption is synchronical, using the same keys, but how does it work using two different keys in asynchronical?

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

    Any thoughts on ZK-STARKs as a way to create quantum resistance?

    Posted: 23 Apr 2019 08:00 AM PDT

    ZK-STARKs is being mentioned here and there as an replacement for current signature schemes. (For example the blockchain Ethereum is planning to use ZK-STARKs) Amongst other things it is said to make the blockchian quantum resistant.

    submitted by /u/Dezeyay
    [link] [comments]
    Read more
    at

    No comments:

    Post a Comment