• Breaking News

    Thursday, February 1, 2018

    Home Unlabelled Cryptography Discontinue support for weak cryptographic standards

    Cryptography Discontinue support for weak cryptographic standards

    February 01, 2018

    Cryptography Discontinue support for weak cryptographic standards

    Discontinue support for weak cryptographic standards

    Posted: 31 Jan 2018 02:11 PM PST

    So my professor started to go into what are called "private keys" and "public keys" in class, but I'm still confused on the concept

    Posted: 31 Jan 2018 07:05 AM PST

    He started by making us go on Amazon, right clicking the secure icon in the address bar, and showing us the public key, which was just a bunch of pairs of letters and numbers. He then said that we can send secure and encrypted e-mails by basically doing this: Sally wants to send a message to her boyfriend John. Sally would encrypt the message with Sallys private key. She would also encrypt it with John's public key. Then she would send the message. If John wanted to reply, he would use his private key and also encrypt it with Sallys public key. And this would continue on.

    But here's what I'm confused on: How are they getting these keys in the first place? And how would John be able to get Sallys encrypted private key when he gets her message the first time?

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

    Is There a Encryption Algorithm that Allows for 2 Passwords with Two Different Outputs?

    Posted: 31 Jan 2018 05:47 PM PST

    Been scouring the interwebs for information. Can't find anything that'll work for what I want.

    I am very new to cryptography, so please ELI5.

    I am making a program that uses a single encrypted phrase to store two pieces of information at once, and I've hit a roadblock: I know nothing about cryptography!!! What I want to happen and when you decrypt with Password A, you get Message A, and when you decrypt with Password B, you get Message B.

    Password would be user chosen, so no random numbers generated by the algorithm. Then, I have two pre-determined, NON CHANGEABLE numbers, which in my case I have a "Message A" (0x58f77e33275549) and "Message B" (0x5ac34). There will be a different Message for every person, because they are a UUID in a sense, so this has to work on a mass scale, so it can't be rng that the numbers will line up so it works.

    What I want to happen is when I decrypt with Password A, I want to get Message A, and when I decrypt with Password B, I want to get Message B.

    The encryption method also can't be based on pure chance, because

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

    Which platform / chain do you guys think is best for bloackchain based content delivery?

    Posted: 01 Feb 2018 01:57 AM PST

    real-world examples of when disregarding Kerckhoffs' principle resulted in disaster?

    Posted: 31 Jan 2018 07:06 PM PST

    just started taking a crypto course and learned about the idea of security relying solely on the private key while the encryption scheme is made publicly available since peer reviewed schemes are likely to be stronger than any scheme an individual designer could create

    are there any examples of perhaps a company deciding to ignore this principle by creating their own encryption scheme just to have it blow up in their faces?

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

    Is there an OTP protocol for packet exchange following physical handshake?

    Posted: 31 Jan 2018 03:00 PM PST

    Suppose you are performing a physical handshake where an arbitrary amount of data can be exchanged. The goal is to establish an information theoretic secure communication channel for as much data as the entropy exchanged permits.

    Both participants have an entropy source.

    Is there an established or researched protocol for this?

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

    Practical Implementation of Canetti-Halevi-Katz Forward Secure PKE

    Posted: 31 Jan 2018 10:36 AM PST
    Read more
    at

    No comments:

    Post a Comment