To make it clear, only you can write an encrypted message (using your private key) that the server can decrypt using your public key. The two parties (you and the server) have each other's public key, which means that each of you can decrypt any message coming from each other. Let's assume you configured the server to know your public key, and you have the public key of the server. When you connect to a server using SSH, the server sends you their public key, so you can also verify it's identity. Ok, we have two keys, a public key and a private key, let's see how all this works. Keep your private key secret, store it securely somewhere that only you can access it, this one is never shared. And the messages you send are encrypted using your private key. Your public key is the one that you give anyone that wants to identify you, with the public key anyone can decrypt messages coming from you. SSH keys come in pairs, a public key and a private key. To understand key pairs, first, let's talk about some basic concepts. That is the idea behind using key pairs, let's have a look. To make it harder, the questions change, and only you can answer those questions correctly. It would be nice if you could establish a connection to a server and then prove that it is you by answering a series of questions that only you can answer. It doesn't matter how but the problem is that the password is being transmitted and if intercepted it can be used by anyone to impersonate you. The password can be intercepted, or you can be tricked into sending it to a server pretending to be the real server. Transmitting your password through the internet to connect to a remote server is dangerous.

Copy paste private key into gpg suite