6 ms·
Referring to the previous person's comment, that you need to manage a PKI and have to distribute the keys yourself, no auth/login etc.
by PLG88 8mo ago
Referring to the previous person's comment, that you need to manage a PKI and have to distribute the keys yourself, no auth/login etc.
- tjoff 8mo agoHow does that make it not "truly open source"? I made a shell script that does most of that for my needs.
- PLG88 8mo agoFair, I was being loose with my language. What I should have said is that it does not come fully featured open source, that you need to do a certain amount of rolling your own.
- esseph 8mo agoThe same could be said for a webserver, a radius server, etc. I mean ssh "requires" a network to be remotely useful :) Edit, since I can't reply sadly: You're right, that was a bad example. I can probably list at least a few dozen things that all require certificates though, which was really my point. Everything has dependencies. Also if you just... Don't trust big tech, run your own CA.
- PLG88 8mo agonah, I dont buy that. A network is not a functional requirement of SSH etc in your use case.
- PLG88 8mo agoRight, but if certificates are a fundamental part of your design, you should include the functional mechanisms to manage them imho (i.e., key distribution, auth/login). The developers created it, but they keep it in the commercial product. Other overlays which use PKI include those functions in the FOSS.