- 22 Oct, 2014 1 commit
-
- 20 Oct, 2014 2 commits
-
-
Juan Batiz-Benet authored
![](http://m.memegen.com/77n7dk.jpg)
-
Juan Batiz-Benet authored
Now, all peers should be retrieved from the Peerstore, which will construct the peers accordingly. This ensures there's only one peer object per peer (opposite would be bad: things get out sync) cc @whyrusleeping
-
- 19 Oct, 2014 1 commit
-
-
Juan Batiz-Benet authored
It's a patch, really. it's not the full multiconn fix.
-
- 18 Oct, 2014 2 commits
-
-
Juan Batiz-Benet authored
- does end properly - no goroutines leaked!
-
Juan Batiz-Benet authored
-
- 09 Oct, 2014 1 commit
-
-
Juan Batiz-Benet authored
and other logging switches. I kept the u.PErr and u.POut in cli commands, as those do need to write raw output directly.
-
- 08 Oct, 2014 1 commit
-
-
Juan Batiz-Benet authored
- use log.* instead of u.* - use automatic type conversions to .String() (Peer.String() prints nicely, and avoids calling b58 encoding until needed)
-
- 06 Oct, 2014 2 commits
-
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
the u.Hash error can be safely ignored (panic) because multihash only fails from the selection of hash function. If the fn + length are valid, it won't error. cc @whyrusleeping
-
- 05 Oct, 2014 1 commit
-
-
Juan Batiz-Benet authored
This commit fixed the notoriously annoying "Malformed Public Key" problem. The issue was that sometimes the byte representation of the points (x,y in big.Int) generated would be one less byte than expected. This is simply because (* big.Int) Write uses the least amount of bytes needed for the int. I instead changed the marshalling/unmarshalling to do exactly what stdlib crypto/tls does: use `ellipctic.Marshal` which marshals according to the ANSI X9.62 standard. http://golang.org/pkg/crypto/elliptic/#Marshal http://golang.org/src/pkg/crypto/tls/key_agreement.go#L214 ```Go // crypto/tls ka.privateKey, x, y, err = elliptic.GenerateKey(ka.curve, config.rand()) ecdhePublic := elliptic.Marshal(ka.curve, x, y) // ipfs/crypto priv, x, y, err := elliptic.GenerateKey(curve, rand.Reader) pubKey := elliptic.Marshal(curve, x, y) ``` ((Warning: we're using `rand.Reader` directly, which we shouldn't do, as it can be seeded. We should use a configured source, as crypto/tls. Flagged in #143)) This makes me think we should re-use a lot of their datastructures and functions directly (e.g. ecdheKeyAgreement) Fixed: #135 cc @bren2010 @whyrusleeping
-
- 01 Oct, 2014 3 commits
- 27 Sep, 2014 2 commits
-
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
-
- 26 Sep, 2014 1 commit
-
-
Juan Batiz-Benet authored
-
- 23 Sep, 2014 1 commit
-
-
Juan Batiz-Benet authored
-
- 22 Sep, 2014 4 commits
-
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
-
- 13 Sep, 2014 6 commits
-
-
Brian Tiger Chow authored
-
Brian Tiger Chow authored
-
Brian Tiger Chow authored
-
Brian Tiger Chow authored
-
Brian Tiger Chow authored
-
Brian Tiger Chow authored
* handle subroutine errors * further specify the type of channel
-
- 11 Sep, 2014 2 commits
-
-
Siraj Ravel authored
-
Siraj Ravel authored
-
- 10 Sep, 2014 1 commit
-
-
Brian Tiger Chow authored
dependencies are vendored into Godeps/_workspace and commit versions are recorded in Godeps.json update datastore to e89f0511 update go.crypto
-
- 04 Sep, 2014 5 commits
-
-
Brendan Mc authored
-
Brendan Mc authored
-
Brendan Mc authored
-
Brendan Mc authored
-
Brendan Mc authored
-
- 03 Sep, 2014 1 commit
-
-
Jeromy authored
-
- 02 Sep, 2014 3 commits