Re: Why does 'ssh' and 'scp' work to one and not another?
.
I have previously responded to each previous suggestion and request for info
to try to find a solution to the subject problem, and I will continue to
do so. There have been three subsequent replies to this issue and I will
now reply to each one separately, in order.
First, kitepilot last suggested the following, with replies below:
(1) grep joe /etc/passwd -- and post the line
(2) find /var/log -type f -exec grep -H joe {} \; -- and post the output
(3) Look at line:
Feb 10 18:18:16 localhost su: pam_unix(su:auth): authentication failure;
logname= uid=500 euid=0 tty=pts/1 ruser=joe rhost= user=root
(4) From console in 73
ssh -v localhost (on 73) -- and post the reply
(5) Then from the other machine do:
ssh -v 73 (on 73) -- and post that too
(1) $ fgrep joe passwd -- result:
joe:x:500:500:Joe:/home/joe:/bin/bash
(2) $ find /var/log -type f -exec grep -H joe {} \;
Due to the length of the result of this command, I have uploaded that result
at the following link: http://www.upquick.com/linux/temp/var.log.joe
(3) Look at line:
Feb 10 18:18:16 localhost su: pam_unix(su:auth): authentication failure;
logname= uid=500 euid=0 tty=pts/1 ruser=joe rhost= user=root
I have looked at that line, but I don't know what to do about it.
(4) From console in 73
ssh -v localhost (on 73) -- and post the reply -- the result is below:
OpenSSH_5.3p1, OpenSSL 0.9.8l 5 Nov 2009
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to localhost [127.0.0.1] port 22.
debug1: Connection established.
debug1: identity file /home/joe/.ssh/identity type -1
debug1: identity file /home/joe/.ssh/id_rsa type -1
debug1: identity file /home/joe/.ssh/id_dsa type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.3
debug1: match: OpenSSH_5.3 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.3
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server-client aes128-ctr hmac-md5 none
debug1: kex: client-server aes128-ctr hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(102410248192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host 'localhost' is known and matches the RSA host key.
debug1: Found key in /home/joe/.ssh/known_hosts:4
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue:
publickey,password,keyboard-interactive
debug1: Next authentication method: publickey
debug1: Trying private key: /home/joe/.ssh/identity
debug1: Trying private key: /home/joe/.ssh/id_rsa
debug1: Trying private key: /home/joe/.ssh/id_dsa
debug1: Next authentication method: keyboard-interactive
debug1: Authentications that can continue:
publickey,password,keyboard-interactive
debug1: Next authentication method: password
j...@localhost's password:
(5) Then from the other machine do:
ssh -v 73 -- and post that too
Since I did the first 'ssh -v' on computer #73, by the other machine
I assumed you meant to do the suggested command on machine #68. Here was
the result:
$ ssh -v 73
bash: syntax error near unexpected token `73'
Sorry if I did not follow your last instruction correctly, kitepilot.
Responses to the other two suggestions/requests will follow shortly.
---
PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: Why does 'ssh' and 'scp' work to one and not another?
OK, this is what we know:
joe:x:500:500:Joe:/home/joe:/bin/bash
You can log in with a valid shell.
ssh -v localhost (on 73)
It doesn't say in your message that .73 accepted the password, but:
a.- If you could not complete the login because it refused the password,
then you have a problem local to .73
b.- If you logged in successfully, then your problem is most likely outside
the .73 machine, unless you are running xinetd (ps aux|grep inetd)
Now I apologize, because:
ssh -v 73 -- and post that too
Actually meant:
ssh -v place here the full IP address of .73 -- and post that too
:)
I still don't know what the problem is.
But I know what it is not... :)
If you grant me access to .73 I'll help you debug it over the phone, this
could be a long array of issues, and maybe more than 1.
ET
j...@actionline.com writes:
.
I have previously responded to each previous suggestion and request for info
to try to find a solution to the subject problem, and I will continue to
do so. There have been three subsequent replies to this issue and I will
now reply to each one separately, in order.
First, kitepilot last suggested the following, with replies below:
(1) grep joe /etc/passwd -- and post the line
(2) find /var/log -type f -exec grep -H joe {} \; -- and post the output
(3) Look at line:
Feb 10 18:18:16 localhost su: pam_unix(su:auth): authentication failure;
logname= uid=500 euid=0 tty=pts/1 ruser=joe rhost= user=root
(4) From console in 73
ssh -v localhost (on 73) -- and post the reply
(5) Then from the other machine do:
ssh -v 73 (on 73) -- and post that too
(1) $ fgrep joe passwd -- result:
joe:x:500:500:Joe:/home/joe:/bin/bash
(2) $ find /var/log -type f -exec grep -H joe {} \;
Due to the length of the result of this command, I have uploaded that result
at the following link: http://www.upquick.com/linux/temp/var.log.joe
(3) Look at line:
Feb 10 18:18:16 localhost su: pam_unix(su:auth): authentication failure;
logname= uid=500 euid=0 tty=pts/1 ruser=joe rhost= user=root
I have looked at that line, but I don't know what to do about it.
(4) From console in 73
ssh -v localhost (on 73) -- and post the reply -- the result is below:
OpenSSH_5.3p1, OpenSSL 0.9.8l 5 Nov 2009
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to localhost [127.0.0.1] port 22.
debug1: Connection established.
debug1: identity file /home/joe/.ssh/identity type -1
debug1: identity file /home/joe/.ssh/id_rsa type -1
debug1: identity file /home/joe/.ssh/id_dsa type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.3
debug1: match: OpenSSH_5.3 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.3
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server-client aes128-ctr hmac-md5 none
debug1: kex: client-server aes128-ctr hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(102410248192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host 'localhost' is known and matches the RSA host key.
debug1: Found key in /home/joe/.ssh/known_hosts:4
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue:
publickey,password,keyboard-interactive
debug1: Next authentication method: publickey
debug1: Trying private key: /home/joe/.ssh/identity
debug1: Trying private key: /home/joe/.ssh/id_rsa
debug1: Trying private key: /home/joe/.ssh/id_dsa
debug1: Next authentication method: keyboard-interactive
debug1: Authentications that can continue:
publickey,password,keyboard-interactive
debug1: Next authentication method: password
j...@localhost's password:
(5) Then from the other machine do:
ssh -v 73 -- and post that too
Since I did the first 'ssh -v' on computer #73, by the other machine
I assumed you meant to do the suggested command on machine #68. Here was
the result:
$ ssh -v 73
bash: syntax error near unexpected token `73'
Sorry if I did not follow your last instruction correctly, kitepilot.
Responses to the other two suggestions/requests will follow shortly.
---
PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
---
PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: Why does 'ssh' and 'scp' work to one and not another?
. craig last wrote: echo - \n Marking my place in the logs \n - \ /var/log/secure echo - \n Marking my place in the logs \n - \ /var/log/messages then try to login, then look at the logs - after the marks you just made. Here's the result: For secure: - \n Marking my place in the logs \n - Feb 12 10:24:01 localhost crond[24469]: pam_unix(crond:session): session opened for user root by (uid=0) Feb 12 10:24:01 localhost crond[24469]: pam_unix(crond:session): session closed for user root Feb 12 10:25:01 localhost crond[24552]: pam_unix(crond:session): session opened for user root by (uid=0) Feb 12 10:25:01 localhost crond[24552]: pam_unix(crond:session): session closed for user root For messages: - \n Marking my place in the logs \n - Feb 12 10:24:01 localhost crond[24470]: (root) CMD ( /usr/share/msec/promisc_check.sh) Feb 12 10:24:43 localhost sshd[24518]: Failed password for joe from 192.168.0.68 port 34485 ssh2 Feb 12 10:24:46 localhost last message repeated 2 times Feb 12 10:25:01 localhost crond[24553]: (root) CMD ( /usr/share/msec/promisc_check.sh) --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: Why does 'ssh' and 'scp' work to one and not another?
On Fri, 2010-02-12 at 10:34 -0700, j...@actionline.com wrote: . craig last wrote: echo - \n Marking my place in the logs \n - \ /var/log/secure echo - \n Marking my place in the logs \n - \ /var/log/messages then try to login, then look at the logs - after the marks you just made. Here's the result: For secure: - \n Marking my place in the logs \n - Feb 12 10:24:01 localhost crond[24469]: pam_unix(crond:session): session opened for user root by (uid=0) Feb 12 10:24:01 localhost crond[24469]: pam_unix(crond:session): session closed for user root Feb 12 10:25:01 localhost crond[24552]: pam_unix(crond:session): session opened for user root by (uid=0) Feb 12 10:25:01 localhost crond[24552]: pam_unix(crond:session): session closed for user root For messages: - \n Marking my place in the logs \n - Feb 12 10:24:01 localhost crond[24470]: (root) CMD ( /usr/share/msec/promisc_check.sh) Feb 12 10:24:43 localhost sshd[24518]: Failed password for joe from 192.168.0.68 port 34485 ssh2 Feb 12 10:24:46 localhost last message repeated 2 times Feb 12 10:25:01 localhost crond[24553]: (root) CMD ( /usr/share/msec/promisc_check.sh) Failed password for joe from 192.168.0.68 seems pretty clear to me Craig -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: Why does 'ssh' and 'scp' work to one and not another?
. Kitepilot last wrote (in part): If you grant me access to .73 I'll help you debug it over the phone, this could be a long array of issues, and maybe more than 1. Thank you very much. I'll be happy to do that. Please feel free to call me at 480-325-5055. Meanwhile, I will continue to prepare replies to each of the other suggestions/requests I've received. Joe --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: Why does 'ssh' and 'scp' work to one and not another?
Failed password for joe from 192.168.0.68 seems pretty clear to me We have known all along that there is a failed password, but I don't know how to fix that. Both the user and root passwords work to log in to this computer, but the same passwords do not work to log in remotely. I have tried changing the passwords, but the system will not allow me to do so. --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: Why does 'ssh' and 'scp' work to one and not another?
On Fri, 2010-02-12 at 10:45 -0700, j...@actionline.com wrote: Failed password for joe from 192.168.0.68 seems pretty clear to me We have known all along that there is a failed password, but I don't know how to fix that. Both the user and root passwords work to log in to this computer, but the same passwords do not work to log in remotely. I have tried changing the passwords, but the system will not allow me to do so. because 'user' has to satisfy 'rules' for passwords but root does not. if you... sudo 'su -' and then type passwd joe you can enter anything you want for a password and not have to satisfy rules. Craig -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: Why does 'ssh' and 'scp' work to one and not another?
ps aux|grep -i linux getenforce --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: Why does 'ssh' and 'scp' work to one and not another? SOLVED
. I have tried changing the passwords, but the system will not allow me to do so. because 'user' has to satisfy 'rules' for passwords but root does not. if you... sudo 'su -' and then type passwd joe you can enter anything you want for a password and not have to satisfy rules. That has apparently solved the problem. I'll do further checking to be sure and will report back. Thank you. --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: Why does 'ssh' and 'scp' work to one and not another? SOLVED
Glad we got down to the exact details of the issue. Joe, that's the process, much as it seems impersonal, and while you thought your problem was SSH, which was what you were trying to do, it actually was a bad password, which WAS the error message you got! Linux is just like a good domestic or business partner, she will tell you very clearly exactly what is wrong with her! On Fri, Feb 12, 2010 at 11:16 AM, j...@actionline.com wrote: . I have tried changing the passwords, but the system will not allow me to do so. because 'user' has to satisfy 'rules' for passwords but root does not. if you... sudo 'su -' and then type passwd joe you can enter anything you want for a password and not have to satisfy rules. That has apparently solved the problem. I'll do further checking to be sure and will report back. Thank you. --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss -- Skype: (623)239-3392 ATT: (503)754-4452 http://obnosis.110mb.com/nuke/index.php http://uncyclopedia.wikia.com/wiki/Arizona --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: Why does 'ssh' and 'scp' work to one and not another?
. Brian Cluff wrote: Does your joe account on 73 have a restricted or non-shell in the /etc/passwd? Eric Cope wrote: sounds like ssh isn't accessible on 73. Is that true? I guess that must be true. How can I fix that? That is the question. 'sshd_config' is identical on 73 and on 68 where ssh and scp both work (on 68). When I try ssy from 68 to 73, this is the result: $ ssh 192.168.0.73 j...@192.168.0.73's password: Permission denied, please try again. j...@192.168.0.73's password: Permission denied, please try again. j...@192.168.0.73's password: Permission denied (publickey,password,keyboard-interactive). --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: Why does 'ssh' and 'scp' work to one and not another?
On Thu, 2010-02-11 at 06:30 -0700, j...@actionline.com wrote: . Brian Cluff wrote: Does your joe account on 73 have a restricted or non-shell in the /etc/passwd? Eric Cope wrote: sounds like ssh isn't accessible on 73. Is that true? I guess that must be true. How can I fix that? That is the question. 'sshd_config' is identical on 73 and on 68 where ssh and scp both work (on 68). When I try ssy from 68 to 73, this is the result: $ ssh 192.168.0.73 j...@192.168.0.73's password: Permission denied, please try again. j...@192.168.0.73's password: Permission denied, please try again. j...@192.168.0.73's password: Permission denied (publickey,password,keyboard-interactive). I suppose if you really wanted the answer to that question you would have checked the logs like I told you. Craig -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: Why does 'ssh' and 'scp' work to one and not another?
Go to a terminal on 192.168.0.73, login as joe and do: ssh localhost And tell me what happens. And, (as someone said) look at /var/logs/auth.log (or equivalent) on 192.168.0.73 and look for joe: grep joe /var/logs/auth.log ET j...@actionline.com writes: . Brian Cluff wrote: Does your joe account on 73 have a restricted or non-shell in the /etc/passwd? Eric Cope wrote: sounds like ssh isn't accessible on 73. Is that true? I guess that must be true. How can I fix that? That is the question. 'sshd_config' is identical on 73 and on 68 where ssh and scp both work (on 68). When I try ssy from 68 to 73, this is the result: $ ssh 192.168.0.73 j...@192.168.0.73's password: Permission denied, please try again. j...@192.168.0.73's password: Permission denied, please try again. j...@192.168.0.73's password: Permission denied (publickey,password,keyboard-interactive). --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: Why does 'ssh' and 'scp' work to one and not another?
. I have tried every suggest I could so far, with no success. == Brian Cluff wrote: Does your joe account on 73 have a restricted or non-shell in the /etc/passwd? How would I determine the answer to that question? == Eric Cope wrote: sounds like ssh isn't accessible on 73. Is that true? I replied: I guess that must be true. How can I fix that? 'sshd_config' is identical on 73 and on 68 and ssh and scp both work on 68 but neither work on 73. The contents of sshd_config can be viewed at this link: http://www.upquick.com/linux/temp/sshd_config73 == craig white wrote: check the system logs (secure messages) on '73' and you should find your answer. I did examine those logs (17,000 lines in the last 4 days) but I don't know what to look for. I suppose if you really wanted the answer to that question you would have checked the logs like I told you. I've uploaded those two logs (secure messages) here: http://www.upquick.com/linux/temp/secure73 http://www.upquick.com/linux/temp/messages73 == kitepilot wrote: Go to a terminal on 192.168.0.73, login as joe and do: ssh localhost And tell me what happens. And, (as someone said) look at /var/logs/auth.log (or equivalent) on 192.168.0.73 and look for joe: grep joe /var/logs/auth.log When I try: ssh localhost on '73' this is the result: j...@192.168.0.73's password: (I entered the correct user password) Permission denied, please try again. j...@192.168.0.73's password: (I entered the correct root password) Permission denied, please try again. j...@192.168.0.73's password: (I tried just pressing Enter) Permission denied (publickey,password,keyboard-interactive). I've uploaded /var/log/auth.log and the grep joe result here: http://www.upquick.com/linux/temp/auth.log73 -- (10,000 entries) http://www.upquick.com/linux/temp/auth.log73.joe -- (16 entries) I also tried changing the user password on 73 and the system responded that the several passwords that I tried to enter were not acceptable (too short, not enough different characters, etc.) When I do 'ssh localhost' on '68' it asks for a password and accepts the same password that I have set on both '68' and '73' --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: Why does 'ssh' and 'scp' work to one and not another?
How would I determine the answer to that question?
Look at /etc/passwd
Do:
grep joe /etc/passwd
and post the line(s)
I did examine those logs (17,000 lines in the last 4 days)
but I don't know what to look for.
Do:
find /var/log -type f -exec grep -H joe {} \;
And post the output.
Look at line:
Feb 10 18:18:16 localhost su: pam_unix(su:auth): authentication failure;
logname= uid=500 euid=0 tty=pts/1 ruser=joe rhost= user=root
Now, from a console in 73, logged in as joe do:
ssh -v localhost
And post the reply.
Then from the other machine do:
ssh -v 73
And post that too.
ET
ET
j...@actionline.com writes:
.
I have tried every suggest I could so far, with no success.
== Brian Cluff wrote:
Does your joe account on 73 have a restricted
or non-shell in the /etc/passwd?
How would I determine the answer to that question?
== Eric Cope wrote:
sounds like ssh isn't accessible on 73. Is that true?
I replied: I guess that must be true. How can I fix that?
'sshd_config' is identical on 73 and on 68 and ssh and scp
both work on 68 but neither work on 73.
The contents of sshd_config can be viewed at this link:
http://www.upquick.com/linux/temp/sshd_config73
== craig white wrote:
check the system logs (secure messages) on '73'
and you should find your answer.
I did examine those logs (17,000 lines in the last 4 days)
but I don't know what to look for.
I suppose if you really wanted the answer to that
question you would have checked the logs like I told you.
I've uploaded those two logs (secure messages) here:
http://www.upquick.com/linux/temp/secure73
http://www.upquick.com/linux/temp/messages73
== kitepilot wrote:
Go to a terminal on 192.168.0.73, login as joe and do:
ssh localhost
And tell me what happens.
And, (as someone said) look at /var/logs/auth.log (or equivalent)
on 192.168.0.73 and look for joe:
grep joe /var/logs/auth.log
When I try: ssh localhost on '73' this is the result:
j...@192.168.0.73's password: (I entered the correct user password)
Permission denied, please try again.
j...@192.168.0.73's password: (I entered the correct root password)
Permission denied, please try again.
j...@192.168.0.73's password: (I tried just pressing Enter)
Permission denied (publickey,password,keyboard-interactive).
I've uploaded /var/log/auth.log and the grep joe result here:
http://www.upquick.com/linux/temp/auth.log73 -- (10,000 entries)
http://www.upquick.com/linux/temp/auth.log73.joe -- (16 entries)
I also tried changing the user password on 73 and the system
responded that the several passwords that I tried to enter were
not acceptable (too short, not enough different characters, etc.)
When I do 'ssh localhost' on '68' it asks for a password and
accepts the same password that I have set on both '68' and '73'
---
PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
---
PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: Why does 'ssh' and 'scp' work to one and not another?
On Thu, 2010-02-11 at 15:02 -0700, j...@actionline.com wrote: == craig white wrote: check the system logs (secure messages) on '73' and you should find your answer. I did examine those logs (17,000 lines in the last 4 days) but I don't know what to look for. I suppose if you really wanted the answer to that question you would have checked the logs like I told you. I've uploaded those two logs (secure messages) here: http://www.upquick.com/linux/temp/secure73 http://www.upquick.com/linux/temp/messages73 let me see now... you don't want to look at 17,000 lines but I should? Why don't you take this as an opportunity to learn how to solve problems? For example, how to use logs to troubleshoot... run as root echo - \n Marking my place in the logs \n - \ /var/log/secure echo - \n Marking my place in the logs \n - \ /var/log/messages then try to login then look at the logs - after the marks you just made. Craig -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: Why does 'ssh' and 'scp' work to one and not another?
. craig white wrote: let me see now... you don't want to look at 17,000 lines but I should? No, Craig, you definitely should not ... and I am very sorry to have caused you such exasperation toward me. I sincerely appreciate the constructive suggestions that so many helpful friends on the PLUG forum provide and I am just trying to respond to each suggestion with whatever information I can provide as I continue to search for a solution to this problem. --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: Why does 'ssh' and 'scp' work to one and not another?
Responding (as you have been) with EXACT error and screen capture is good. Logs and configurations are great also. # tail /var/log/secure # tail /var/log/messages ssh -version cat /etc/ssh/sshd_config |mail myaddresswhereicanforwardtocraigpersonallyforhelpoffline Craig is usually one of the ones with sufficient help assist experience to get you external to the problem (because your bandwidth or memory/ram are swapping with the level of complexity and you can't think critically) to help compare and dissect the error messages or fix within his experience. You can always directly email me also. I hope you got this figured out? On 2/11/10, j...@actionline.com j...@actionline.com wrote: . craig white wrote: let me see now... you don't want to look at 17,000 lines but I should? No, Craig, you definitely should not ... and I am very sorry to have caused you such exasperation toward me. I sincerely appreciate the constructive suggestions that so many helpful friends on the PLUG forum provide and I am just trying to respond to each suggestion with whatever information I can provide as I continue to search for a solution to this problem. --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss -- Skype: (623)239-3392 ATT: (503)754-4452 http://obnosis.110mb.com/nuke/index.php http://uncyclopedia.wikia.com/wiki/Arizona --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: Why does 'ssh' and 'scp' work to one and not another?
On Thu, 2010-02-11 at 18:47 -0700, j...@actionline.com wrote: . craig white wrote: let me see now... you don't want to look at 17,000 lines but I should? No, Craig, you definitely should not ... and I am very sorry to have caused you such exasperation toward me. I sincerely appreciate the constructive suggestions that so many helpful friends on the PLUG forum provide and I am just trying to respond to each suggestion with whatever information I can provide as I continue to search for a solution to this problem. I'm not sure why you should think I am exasperated with you. I really don't have any investment in your problem. I often find on this list (and maybe some other lists), someone with a problem really has a larger problem than the particular issue of the moment and that is they don't seem to possess the skills to solve problems. Then of course there are people who have trouble discerning which people are offering useful information and which people are just tossing out ideas without much consideration. So I try to teach people the process itself of solving the problem for themselves. In your particular case, I would be surprised if the logs don't tell you exactly what your particular issue is and so the notion of people hurling suggestions at you just becomes a fairly useless exercise that tells you little except what they are guessing might be the problem. I can't see any logic to the idea of guessing when I believe that the system is working as it should and is actually logging the problem. Let's put it another way... On Windows, there is 'Event Viewer' (yes, IIS saves to log files in % SYSTEM ROOT%System 32\Log file and... Macintosh has 'Console' application for viewing logs Linux has /var/log/messages /var/log/secure /var/log/maillog, etc. The first place to look is the logs... doesn't matter what OS you are using. It's the first step of problem solving on any computer. So if you want to keep chasing down everyone's guess, have at it. If you want to solve your particular issue, start with the logs. If you want to actually learn how to manage your own computers, learn the process of solving problems which begins with learning how to look at the logs. Craig -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: Why does 'ssh' and 'scp' work to one and not another?
On Thu, 2010-02-11 at 19:25 -0700, Craig White wrote: On Thu, 2010-02-11 at 18:47 -0700, j...@actionline.com wrote: . craig white wrote: let me see now... you don't want to look at 17,000 lines but I should? No, Craig, you definitely should not ... and I am very sorry to have caused you such exasperation toward me. I sincerely appreciate the constructive suggestions that so many helpful friends on the PLUG forum provide and I am just trying to respond to each suggestion with whatever information I can provide as I continue to search for a solution to this problem. I'm not sure why you should think I am exasperated with you. I really don't have any investment in your problem. I often find on this list (and maybe some other lists), someone with a problem really has a larger problem than the particular issue of the moment and that is they don't seem to possess the skills to solve problems. Then of course there are people who have trouble discerning which people are offering useful information and which people are just tossing out ideas without much consideration. So I try to teach people the process itself of solving the problem for themselves. In your particular case, I would be surprised if the logs don't tell you exactly what your particular issue is and so the notion of people hurling suggestions at you just becomes a fairly useless exercise that tells you little except what they are guessing might be the problem. I can't see any logic to the idea of guessing when I believe that the system is working as it should and is actually logging the problem. Let's put it another way... On Windows, there is 'Event Viewer' (yes, IIS saves to log files in % SYSTEM ROOT%System 32\Log file and... Macintosh has 'Console' application for viewing logs Linux has /var/log/messages /var/log/secure /var/log/maillog, etc. The first place to look is the logs... doesn't matter what OS you are using. It's the first step of problem solving on any computer. So if you want to keep chasing down everyone's guess, have at it. If you want to solve your particular issue, start with the logs. If you want to actually learn how to manage your own computers, learn the process of solving problems which begins with learning how to look at the logs. by the way... the answer is indeed in the logs... I'll give you a hint... it's in the 16 line auth.log Failed password for joe from 192.168.0.68 port 43942 ssh2 Which part of that gives you the most problem and we can break it down further? Craig -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: Why does 'ssh' and 'scp' work to one and not another?
Yes, I usually install the keys and realize that my problem was either a Root Allow = no or strict error checking or no hosts entry with strict error checking, etc. I would just make both sshd_config 's match and copy the old ones to backup. restart the daemon change both passwords start a tcpdump -i eth0 /tmp/dumpfile on the target server do the ssh from the other server get the error message from the logs: (In 5 different window sessions): # tail -f /var/log/auth.log # tail -f /var/log/messages # tail -f /var/log/secure # dmesg go back to the target server and stop the tcpdump with control C # grep ssh /tmp/dumpfile | more Take all that information and shoot it into an email and send me or Craig offline please? On 2/11/10, Craig White craigwh...@azapple.com wrote: On Thu, 2010-02-11 at 19:25 -0700, Craig White wrote: On Thu, 2010-02-11 at 18:47 -0700, j...@actionline.com wrote: . craig white wrote: let me see now... you don't want to look at 17,000 lines but I should? No, Craig, you definitely should not ... and I am very sorry to have caused you such exasperation toward me. I sincerely appreciate the constructive suggestions that so many helpful friends on the PLUG forum provide and I am just trying to respond to each suggestion with whatever information I can provide as I continue to search for a solution to this problem. I'm not sure why you should think I am exasperated with you. I really don't have any investment in your problem. I often find on this list (and maybe some other lists), someone with a problem really has a larger problem than the particular issue of the moment and that is they don't seem to possess the skills to solve problems. Then of course there are people who have trouble discerning which people are offering useful information and which people are just tossing out ideas without much consideration. So I try to teach people the process itself of solving the problem for themselves. In your particular case, I would be surprised if the logs don't tell you exactly what your particular issue is and so the notion of people hurling suggestions at you just becomes a fairly useless exercise that tells you little except what they are guessing might be the problem. I can't see any logic to the idea of guessing when I believe that the system is working as it should and is actually logging the problem. Let's put it another way... On Windows, there is 'Event Viewer' (yes, IIS saves to log files in % SYSTEM ROOT%System 32\Log file and... Macintosh has 'Console' application for viewing logs Linux has /var/log/messages /var/log/secure /var/log/maillog, etc. The first place to look is the logs... doesn't matter what OS you are using. It's the first step of problem solving on any computer. So if you want to keep chasing down everyone's guess, have at it. If you want to solve your particular issue, start with the logs. If you want to actually learn how to manage your own computers, learn the process of solving problems which begins with learning how to look at the logs. by the way... the answer is indeed in the logs... I'll give you a hint... it's in the 16 line auth.log Failed password for joe from 192.168.0.68 port 43942 ssh2 Which part of that gives you the most problem and we can break it down further? Craig -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss -- Skype: (623)239-3392 ATT: (503)754-4452 http://obnosis.110mb.com/nuke/index.php http://uncyclopedia.wikia.com/wiki/Arizona --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Why does 'ssh' and 'scp' work to one and not another?
. Why does 'ssh' and 'scp' work to one and not another? $ scp testm2p j...@192.168.0.68:/home/joe/ -- This works to computer 68 on my network But why does the following not work to computer 73? Both have sshd started. $ scp testm2p j...@192.168.0.73:/home/joe/ Warning: Permanently added '192.168.0.73' (RSA) to the list of known hosts. j...@192.168.0.73's password: Permission denied, please try again. j...@192.168.0.73's password: Connection closed by 192.168.0.73 lost connection == I also tried this (which works to 68) and it also does not work to 73. $ ssh 192.168.0.73 j...@192.168.0.73's password: Permission denied, please try again. What do I need to fix to get these both to work? --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: Why does 'ssh' and 'scp' work to one and not another?
On Wed, 2010-02-10 at 12:06 -0700, Josef Lowder wrote: . Why does 'ssh' and 'scp' work to one and not another? $ scp testm2p j...@192.168.0.68:/home/joe/ -- This works to computer 68 on my network But why does the following not work to computer 73? Both have sshd started. $ scp testm2p j...@192.168.0.73:/home/joe/ Warning: Permanently added '192.168.0.73' (RSA) to the list of known hosts. j...@192.168.0.73's password: Permission denied, please try again. j...@192.168.0.73's password: Connection closed by 192.168.0.73 lost connection == I also tried this (which works to 68) and it also does not work to 73. $ ssh 192.168.0.73 j...@192.168.0.73's password: Permission denied, please try again. What do I need to fix to get these both to work? check the system logs (secure messages) on '73' and you should find your answer. Craig -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: Why does 'ssh' and 'scp' work to one and not another?
What's in /etc/ssh/sshd_config of both boxes? ET Josef Lowder writes: . Why does 'ssh' and 'scp' work to one and not another? $ scp testm2p j...@192.168.0.68:/home/joe/ -- This works to computer 68 on my network But why does the following not work to computer 73? Both have sshd started. $ scp testm2p j...@192.168.0.73:/home/joe/ Warning: Permanently added '192.168.0.73' (RSA) to the list of known hosts. j...@192.168.0.73's password: Permission denied, please try again. j...@192.168.0.73's password: Connection closed by 192.168.0.73 lost connection == I also tried this (which works to 68) and it also does not work to 73. $ ssh 192.168.0.73 j...@192.168.0.73's password: Permission denied, please try again. What do I need to fix to get these both to work? --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: Why does 'ssh' and 'scp' work to one and not another?
Does your joe account on 73 have a restricted or non-shell in the /etc/passwd? Brian Cluff Josef Lowder wrote: . Why does 'ssh' and 'scp' work to one and not another? $ scp testm2p j...@192.168.0.68:/home/joe/ -- This works to computer 68 on my network But why does the following not work to computer 73? Both have sshd started. $ scp testm2p j...@192.168.0.73:/home/joe/ Warning: Permanently added '192.168.0.73' (RSA) to the list of known hosts. j...@192.168.0.73's password: Permission denied, please try again. j...@192.168.0.73's password: Connection closed by 192.168.0.73 lost connection == I also tried this (which works to 68) and it also does not work to 73. $ ssh 192.168.0.73 j...@192.168.0.73's password: Permission denied, please try again. What do I need to fix to get these both to work? --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: Why does 'ssh' and 'scp' work to one and not another?
sounds like ssh isn't accessible on 73. Is that true? On Wed, Feb 10, 2010 at 8:46 PM, Brian Cluff br...@snaptek.com wrote: Does your joe account on 73 have a restricted or non-shell in the /etc/passwd? Brian Cluff Josef Lowder wrote: . Why does 'ssh' and 'scp' work to one and not another? $ scp testm2p j...@192.168.0.68:/home/joe/ -- This works to computer 68 on my network But why does the following not work to computer 73? Both have sshd started. $ scp testm2p j...@192.168.0.73:/home/joe/ Warning: Permanently added '192.168.0.73' (RSA) to the list of known hosts. j...@192.168.0.73's password: Permission denied, please try again. j...@192.168.0.73's password: Connection closed by 192.168.0.73 lost connection == I also tried this (which works to 68) and it also does not work to 73. $ ssh 192.168.0.73 j...@192.168.0.73's password: Permission denied, please try again. What do I need to fix to get these both to work? --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss -- Eric Cope http://cope-et-al.com --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
