Live data from Hacker News

Viewing profile — cipherboy

cipherboy

HN member
Joined
Mon, Sep 28, 2015, 8:49 PM UTC
HN karma
700
Public activity
202 items

About cipherboy

Software developer. Dabbles in cryptography and SAT from time to time. Violin always. The BUSL-1.1 is not OSS. Contributor to OpenBao.

My views are my own, not that of any past, present, or future employer.

https://cipherboy.com

https://github.com/cipherboy

alexander.m.scheel@gmail.com

Recent public activity

  1. story
  2. story
  3. story
  4. story
  5. comment
    Comment #48928810

    Vault has had PKI since pre-v1; ACME was introduced in 2022 to modernize its APIs.

  6. comment
    Comment #44827389

    I'll bite ;-) Appreciate your replies as always tptacek! It is a fair criticism. But I think two things give us an advantage here: 1. IBM started this fork and later bought HashiCo…

  7. comment
    Comment #44826966

    Yes and https://discuss.hashicorp.com/t/hcsec-2024-05-vault-cert-aut... was an earlier authN+authZ bypass in the same code block. So maybe one step down in severity, though I do no…

  8. comment
    Comment #44825676

    Since HashiCorp and OP did not opt to disclose to OpenBao, the most authoritative source right now is HashiCorp's security tracker, linked down-thread: https://news.ycombinator.com…

  9. comment
    Comment #44825254

    To quote a movie, only a Sith deals in absolutes ;-) The OpenBao community call is in 10 minutes if you want to talk more about it live: https://calendar.google.com/calendar/embed?…

  10. comment
    Comment #44823317

    OpenBao, under the Linux Foundation's OpenSSF, is making meaningful improvements to the code. I'd love to have high-quality reports, if you're willing to re-visit these. :-)

  11. comment
    Comment #44823247

    I do not speak for HashiCorp, but they have published information on this CVE here: https://discuss.hashicorp.com/t/hcsec-2025-21-vault-user-enu... OpenBao is reasonably confident …

  12. comment
    Comment #44823035

    For anyone interested in CVE-2025-6010: https://discuss.hashicorp.com/t/hcsec-2025-21-vault-user-enu...

  13. comment
    Comment #44823027

    On behalf of the OpenBao project, I welcome collaboration with future researchers. We were not informed of these vulnerabilities before HashiCorp posted their usual CVE bulletins, …

  14. comment
    Comment #44277416

    Dupe of https://news.ycombinator.com/item?id=44276916

  15. comment
    Comment #44144812

    While I'm sure Vault contracts run more than what I'd care to know, the project is set up under the Linux Foundation and I've been told in the past that we as a project are capable…

  16. comment
    Comment #44143974

    Not without community involvement :-) Horizontal scalability and disaster recovery is one of the next larger features on our mind. We won't use the architecture of Performance Seco…

  17. comment
    Comment #44138127

    Yes, implemented from scratch by the community but (mostly--barring one reported issue) the same functionality and behavior. Not storage-level compatible, we (likely?) made differe…

  18. comment
    Comment #44137520

    You should read this RFC: https://github.com/openbao/openbao/issues/1340 If you use that with a PostgreSQL backend (which doesn't require raft and has faster leader changes), it mi…

  19. comment
    Comment #44134425

    It is a secrets manager; I think it's a fair question. Very few individuals will want to run them, the reality is they're mostly for businesses to consume. Businesses need maintena…

  20. comment
    Comment #44134409

    Definitely. It's why I've been pushing for open governance and slowly building community's trust in additional maintainers to avoid burnout and ensure continuity. You can see maint…

  21. comment
    Comment #44134391

    Nice! The biggest gap with Vault Enterprise that I'm hoping we'll get to next release will be horizontal scalability of read requests. We should be fairly compatible otherwise! Our…

  22. comment
    Comment #44134349

    AWS plugins are released separately: https://github.com/openbao/openbao-plugins/releases

  23. comment
    Comment #44134033

    Yes, a big thank you to you, Jan, in particular! The organization has been slowly building trust in more committers and maintainers and so he's had to personally review many a pull…

  24. comment
    Comment #44134022

    If you have reproducers for behavioral differences, happy to take issues and PRs! (Entities was discussed here: https://github.com/openbao/openbao/issues/1110#issuecomment-... ) Ri…

  25. comment
    Comment #44134006

    GitHub's charts are inaccurate and a quick glance at the commit list would tell you that: https://github.com/openbao/openbao/commits/main/ -- you have to cross some threshhold numb…