Live data from Hacker News

Viewing profile — jamiesonbecker

jamiesonbecker

HN member
Joined
Wed, Aug 22, 2018, 12:59 AM UTC
HN karma
443
Public activity
213 items

About jamiesonbecker

CEO at userify.com (innovative SSH key management, self-hosted and saas)

Email: first.last at userify.

Recent public activity

  1. comment
  2. comment
    Comment #47800400

    Rotating keys is easy with the right software. (I work @ Userify) Agree with the auditing point Token-based keys, to tptacek's point, is that they can be a giant pain once you star…

  3. comment
    Comment #47799989

    One key per device is exactly what we recommend too. Private keys should always be protected as much as possible within that device and should never leave that device. Just paste a…

  4. comment
  5. comment
    Comment #47678260

    The next one linked at the bottom, https://jonno.nz/posts/stealing-nanoclaw-patterns-for-webapp... has this bold and frankly unbelievable claim: "70% of startups fail due to premat…

  6. comment
  7. comment
    Comment #47635248

    Then install your own: curl i.userify.com | sudo - sE

  8. comment
    Comment #47634418

    The experience might be better right up until you're running it in prod and someone happens to ask about: Cert revocation (or even expiration) Sudo roles User removal and process t…

  9. comment
    Comment #47634288

    Honestly, we used to replace a lot of pam_ldap and similar sorts of awful solutions. With those, if your LDAP went down even for a heartbeat, you couldn't log in at all. So I total…

  10. comment
    Comment #47634214

    Great question. Not yet ;)

  11. comment
    Comment #47632331

    Well, TOFU is really just the model for how the chain of trust is established. In practice there isn’t really trust on first use : there’s verify the key matches what’s expected , …

  12. comment
    Comment #47628908

    That works for authn in the happy path: short-lived cert, grab it, connect, done. Except for everything around that: * user lifecycle (create/remove/rename accounts) * authz (who g…

  13. comment
    Comment #47628687

    SSH certs quietly hurt in prod. Short-lived creds + centralized CA just moves complexity upward without solving the core problem: user management. The system shifts from many small…

  14. comment
    Comment #47628547

    But then you can't log in if your box goes offline for any reason.

  15. comment
    Comment #47628508

    We're in the process of updating the experience to this century ! ;) We've always taken the stance that crusty is better than vulnerable, but it turns out that not having a modern …

  16. comment
    Comment #47628467

    Exactly. We'd had discussions about building https://Userify.com (plug!) around SSH certificates, but elected to go with keys instead, because Userify delivers most of the good thi…

  17. comment
  18. comment
    Comment #47240505

    Classic OpenSSH safety check: if /home/$user (or ~/.ssh) is too open, or ownership/modes are off, sshd will refuse pubkey auth. Annoying, but correct. If you still have some access…

  19. comment
    Comment #46368215

    at least it had a minimum of Clause. Clause. Punchline.

  20. comment
    Comment #46368183

    I like it too, even though it has that distinctive odor of being totally written by chatgpt though. (a bit distracting tbh)

  21. comment
    Comment #46368166

    One of the big issues was latency.

  22. comment
  23. comment
    Comment #46259850

    Thank you for the comprehensive answers! (By the way: NVIDIA AIstore is NOT a proxying/caching engine, although it can, which is somewhat unique among these types of stores. AIstor…

  24. comment
  25. comment
    Comment #46254941

    These questions are meant to be constructively critical, but not hyper-critical: I'm genuinely interested and a big fan of open-source projects in this space: * In terms of a high-…