3 ms·
Yeah, you should re-educate yourself. Like i said, i used SSH certificates managed exclusively with ssh-keygen, i don't have any connection between the OpenSSL
by blueflow 5y ago
Yeah, you should re-educate yourself. Like i said, i used SSH certificates managed exclusively with ssh-keygen, i don't have any connection between the OpenSSL and SSH cryptosystems, nor do i see a point in that. My advice: Disregard any blog posts mucking SSH certs with OpenSSL and take the same time to read the ssh-keygen manpage.
- inetknght 5y ago> Yeah, you should re-educate yourself. Thanks! That sounds quite condescending. I'd educated myself by reading about ssh keys in ssh and wondering how to use them. Perhaps you should make your own blog post describing how to do it all using only ssh-keygen then.
- blueflow 5y agoHere is my "blogpost": https://www.man7.org/linux/man-pages/man1/ssh-keygen.1.html https://www.man7.org/linux/man-pages/man1/ssh-keygen.1.html . The signing process is the `ssh-keygen -I` part. The source of truth (in sync with your currently installed version) is right on your disk. Invoke `man ssh-keygen`. Sorry for my tone. I'm pissed that, every second day, some person comes along and demonstrates to me that I'm seemingly the only person in the world who is reading the documentation on the tools we all use. Like, how do you even know what you are doing?
- inetknght 5y agoAnd yet: I did read the documentation and using openssl was the solution I had come up with. Perhaps I was using a nonstandard version of ssh. Telling people to "just read the documentation" is quite condescending when they're demonstrating that they've come up with a different solution. It was years ago and I don't remember what version I was using. Indeed, using ssh-keygen for the whole process certainly seems easier.
- blueflow 5y agoI'm sorry for my harsh words.