this post was submitted on 23 Jul 2023
59 points (96.8% liked)

Selfhosted

40459 readers
298 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

I have too many machines floating around, some virtual, some physical, and they're getting added and removed semi-frequently as I play around with different tools/try out ideas. One recurring pain point is I have no easy way to manage SSH keys around them, and it's a pain to deal with adding/removing/cycling keys. I know I can use AuthorizedKeysCommand on sshd_config to make the system fetch a remote key for validation, I know I could theoretically publish my pub key to github or alike, but I'm wondering if there's something more flexible/powerful where I can manage multiple users (essentially roles) such that each machine can be assigned a role and automatically allow access accordingly?

I've seen Keyper before, but the container haven't been updated for years, and the support discord owner actively kicks everyone from the server, even after asking questions.

Is there any other solution out there that would streamline this process a bit?

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 7 points 1 year ago (2 children)

I do this, use the small step ca/Cli to manage the lot. It's amazing

[–] [email protected] 8 points 1 year ago (1 children)

It's such an underrated feature. It baffles me how people immediately turn to overly complicated solutions solving a problem they don't really have to solve, just because everyone assumes the only way is the default commonly known way. Like OP, people immediately jump to the conclusion you need extra software to manage the keys, rather than using another authentication method natively supported, and keep filling their known_hosts file with junk, making the whole validation process useless because everyone just accepts whatever key the host presents.

It's amazing how simple it is. Developer needs temporary access to debug a web server? Sure, here's your 2h valid cert to log in as the web user on the server, don't even need to actually log into the server to put their key in and then remove it. I mint a cert and it's ready to go on whichever users and servers I specified in the cert. Can't even gain persistence because regular authorized_keys is disabled and we have limited session durations.

I regularly leave people baffled at work because I come up with a clever and built-in super simple solution to something they expected to just slap more scripts and software to work around the only way they know to use the software. Read your manpages in full folks, it'll save you so much work. Know what your software is capable of.

[–] [email protected] 5 points 1 year ago

That's a long rant, but your on point with it. I have a colleague who refuses to try new things cuz they don't understand that it makes life easier, I do tend to find the solutions that are simpler and easier to work

[–] [email protected] 0 points 1 year ago (1 children)

Is smallstep free to self host? Looking at their pricing page it's kind of unclear, and their saas is pretty pricey.

[–] [email protected] 1 points 1 year ago