Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: ipfs/kubo
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 9618b6ddc7e7^
Choose a base ref
...
head repository: ipfs/kubo
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 756166a4b05c
Choose a head ref
  • 2 commits
  • 4 files changed
  • 1 contributor

Commits on Jun 19, 2015

  1. daemon option to optionally disable secio

    This commit adds an option to turn off all encryption. This is a mode
    used for tests, debugging, achieving protocol implementation interop,
    learning about how the protocol works (nc ftw), and worst case
    networks which _demand_ to be able to snoop on all the traffic.
    (sadly, there are some private intranets like this...). (We should
    consider at least _signing_ all this traffic.)
    
    Because of the severity of this sort of thing, this is an
    all-or-nothing deal. Either encryption is ON or OFF _fully_.
    This way, partially unencrypted nodes cannot be accidentally left
    running without the user's understanding. Nodes without encrypted
    connections will simply not be able to speak to any of the global
    bootstrap nodes, or anybody in the public network.
    
    License: MIT
    Signed-off-by: Juan Batiz-Benet <juan@benet.ai>
    jbenet committed Jun 19, 2015
    Copy the full SHA
    9618b6d View commit details
  2. daemon output includes swarm addresses

    daemon output now includes initial swarm addresses. this is not a
    full solution, as a change in network will not trigger re-printing.
    We need a good way to do that.
    
    This made me re-think how we're outputting these messages, perhaps
    we should be throwing them as log.Events, and capturing some with
    a special keyword to output to the user on stdout. Things like
    network addresses being rebound, NATs being holepunched, external
    network addresses being figured out, connections established, etc
    may be valuable events to show the user. Of course, these should be
    very few, as a noisy daemon is an annoying daemon.
    
    License: MIT
    Signed-off-by: Juan Batiz-Benet <juan@benet.ai>
    jbenet committed Jun 19, 2015
    Copy the full SHA
    756166a View commit details
Loading