Skip to content

GitLab

Switch branch/tag
  1. 27 Aug, 2015 1 commit
  3. 23 Aug, 2015 1 commit
  5. 22 Jul, 2015 2 commits
  7. 19 Jul, 2015 1 commit
  9. 16 Jul, 2015 1 commit
  11. 14 Jul, 2015 2 commits
  13. 05 Jul, 2015 2 commits
  15. 04 Jul, 2015 2 commits
  17. 01 Jul, 2015 2 commits
  19. 30 Jun, 2015 2 commits
  21. 27 Jun, 2015 3 commits
    • Juan Batiz-Benet's avatar
      fix swarm notif tests · dae8ff49
      Juan Batiz-Benet authored 
      

they were failing intermittently

License: MIT
Signed-off-by: default avatarJuan Batiz-Benet <juan@benet.ai>
      dae8ff49
    • Juan Batiz-Benet's avatar
      mock: fix notif test · 1cef084e
      Juan Batiz-Benet authored 
      

License: MIT
Signed-off-by: default avatarJuan Batiz-Benet <juan@benet.ai>
      1cef084e
    • Juan Batiz-Benet's avatar
      daemon option to optionally disable secio · 19f33952
      Juan Batiz-Benet authored 
      

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: default avatarJuan Batiz-Benet <juan@benet.ai>
      19f33952
  23. 23 Jun, 2015 3 commits
  25. 01 Jun, 2015 1 commit
  27. 18 May, 2015 1 commit
  29. 12 May, 2015 1 commit
    • Juan Batiz-Benet's avatar
      net/p2p + secio: parallelize crypto handshake · 95198430
      Juan Batiz-Benet authored 
      We had a very nasty problem: handshakes were serial so incoming
dials would wait for each other to finish handshaking. this was
particularly problematic when handshakes hung-- nodes would not
recover quickly. This led to gateways not bootstrapping peers
fast enough.

The approach taken here is to do what crypto/tls does:
defer the handshake until Read/Write[1]. There are a number of
reasons why this is _the right thing to do_:
- it delays handshaking until it is known to be necessary (doing io)
- it "accepts" before the handshake, getting the handshake out of the
  critical path entirely.
- it defers to the user's parallelization of conn handling. users
  must implement this in some way already so use that, instead of
  picking constants surely to be wrong (how many handshakes to run
  in parallel?)

[0] http://golang.org/src/crypto/tls/conn.go#L886
      95198430
  31. 30 Apr, 2015 1 commit
  33. 28 Apr, 2015 1 commit
  35. 20 Apr, 2015 1 commit
    • Juan Batiz-Benet's avatar
      remove debugerrors · b5957350
      Juan Batiz-Benet authored 
      We now consider debugerrors harmful: we've run into cases where
debugerror.Wrap() hid valuable error information (err == io.EOF?).
I've removed them from the main code, but left them in some tests.
Go errors are lacking, but unfortunately, this isn't the solution.

It is possible that debugerros.New or debugerrors.Errorf should
remain still (i.e. only remove debugerrors.Wrap) but we don't use
these errors often enough to keep.
      b5957350
  37. 17 Apr, 2015 1 commit
  39. 12 Apr, 2015 1 commit
  41. 08 Apr, 2015 1 commit
    • Juan Batiz-Benet's avatar
      reuseport: env var to turn it off · 9dbbe6db
      Juan Batiz-Benet authored 
      reuseport is a hack. It is necessary for us to do certain kinds of
tcp nat traversal. Ideally, reuseport would be available in go:

  https://github.com/golang/go/issues/9661

But until that issue is fixed, we're stuck with this. In some cases,
reuseport is strictly a detriment: nodes are not NATed. This commit
introduces an ENV var IPFS_REUSEPORT that can be set to false to
avoid using reuseport entirely:

  IPFS_REUSEPORT=false ipfs daemon

This approach addresses our current need. It could become a config
var if necessary. If reuseport continues to give problems, we should
look into improving it.
      9dbbe6db
  43. 01 Apr, 2015 1 commit
    • Jeromy's avatar
      bandwidth metering on streams · 44309cd5
      Jeromy authored 
      humanize bandwidth output

instrument conn.Conn for bandwidth metrics

add poll command for continuous bandwidth reporting

move bandwidth tracking onto multiaddr net connections

another mild refactor of recording locations

address concerns from PR

lower mock nodes in race test due to increased goroutines per connection
      44309cd5
  45. 31 Mar, 2015 1 commit
  47. 07 Mar, 2015 1 commit
  49. 25 Feb, 2015 1 commit
    • Henry's avatar
      rewrote import paths of go.net/context to use golang.org/x/context · e73da92c
      Henry authored 
      - updated go-ctxgroup and goprocess
ctxgroup: AddChildGroup was changed to AddChild. Used in two files:
- p2p/net/mock/mock_net.go
- routing/dht/dht.go

- updated context from hg repo to git
prev. commit in hg was ad01a6fcc8a19d3a4478c836895ffe883bd2ceab. (context: make parentCancelCtx iterative)
represents commit 84f8955a887232b6308d79c68b8db44f64df455c in git repo

- updated context to master (b6fdb7d8a4ccefede406f8fe0f017fb58265054c)

Aaron Jacobs (2):
net/context: Don't accept a context in the DoSomethingSlow example.
context: Be clear that users must cancel the result of WithCancel.

Andrew Gerrand (1):
go.net: use golang.org/x/... import paths

Bryan C. Mills (1):
net/context: Don't leak goroutines in Done example.

Damien Neil (1):
context: fix removal of cancelled timer contexts from parent

David Symonds (2):
context: Fix WithValue example code.
net: add import comments.

Sameer Ajmani (1):
context: fix TestAllocs to account for ints in interfaces
      e73da92c
  51. 20 Feb, 2015 1 commit
  53. 11 Feb, 2015 1 commit
  55. 10 Feb, 2015 1 commit
  57. 06 Feb, 2015 1 commit
    • Juan Batiz-Benet's avatar
      ratelimiter: fixing rate limiter use · 8a81975c
      Juan Batiz-Benet authored 
      Use of the ratelimiter should be conscious of the ratelimiter's
potential closing. any loops that add work to ratelimiter
should (a) only do so if the rate limiter is not closed,
or (b) prevent limiter while work is added
(i.e. use limiter.Go(addWorkHere))
      8a81975c
  59. 03 Feb, 2015 1 commit