[06:34:04] Marlen Caemmerer * Re: [Toolserver-l] ssl certificate [07:09:04] Federico Leva (Nemo) * Re: [Toolserver-l] Toolserver db outperformed by labs [08:18:04] Silke Meyer * Re: [Toolserver-l] ssl certificate [09:07:04] Marlen Caemmerer * Re: [Toolserver-l] ssl certificate [13:22:04] Marlen Caemmerer * Re: [Toolserver-l] ssl certificate [14:28:04] Silke Meyer * [Toolserver-announce] Status update on Tool Labs [14:36:04] Patricia Pintilie * Re: [Toolserver-l] Patricia Pintilie [14:40:36] Patricia Pintilie > /dev/null [15:41:04] Tim Landscheidt * Re: [Toolserver-l] Toolserver db outperformed by labs [17:56:04] Tim Landscheidt * Re: [Toolserver-l] ssl certificate [18:55:04] Marlen Caemmerer * Re: [Toolserver-l] ssl certificate [19:03:04] Tim Landscheidt * Re: [Toolserver-l] ssl certificate [19:11:25] hi all. I am trying to run the command acctrenew on nightshade, but it is not found. I also checked if it was a problem with my PATH, it is not... What should I do? [19:11:56] I can login with my password only at nightshade, not at the willow [19:15:32] everton137: acctrenew works only on Solaris hosts. Why can't you login to willow? [19:16:05] scfc_de, I don't know. I enter the very same password I enter no nightshade and it doesn't work... [19:16:51] everton137: What password? Toolserver uses keys for login. [19:17:34] scfc_de, well, I added my public key in the beginning, but later it asked me for a password, which I changed once at nightshade [19:17:45] I cannot remember when I did set the password [19:18:40] everton137: How did you set the password? With "passwd"? "setpass"? [19:19:27] scfc_de, initially i just followed the LDAP instructions. setpass, I guess. But I cannot remember now if I used passwd later [19:20:23] everton137: So you can log into willow, but you can't run acctrenew there because it asks you for a password, or can't you log into willow altogether? [19:20:50] scfc_de, I cannot log in at willow because it asks me a password... [19:20:58] I can only at nightshade [19:21:34] What happens if you "ssh willow" on nightshade? [19:21:50] scfc_de, both ask me a password [19:22:01] then I can rightly login on nightshade, not on willow [19:23:14] everton137: What's "both"? If you are logged in at nightshade, i. e. you see a prompt "everton137@nightshade:~$ ", and you enter there "ssh willow" + RET, what is displayed? [19:23:16] scfc_de, do you know if I can add my public key again [19:23:44] scfc_de, got it now, trying [19:23:45] sorry [19:25:50] scfc_de, worked! [19:25:52] thanks! [19:25:53] :) [19:27:17] everton137: No problem. Can you log into willow now from your system? [19:27:33] trying [19:29:35] On your own system, in ~/.ssh/config, do you have a specific configuration for nightshade? [19:30:33] scfc_de, no, I don't [19:30:45] Hmmm. [19:30:47] I need be away a few minutes. I will fix that later [19:30:57] it is not working to login with nighthade passord [19:31:07] but I can login on willow from nightshade [19:31:21] Do you use IP6? [19:31:27] scfc_de, no [19:31:36] Then I'm out of ideas. [19:31:50] scfc_de, no problem. I will try later to add my public key again [19:32:18] it was working, but it stoped. then I began to use my password and didn't try to figure out why. now fixed with your tip, thanks! [19:32:39] I mean, the account renew is fixe [19:32:40] d [19:33:32] everton137: I think you need a root to update your public key. [19:34:35] if you are still logged in, you can change ~/.ssh/authorized_keys [19:35:23] valhallasw: *Argl*, of course. [19:35:48] On Tools, it's LDAP only. [19:36:26] everton137: Could you post that file? [19:52:36] valhallasw, scfc_de I added my public key (again) on ~/.ssh/authorized_keys. Willow still asks my passord. [19:54:42] everton137: Do you have a mantra on your key? [19:55:17] "Passphrase" is the term used more often, I believe :-). [19:55:32] scfc_de, what does having a mantra mean? :P [20:10:19] everton137: when you log in from your own computer or from nightshade? [20:10:31] the first should work, the latter might not [20:10:37] valhallasw, from my computer [20:13:42] everton137: hum, strange [20:13:58] needa finsh other things [20:13:58] everton137: Now do you have a passphrase on your key? [20:14:15] I'll come back to this later. thanks, scfc_de valhallasw [20:14:30] scfc_de, no, I don't think so. When I created it, I left blnk [20:14:32] scfc_de: that shouldn't matter [20:15:13] everton137: you could try using ssh -v willow.toolserver.org [20:15:28] it should show you any issues [20:17:07] valhallasw, the output http://pastebin.com/2r9hw5gK [20:17:17] and then it asks the password [20:20:39] everton137: you seem to have multiple private keys [20:20:58] are you sure the relevant one has it's public key in authorized_keys? [20:20:59] valhallasw, thanks, I'll check it out later [20:21:08] I think so. [20:21:20] everton137: and .ssh/id_rsa seems to be a public key, which is strange [20:21:29] the public key should be in .ssh/id_rsa.pub [20:21:45] although that doesn't explain why you can login to nightshade [20:22:00] everton137: can you maybe also ssh -v nightshade.toolserver.org, exit the shell and post that log? [20:22:10] valhallasw, I really cannot do this now [20:22:18] everton137: no problem :-) [20:22:18] I'll try tomorrow [20:22:31] sure! try to compare the outputs. [20:26:29] valhallasw: My thought was that maybe somehow everton137's ssh was configured to offer a different public key to willow than to nightshade, and one of them had a passphrase, and the other not. [20:27:43] There are some differences in the sshd configs, for example you can't use sshfs to the Debian hosts, but it works on the Solaris ones, but for basic login it shouldn't matter, you're right about that. [20:29:03] scfc_de: the passphrase is just the secondary login mechanism [20:29:21] I'm not sure why that is activated anyway, as no-one should login using a password... [20:36:49] valhallasw: Pass*word* you mean. And "no-one *can* login using a password" :-). [20:46:01] scfc_de: then why does the server suggest it at all? [20:47:03] basically: publickey,password,keyboard-interactive,hostbased should really be publickey,hostbased [20:47:20] so that when your key is not accepted, you just cannot login, instead of getting a password prompt [20:50:30] valhallasw: Perhaps some access for the roots? Otherwise, I certainly agree that it would be better to change it. When LDAP is down, the password prompt confuses the hell out of most users. [20:54:16] scfc_de: it's possible to configure it on a user-by-user basis afaik [20:54:36] valhallasw: That would be nice.