Live data from Hacker News

Viewing profile — lotharrr

lotharrr

HN member
Joined
Wed, Sep 18, 2013, 7:00 PM UTC
HN karma
462
Public activity
79 items

About lotharrr

Brian Warner

Recent public activity

  1. comment
    Comment #45494200

    FYI, there's a subcommand just for this use case: `wormhole ssh invite` / `accept`, which will read the SSH pubkey on one end and append it to authorized_keys on the other.

  2. comment
    Comment #45494157

    We're making good progress on hole-punching, but it isn't available yet. Once complete, that should take some pressure/cost off the transit relay machine. Note that the transit rel…

  3. comment
    Comment #45494110

    (author here) Both sides connect to the "mailbox relay server" to perform key exchange and setup. That's a host named "relay.magic-wormhole.io". If either side has a public IP addr…

  4. comment
    Comment #45494052

    (magic-wormhole author here) Debian was kind enough to configure their distribution's copy with a distinct hostname for the transit relay helper (the bit that forwards bulk encrypt…

  5. comment
    Comment #43474057

    I've been pretty happy with Unifi's "In-Wall" AP (e.g. https://store.ui.com/us/en/category/wifi-wall/products/u6-iw ): PoE powered, has four downstream RJ45 ports (one with PoE its…

  6. comment
    Comment #43345660

    One tricky constraint is that a "simple URL" isn't big enough to hold a full-entropy encryption key. So your security must either come from PAKE (like magic-wormhole and friends), …

  7. comment
    Comment #41288123

    WebRTC (and the various hole-punching techniques listed elsewhere here) have mechanisms to help with most cases of both participants living behind NAT boxes. The remaining cases re…

  8. comment
    Comment #41284134

    Nope. It needs to contact the "mailbox server" to coordinate the rest of the protocol. Two machines with local connectivity (e.g. on the same LAN, but your WAN connection is broken…

  9. comment
    Comment #41284078

    Correct. The wormhole code is a channel number (called a "nameplate") and a short secret, which defaults to 16 bits of entropy. The secret is used as the input to a PAKE, which onl…

  10. comment
    Comment #41280321

    The PAKE algorithm lets you spend an interactive roundtrip to buy a full-strength key out of a weak shared secret. An attacker can attempt to guess the passphrase, and their chance…

  11. comment
    Comment #41280310

    I don't know of one yet, but I tried to choose protocols (websockets) that were friendly to being hosted in a browser, or a browser plugin. The exception is the bulk-transfer proto…

  12. comment
    Comment #41278914

    Magic-wormhole is really intended to help with the first-step "introduction" phase of a tool like that: start with two humans that can yell a codephase at each other, and finish wi…

  13. comment
    Comment #41278815

    It can't hurt, but it shouldn't be necessary. The client-side software establishes an encrypted connection with its peer, using an encryption scheme that should be just as secure […

  14. comment
    Comment #41278689

    Mostly no. ssh/rsync is compiled C code, so might be slightly faster than a Python-based `wormhole`, if you have a really fast connection to take advantage of. And rsync provides t…

  15. comment
    Comment #41278642

    There's a `wormhole send --text BLOB`, which doesn't bother with a bulk-data "transit" connection, and just drops a chunk of text on the receiving side's stdout. You can also impor…

  16. comment
    Comment #41278629

    Not really.. the closest approximation would be if both sides set their `--transit-helper` to an unusable port like `tcp:localhost:9`. That would effectively remove the relay helpe…

  17. comment
    Comment #41277826

    Alas no. It's a one-shot file-transfer tool, and we don't store a copy of the encrypted data or anything. So the sender must stay running until the receiver has finished downloadin…

  18. comment
    Comment #41277763

    None that I know of. It just uses a TCP connection to the mailbox server (with keepalives), and then TCP connections for the bulk-transfer transit phase, so I can't think of anythi…

  19. comment
    Comment #41277716

    Yes, it relies on two servers, both of which I run. All connections use the "mailbox server", to exchange short messages, which are used to do the cryptographic negotiation, and th…

  20. comment
    Comment #41277656

    Not yet. The "Dilation" protocol (which is about 80% implemented) is intended to support WebRTC as a transport layer. IIRC it requires a public server to tell you about your extern…

  21. comment
    Comment #41277551

    scp/rsync are great tools, but they require pre-coordination of keys. One side is the client, the other is the server. The client needs an account on the server machine (so the hum…

  22. comment
    Comment #41277253

    There are two servers. The "mailbox server" helps with handshakes and metadata transfers, and is super-low bandwidth, a few hundred bytes per connection. The "transit relay helper"…

  23. comment
    Comment #41277054

    Yeah, syncthing is awesome for repeated interaction.. once you've configured the two sides to know about each other, it's really flexible for doing an initial transfer, pushing jus…

  24. comment
    Comment #41276886

    author here.. happy to answer any questions!

  25. comment
    Comment #41276814

    (author here) The protocol enumerates all the IPv4 addresses on each side, and attempts to connect to all of them, and the first successful handshake wins. So if your VPN arrangeme…