Re: decoding sshd failure
At 10:13 PM 6/3/2004, you wrote: >Below is a fragment of output from sshd -d -d -d > >Can someone tell me why it doesn't like my publickey? I think I've done everything >right, but no joy. I can login using the password just fine. >Thanks. >David > >debug1: userauth-request for user dcorbin service ssh-connection method publickey >debug1: attempt 1 failures 1 >debug2: input_userauth_request: try method publickey >debug1: test whether pkalg/pkblob are acceptable >debug3: mm_key_allowed entering >debug3: mm_request_send entering: type 20 >debug3: monitor_read: checking request 20 >debug3: mm_answer_keyallowed entering >debug3: mm_answer_keyallowed: key_from_blob: 0x100ecb30 >debug1: temporarily_use_uid: 11141/10513 (e=18/544) >debug1: trying public key file /home/dcorbin/.ssh/authorized_keys >debug3: mm_key_allowed: waiting for MONITOR_ANS_KEYALLOWED >debug3: mm_request_receive_expect entering: type 21 >debug3: mm_request_receive entering >debug1: restore_uid: (unprivileged) >debug1: temporarily_use_uid: 11141/10513 (e=18/544) >debug1: trying public key file /home/dcorbin/.ssh/authorized_keys2 >debug1: restore_uid: (unprivileged) >debug3: mm_answer_keyallowed: key 0x100ecb30 is disallowed >debug3: mm_request_send entering: type 21 >debug2: userauth_pubkey: authenticated 0 pkalg ssh-dss >Failed publickey for dcorbin from 172.16.5.102 port 1697 ssh2 I can't tell from this. Yours and my output diverge after the line in your file reading: >debug1: trying public key file /home/dcorbin/.ssh/authorized_keys Mine goes on with: debug3: secure_filename: checking '/users/lhall/.ssh' debug3: secure_filename: checking '/users/lhall' debug3: secure_filename: terminating check at '/users/lhall' Given that yours is "waiting", my WAG is that your home is not local. Things may also be complicated by the fact that your user is a domain user. That's pretty tenuous but I don't have access to a domain environment at the moment so I can't try it for myself. You might want to try logging in as a local user though. But if you're home directory is a UNC share that requires password authentication, that's going to be your real problem. Otherwise, you must have some permissions problem. Your best bet is to grab the source and track where the "waiting" message is that you get. That should help provide some context. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: decoding sshd failure
On Thursday 03 June 2004 23:18, Larry Hall wrote: > At 10:13 PM 6/3/2004, you wrote: > >Below is a fragment of output from sshd -d -d -d > > > >Can someone tell me why it doesn't like my publickey? I think I've done > > everything right, but no joy. I can login using the password just fine. > > Thanks. > >David > > > >debug1: userauth-request for user dcorbin service ssh-connection method > > publickey debug1: attempt 1 failures 1 > >debug2: input_userauth_request: try method publickey > >debug1: test whether pkalg/pkblob are acceptable > >debug3: mm_key_allowed entering > >debug3: mm_request_send entering: type 20 > >debug3: monitor_read: checking request 20 > >debug3: mm_answer_keyallowed entering > >debug3: mm_answer_keyallowed: key_from_blob: 0x100ecb30 > >debug1: temporarily_use_uid: 11141/10513 (e=18/544) > >debug1: trying public key file /home/dcorbin/.ssh/authorized_keys > >debug3: mm_key_allowed: waiting for MONITOR_ANS_KEYALLOWED > >debug3: mm_request_receive_expect entering: type 21 > >debug3: mm_request_receive entering > >debug1: restore_uid: (unprivileged) > >debug1: temporarily_use_uid: 11141/10513 (e=18/544) > >debug1: trying public key file /home/dcorbin/.ssh/authorized_keys2 > >debug1: restore_uid: (unprivileged) > >debug3: mm_answer_keyallowed: key 0x100ecb30 is disallowed > >debug3: mm_request_send entering: type 21 > >debug2: userauth_pubkey: authenticated 0 pkalg ssh-dss > >Failed publickey for dcorbin from 172.16.5.102 port 1697 ssh2 > > I can't tell from this. Yours and my output diverge after the line in > > your file reading: > >debug1: trying public key file /home/dcorbin/.ssh/authorized_keys > > Mine goes on with: > > debug3: secure_filename: checking '/users/lhall/.ssh' > debug3: secure_filename: checking '/users/lhall' > debug3: secure_filename: terminating check at '/users/lhall' > > Given that yours is "waiting", my WAG is that your home is not local. > Things may also be complicated by the fact that your user is a domain > user. That's pretty tenuous but I don't have access to a domain > environment at the moment so I can't try it for myself. You might > want to try logging in as a local user though. But if you're home > directory is a UNC share that requires password authentication, that's > going to be your real problem. Otherwise, you must have some permissions > problem. Your best bet is to grab the source and track where the "waiting" > message is that you get. That should help provide some context. > Thanks. My home directory is NOT a UNC share, though the user is a domain user as your surmised (somehow). I'll give your suggestions a try. > > > > > -- > Larry Hall http://www.rfk.com > RFK Partners, Inc. (508) 893-9779 - RFK Office > 838 Washington Street (508) 893-9889 - FAX > Holliston, MA 01746 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: decoding sshd failure
Someone wrote: Below is a fragment of output from sshd -d -d -d Can someone tell me why it doesn't like my publickey? I think I've done everything right, but no joy. I can login using the password just fine. Sorry, I missed the start of this thread so I don't know who the original author is but I have some suggestions: I had a problem with ssh not finding my .ssh directory. It turned out that ssh gets your home directory from /etc/passwd and not from $HOME and in my case, for perverse Windows-related reasons I don't understand, this was different. Editing /etc/passwd fixed it. Check the path that ssh is reporting that its looking in and check that this is the right place. Also, I had an embarrassing error the first time I set this up - being British I spelt authorized_keys with an 's' not a 'z'. It took me a while to spot the problem. You don't say what your directory structure is, so could one of these be the problem? Andy -- Andy Rushton, Southampton, UK Be careful or be road-kill. -- Calvin -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: decoding sshd failure
On Friday 04 June 2004 07:40, Andy Rushton wrote: > Someone wrote: > >>>Below is a fragment of output from sshd -d -d -d > >>> > >>>Can someone tell me why it doesn't like my publickey? I think I've done > >>>everything right, but no joy. I can login using the password just fine. > > Sorry, I missed the start of this thread so I don't know who the > original author is but I have some suggestions: > > I had a problem with ssh not finding my .ssh directory. It turned out > that ssh gets your home directory from /etc/passwd and not from $HOME > and in my case, for perverse Windows-related reasons I don't understand, > this was different. Editing /etc/passwd fixed it. Check the path that > ssh is reporting that its looking in and check that this is the right > place. > /home/dcorbin, which is what I expected. > Also, I had an embarrassing error the first time I set this up - being > British I spelt authorized_keys with an 's' not a 'z'. It took me a > while to spot the problem. > > You don't say what your directory structure is, so could one of these be > the problem? The directory structure, as near as I can tell, is "normal". Permission seem 'reasonable' (and I seem to remember sshd will tell you when your permissions are wrong). > > Andy -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: decoding sshd failure
At 06:38 AM 6/4/2004, you wrote: >On Thursday 03 June 2004 23:18, Larry Hall wrote: >> At 10:13 PM 6/3/2004, you wrote: >> >Below is a fragment of output from sshd -d -d -d >> > >> >Can someone tell me why it doesn't like my publickey? I think I've done >> > everything right, but no joy. I can login using the password just fine. >> > Thanks. >> >David >> > >> >debug1: userauth-request for user dcorbin service ssh-connection method >> > publickey debug1: attempt 1 failures 1 >> >debug2: input_userauth_request: try method publickey >> >debug1: test whether pkalg/pkblob are acceptable >> >debug3: mm_key_allowed entering >> >debug3: mm_request_send entering: type 20 >> >debug3: monitor_read: checking request 20 >> >debug3: mm_answer_keyallowed entering >> >debug3: mm_answer_keyallowed: key_from_blob: 0x100ecb30 >> >debug1: temporarily_use_uid: 11141/10513 (e=18/544) >> >debug1: trying public key file /home/dcorbin/.ssh/authorized_keys >> >debug3: mm_key_allowed: waiting for MONITOR_ANS_KEYALLOWED >> >debug3: mm_request_receive_expect entering: type 21 >> >debug3: mm_request_receive entering >> >debug1: restore_uid: (unprivileged) >> >debug1: temporarily_use_uid: 11141/10513 (e=18/544) >> >debug1: trying public key file /home/dcorbin/.ssh/authorized_keys2 >> >debug1: restore_uid: (unprivileged) >> >debug3: mm_answer_keyallowed: key 0x100ecb30 is disallowed >> >debug3: mm_request_send entering: type 21 >> >debug2: userauth_pubkey: authenticated 0 pkalg ssh-dss >> >Failed publickey for dcorbin from 172.16.5.102 port 1697 ssh2 >> >> I can't tell from this. Yours and my output diverge after the line in >> >> your file reading: >> >debug1: trying public key file /home/dcorbin/.ssh/authorized_keys >> >> Mine goes on with: >> >> debug3: secure_filename: checking '/users/lhall/.ssh' >> debug3: secure_filename: checking '/users/lhall' >> debug3: secure_filename: terminating check at '/users/lhall' >> >> Given that yours is "waiting", my WAG is that your home is not local. >> Things may also be complicated by the fact that your user is a domain >> user. That's pretty tenuous but I don't have access to a domain >> environment at the moment so I can't try it for myself. You might >> want to try logging in as a local user though. But if you're home >> directory is a UNC share that requires password authentication, that's >> going to be your real problem. Otherwise, you must have some permissions >> problem. Your best bet is to grab the source and track where the "waiting" >> message is that you get. That should help provide some context. >> > >Thanks. My home directory is NOT a UNC share, though the user is a domain >user as your surmised (somehow). Magic. ;-) Local user IDs are less than 1. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: decoding sshd failure
At 08:27 AM 6/4/2004, you wrote: >On Friday 04 June 2004 07:40, Andy Rushton wrote: >> Someone wrote: >> >>>Below is a fragment of output from sshd -d -d -d >> >>> >> >>>Can someone tell me why it doesn't like my publickey? I think I've done >> >>>everything right, but no joy. I can login using the password just fine. >> >> Sorry, I missed the start of this thread so I don't know who the >> original author is but I have some suggestions: >> >> I had a problem with ssh not finding my .ssh directory. It turned out >> that ssh gets your home directory from /etc/passwd and not from $HOME >> and in my case, for perverse Windows-related reasons I don't understand, >> this was different. Editing /etc/passwd fixed it. Check the path that >> ssh is reporting that its looking in and check that this is the right >> place. >> > >/home/dcorbin, which is what I expected. > >> Also, I had an embarrassing error the first time I set this up - being >> British I spelt authorized_keys with an 's' not a 'z'. It took me a >> while to spot the problem. >> >> You don't say what your directory structure is, so could one of these be >> the problem? > >The directory structure, as near as I can tell, is "normal". Permission seem >'reasonable' (and I seem to remember sshd will tell you when your permissions >are wrong). Depends. Depends on what 'StrictModes' is set to in your /etc/sshd_config? -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
