Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

addressing: Specify security protocols in multiaddr #353

Open
wants to merge 13 commits into
base: master
Choose a base branch
from

Commits on Jul 25, 2021

  1. Configuration menu
    Copy the full SHA
    b6d4ff4 View commit details
    Browse the repository at this point in the history

Commits on Jul 26, 2021

  1. apply @mxinden's suggestions from code review

    Co-authored-by: Max Inden <mail@max-inden.de>
    marten-seemann and mxinden authored Jul 26, 2021
    Configuration menu
    Copy the full SHA
    13fa147 View commit details
    Browse the repository at this point in the history
  2. add missing 'not'

    marten-seemann committed Jul 26, 2021
    Configuration menu
    Copy the full SHA
    35ccd7c View commit details
    Browse the repository at this point in the history
  3. add paragraph about hard-coded multiaddrs

    Co-authored-by: Max Inden <mail@max-inden.de>
    marten-seemann and mxinden authored Jul 26, 2021
    Configuration menu
    Copy the full SHA
    c8b3b09 View commit details
    Browse the repository at this point in the history

Commits on Jul 27, 2021

  1. Configuration menu
    Copy the full SHA
    85f80ca View commit details
    Browse the repository at this point in the history

Commits on Aug 12, 2021

  1. Configuration menu
    Copy the full SHA
    c01af99 View commit details
    Browse the repository at this point in the history

Commits on Aug 30, 2021

  1. Configuration menu
    Copy the full SHA
    6d8004e View commit details
    Browse the repository at this point in the history

Commits on Oct 4, 2021

  1. Configuration menu
    Copy the full SHA
    3c1487a View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    90bef6f View commit details
    Browse the repository at this point in the history
  3. relay/circuit-v2: Fix misconception on passive relaying

    When using passive relaying, there is no need for the initiator to
    include multiple addresses in the `peer` field of the `HopMessage`.
    mxinden committed Oct 4, 2021
    Configuration menu
    Copy the full SHA
    4de35ef View commit details
    Browse the repository at this point in the history

Commits on Oct 29, 2021

  1. Configuration menu
    Copy the full SHA
    8807a12 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    bb3c4f9 View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    128e76d View commit details
    Browse the repository at this point in the history