kcmastrpc
Joined 11 years ago
Karma
321
Submissions
138
Member since
Dec 28
sre, distributed systems engineer, docker captain, fitness nerd, scifi nerd
View on Hacker NewsRecent submissions
Comment · 6 months ago
Author here. Short version: if your agent needs secrets, the common routes are (1) dump them in its env, (2) materialize a .env file, or (3) give it a shell and let it run bws itself. All three have the same problem: the blast radius is everything the token can touch, and prompt injection turns them into full RCE and sadness.
This wraps the bws CLI as an MCP server with explicit CRUD tools for projects and secrets, plus a bws_run that takes an argv array instead of a shell string. First draft of bws_run accepted "sh -c ..."; that's the eval surface I wanted to remove. Shipped version forces explicit program invocation, and if you genuinely want a shell pipeline you have to put sh as argv[0], which is both visible in audit logs and trivially noticed.
A few things I thought worth calling out:
- Destructive tools (*_delete, bws_run) require confirm: true. Not a safety net (the model will set it); a hook point for your approval tooling so you don't have to pattern-match argument shapes.
- Wraps the CLI, not the Rust SDK. Subprocess + JSON parse is 350 lines. SDK path would have been weeks.
- No mocks in the test suite. Three of four integration tests failed against the real bws binary on first run. Caught a bws secret delete returns-plain-text bug that the JSON-stub protocol tests missed.
Code: https://github.com/kvncrw/bws-mcp-server (GPL-3.0). Issues and PRs welcome, especially from anyone running Vaultwarden with Secrets Manager — I don't have one to test against.
Comment · 8 months ago
I can relate. Sincerely debating whether I quit my well-paying and comfortable corporate job and just go full-time entrepreneur before the opportunities disappear.
Comment · 1 year ago
I've tried to incorporate the notion that it's none of my business what other people think of me. I don't always get it right, but having that attitude has helped tremendously on reducing my cortisol levels.
Comment · 1 year ago
this dude makes some pretty cool content. he built his own fab. highly recommend checking out his other vids.
Comment · 1 year ago
I’m sure there are plenty of civilizations that have done this, but on the time scale of the universe no one happens to look at just the right moment.
Comment · 2 years ago
I don't see a reason for my children to have smartphones until they're driving themselves to their own job and social functions.
Comment · 2 years ago
Right, doesn't everybody just use the same password everywhere? I don't see the point of these things.
Comment · 2 years ago
[flagged]
Comment · 2 years ago
As opposed to its previous owners? Don't let those shades get too dark, friend.
Comment · 2 years ago
What's interesting about these two CEOs is one is definitely interested in selling shovels, the other is interested in selling contracting services that must lease the shovels.
I think you're right though, Meta has real challenges ahead of them in terms of capacity and creating an actual product that can be monetized for the general public. It's worth mentioning that FB was doing AI long before the hype train started really rolling, and monetized it -- all behind the scenes.
Comment · 2 years ago
I don't think they're supposed to be "hands-on" with the engineering. They literally hire thousands (if not more) to deal with those problems.
https://github.com/facebookresearch -- there's like 1,000ish repo's here.