I am away from my office for the week. In Sacramento for the IEEE 802.1 interim meeting (for anyone in the neighborhood...). And I am working on SSH with my Centos install(s). 1) For right now I am using my XP drive with Tectia client. I have SSHed into my Centos server using password method and uploaded my public key and such. I see everything there. I think. I then delete all authentication methods but public key and am told that no recognized authentication match. When I add password back into my client, I get the password authentication method. My hunch is there is something I need to do with the SSH server config to access client certificate authentication? What do I need to do, and remember, all I have is a text window into my machine (can su) and I do not have my VI manual with me! (I will go and look for one online). 2) later this evening, I will pop in my Centos drive and then SSH from a Centos client. But of course my keys and such are on my XP drive. I know where Tectia keeps all of its keys, as I have moved them from one XP drive to another. Anyone know what I need to do? I do have a USB drive for the transfer. Or I can upload everything to my Centos server, then download to my Centos client. Thank you for your continued help. Oh, I have been going back into all of my threads here and pulling out notes on what to do to avoid asking something more than once.
the server file /home/username/.ssh/authorized_keys must contain a line containing /home/username/.ssh/id_dsa.pub (use ssh-keygen -t dsa to generate it) Furthermore /etc/ssh/sshd_config must not have PubkeyAuthentication no (yes is the default) [if you delete it remember to /etc/init.d/sshd restart] cheers, MaZe. On Tue, 10 Jan 2006, Robert Moskowitz wrote:> I am away from my office for the week. In Sacramento for the IEEE 802.1 > interim meeting (for anyone in the neighborhood...). > > And I am working on SSH with my Centos install(s). > > 1) For right now I am using my XP drive with Tectia client. I have SSHed > into my Centos server using password method and uploaded my public key and > such. I see everything there. I think. I then delete all authentication > methods but public key and am told that no recognized authentication match. > When I add password back into my client, I get the password authentication > method. > > My hunch is there is something I need to do with the SSH server config to > access client certificate authentication? What do I need to do, and > remember, all I have is a text window into my machine (can su) and I do not > have my VI manual with me! (I will go and look for one online). > > 2) later this evening, I will pop in my Centos drive and then SSH from a > Centos client. But of course my keys and such are on my XP drive. I know > where Tectia keeps all of its keys, as I have moved them from one XP drive to > another. Anyone know what I need to do? I do have a USB drive for the > transfer. Or I can upload everything to my Centos server, then download to > my Centos client. > > Thank you for your continued help. > > Oh, I have been going back into all of my threads here and pulling out notes > on what to do to avoid asking something more than once. > > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos >
Robert Moskowitz wrote:> I am away from my office for the week. In Sacramento for the IEEE > 802.1 interim meeting (for anyone in the neighborhood...). > > And I am working on SSH with my Centos install(s). > > 1) For right now I am using my XP drive with Tectia client. I have > SSHed into my Centos server using password method and uploaded my > public key and such. I see everything there. I think. I then delete > all authentication methods but public key and am told that no > recognized authentication match. When I add password back into my > client, I get the password authentication method.I would generate a key "ssh-keygen -t rsa" on a linux machine, cp to the server, cat id_rsa.pub>>.ssh/authorized_keys2 and see if that gets the job done. The windows machine adds additional complexity that is hard to debug, get the linux part working first. Make sure the permissions are correct in ~/.ssh/ , that is very important. .ssh/authorized_keys2 must be 0600. drwx------ 2 root root 4096 Jan 11 2004 . drwxr-x--- 27 root root 4096 Jan 6 12:10 .. -rw------- 1 root root 580 Jan 3 2005 authorized_keys -rw------- 1 root root 2982 Apr 25 2005 authorized_keys2 -rw------- 1 root root 672 Jan 11 2004 id_dsa -rw-r--r-- 1 root root 613 Jan 11 2004 id_dsa.pub -rw------- 1 root root 538 Jan 11 2004 identity -rw-r--r-- 1 root root 342 Jan 11 2004 identity.pub -rw-r--r-- 1 root root 6998 Dec 29 11:44 known_hosts -- Chris Mason NetConcepts (264) 497-5670 Fax: (264) 497-8463 Int: (305) 704-7249 Fax: (815)301-9759 Cell: 264-235-5670 Yahoo IM: netconcepts_anguilla at yahoo.com