- 16 Nov, 2015 1 commit
-
-
Jeromy authored
-
- 15 Nov, 2015 1 commit
-
-
Jeromy authored
-
- 12 Nov, 2015 1 commit
-
-
Jeromy authored
-
- 30 Sep, 2015 2 commits
-
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
-
- 27 Jun, 2015 1 commit
-
-
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: Juan Batiz-Benet <juan@benet.ai>
-
- 20 Apr, 2015 1 commit
-
-
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.
-
- 08 Apr, 2015 1 commit
-
-
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.
-
- 01 Apr, 2015 1 commit
-
-
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
-
- 31 Mar, 2015 1 commit
-
-
Ho-Sheng Hsiao authored
- Modified Godeps/Godeps.json by hand - [TEST] Updated welcome docs hash to sharness - [TEST] Updated contact doc - [TEST] disabled breaking test (t0080-repo refs local)
-
- 25 Feb, 2015 1 commit
-
-
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
-
- 11 Feb, 2015 1 commit
-
-
Juan Batiz-Benet authored
We were half-way with this. there's no way for net.Dialers to respect contexts, so we have to let the dial finish in the background.
-
- 10 Feb, 2015 1 commit
-
-
Juan Batiz-Benet authored
thanks @whyrusleeping for finding these.
-
- 28 Jan, 2015 2 commits
-
-
Juan Batiz-Benet authored
+ fixed race
-
Juan Batiz-Benet authored
-
- 27 Jan, 2015 1 commit
-
-
Juan Batiz-Benet authored
This commit turns all dial logs into log.Events. Everything's great except for one problem: The LoggableMap I'm using does not print out things correctly. I gave it peer.IDs, and Multiaddrs and both got logged as nothing `{}` (didn't even call their String() methods!) So, for now, this function encodes it when called... This is wrong and should be fixed before being merged in. Otherwise we will be constantly encoding peer.IDs and Multiaddrs without needing to. @briantigerchow how do you suggest doing this? I don't know my way around your Loggable.
-
- 26 Jan, 2015 1 commit
-
-
Juan Batiz-Benet authored
should be returning false.
-
- 24 Jan, 2015 1 commit
-
-
Juan Batiz-Benet authored
-
- 23 Jan, 2015 2 commits
-
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
-
- 21 Jan, 2015 1 commit
-
-
Juan Batiz-Benet authored
-
- 20 Jan, 2015 3 commits
-
-
Juan Batiz-Benet authored
This commit cleans up the reuse port setup, and fixes a problem: make sure to filter addrs out that we simply cannot dial with (e.g. loopback -> non-loopback, or linklocal -> nonlinklocal)
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
-
- 13 Jan, 2015 1 commit
-
-
Juan Batiz-Benet authored
-
- 11 Jan, 2015 1 commit
-
-
Juan Batiz-Benet authored
-
- 09 Jan, 2015 1 commit
-
-
Juan Batiz-Benet authored
-
- 02 Jan, 2015 1 commit
-
-
Juan Batiz-Benet authored
The net package is the next to move. It will be massaged a bit still to fix the Network / "NetworkBackend" conflict.
-