Skip to content
Snippets Groups Projects
  1. Sep 07, 2016
  2. Sep 06, 2016
  3. Sep 05, 2016
  4. Sep 02, 2016
  5. Sep 01, 2016
  6. Aug 31, 2016
  7. Aug 30, 2016
    • akwizgran's avatar
      Merge branch '494-implement-backend-for-reblogging-and-blog-comments' into 'master' · d8a9d83c
      akwizgran authored
      Add support for comments and reblogging to Blog Client
      
      Comments and reblogs need to depend on the post they refer to.
      Since message dependencies are limited to one group,
      the post and also the comments need to be wrapped
      when commented on or reblogged to another blog (and group).
      
      For this reason, in addition to comments, two new wrapping message types
      are introduced. They retain all data of the original messages and allow
      for reconstruction and signature verification.
      
      This MR breaks backwards compatibility with old blog posts.
      It removes the content type, title and parent ID from the post.
      
      Furthermore, it includes one commit that replaces the `Message` in `MessageSharedEvent` with a `MessageId`.
      
      Closes #494
      
      See merge request !285
      d8a9d83c
    • akwizgran's avatar
      Merge branch '364-introduction-responses-should-be-signed' into 'master' · 70a44e8a
      akwizgran authored
      Sign Introduction Information to be able to discover MITM attack
      
      The local introducee doesn't know whether each piece of information received from the introducer originates from the remote introducee or has been replaced by the introducer, i.e. whether the introducer is carrying out a man-in-the-middle attack.
      
      The introduction protocol doesn't aim to detect or prevent man-in-the-middle attacks. We only aim to establish that if the remote identity public key is not replaced then the remote ephemeral public key, transport properties and timestamp are not replaced either. This MR adds a MAC and a signature to the introduction protocol's ACK message to fulfill that aim. See #364 for the detailed security argument.
      
      Later, when the local introducee verifies that the remote identity public key belongs to a particular person (#513), she can also be sure that the remote ephemeral public key, transport properties and timestamp originated from that person.
      
      Closes #364
      
      See merge request !297
      70a44e8a
Loading