Live data from Hacker News

Viewing profile — weavenetwork

weavenetwork

HN member
Joined
Tue, Sep 09, 2014, 9:26 AM UTC
HN karma
117
Public activity
44 items

About weavenetwork

No profile information was provided.

Recent public activity

  1. comment
    Comment #9515941

    Thanks @takeda. Are you aware that we did not roll our own crypto? Instead we used the NaCl crypto libs[1]. Weave adds about 300 LOC to integrate NaCl. You can read about it here -…

  2. comment
    Comment #9510877

    What about them? Would you recommend one of them over the others?

  3. comment
    Comment #9510239

    I'll have to stop saying please when in the US then ;-) But seriously, thanks for taking the time to explain your point of view. alexis.

  4. comment
    Comment #9504452

    cripes. on each host? what kind of physical network are you using, and how many containers per host? how many hosts? let me know if I should email about this instead.

  5. comment
    Comment #9504223

    What throughput do you need, on a per-host basis?

  6. comment
    Comment #9504098

    We are open to recommendations, help and overall insight from expert contributors in security. As many people on this thread have pointed out, it is a big and complex world..

  7. comment
    Comment #9504092

    We did not roll our own crypto. We used NaCl. The rationale is explained here - http://weaveworks.github.io/weave/how-it-works.html#crypto We agree that other approaches are possib…

  8. comment
    Comment #9504085

    No, for example it is 100% uncharitable and unreasonble to assert that "please" is sarcastic. The truth is quite the opposite.

  9. comment
    Comment #9504081

    Paul, I think our work is good. We thought about our approach very carefully.. And we have built systems like this before. The main difficulty is to combine moving fast with limite…

  10. comment
    Comment #9501561

    Complaining on twitter is not the same as finding an issue! Criticism has value, but not all commentary deserves equal weight or time before it is reasonable to request reciprocal …

  11. comment
    Comment #9501554

    indeed. at the risk of entering tinfoil hat land, note the following http://blog.cryptographyengineering.com/2014/12/on-new-snowd... ..although also the not 100% reassuring https:/…

  12. comment
    Comment #9501298

    although, sometimes not obviously so: https://github.com/GoogleCloudPlatform/kubernetes/pull/4483#...

  13. comment
    Comment #9501246

    Tony, the team recently updated the crypto docs to clarify the rationale etc etc - http://weaveworks.github.io/weave/how-it-works.html#crypto ... Moreover the entire crypto code fo…

  14. comment
    Comment #9501021

    Using an account that I share with other people in the same team is not the same as 'marketing'. I am sorry if this somehow offends, but think of the handle as just one poster.

  15. comment
    Comment #9501003

    edit: here is a kubernetes link: https://github.com/GoogleCloudPlatform/kubernetes/pull/4483#... the author, who was part of the MS Azure team at the time, said: "as of today, this…

  16. comment
    Comment #9500966

    True. We did try ipsec, and couldn't find an implementation that was oss, demonstrably safe, and easy enough to pull into a first release. As weave matures, we'd love to work with …

  17. comment
    Comment #9500944

    I'm sorry but I find your interpretations of 1-4 completely uncharitable and unreasonable.

  18. comment
    Comment #9500261

    I don't think anyone meant, or said, "fuck you". Why are you even implying such a thing? Ultimately we can't work on even a fraction of the features that every person wants, and La…

  19. comment
    Comment #9500241

    as laurie mentions in his article, you can easily use off the shelf security solutions with weave... the point of the current crypto is to provide something basic that works. we ch…

  20. comment
    Comment #9500219

    You can of course use etcd with weave... indeed weave can be run with no dependencies, so it may make sense as a way to bootstrap etcd ;-)

  21. comment
    Comment #9500209

    I haven't seen those used in the wild yet, but fwiw, weave is working on a 'fast data path' that uses the same kernel path as ovs

  22. comment
    Comment #9500201

    I should add that one way to get more throughput is to use more than one CPU.

  23. comment
    Comment #9500197

    yes, microseconds surely - we estimate that the cost of switching from kernel to user space, and back again, several times, adds up to 2-300 microseconds. in return for this, you g…

  24. comment
    Comment #9499994

    I'm not sure why you think so, but fwiw, irl, I am alexis at weave dot works

  25. comment
    Comment #9499983

    Correct! Once upon a time people said Amazon cloud was too slow. Then they said it wasn't suitable for large workloads. Then they said it did not make money ... etc etc. I'm not sa…