Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
After the ciphers problem , I face some problems in authenticating with the use of public key. I used ssh-keygen -t rsa to create my own rsa public and private keys. Then, I editted the value of PublicKeyAuthentication so as it becomes yes in ssh_config file. I also copied public key mykey.pub to server and added it to authorized_keys (cat mykey.pub >> authorized_keys).
But, for my dissapointment, ssh denies to accept my prays ... Could you help me ? Any propositions? I have searched all the Internet till now but I didnt find a positive solution.
It might be the key format problem, try to vi the authorized_keys files and make it much more like the decent style...
I met these kinds of problems before...when I appended my putty-generated pub-key into the file....when I appended my Debian-generated pub0key into redhat....etc.
debug1: Next authentication method: publickey
debug1: Offering public key: thauma
debug3: send_pubkey_test
debug2: we sent a publickey packet, wait for reply
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug2: we did not send a packet, disable method
I still have problems... I generated a new pair of keys with the name thauma kai thauma.pub. You can see above the log messages I get through ssh -vvv -i thauma username@server. Any propositions??
You also need to copy the private key to your ~/.ssh directory and call it id_rsa, possibly the public key as well (although I can't quickly think of a reason why the public key would be needed there).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.