SSH woes

2007-02-02 Thread Arindam
I have a Pentium III 733 Mhz box with 512 MB RAM running FreeBSD 6.1. I also have a second box with Fedora Core 2. I tried connecting to my FreeBSD box using ssh from my Fedora Core 2 machine. # ssh -l root myFreeBSD box Password: Password: Password: It kept asking me for Password: although

Re: SSH woes

2007-02-02 Thread usleepless
Arindam, On 2/2/07, Arindam [EMAIL PROTECTED] wrote: I have a Pentium III 733 Mhz box with 512 MB RAM running FreeBSD 6.1. I also have a second box with Fedora Core 2. I tried connecting to my FreeBSD box using ssh from my Fedora Core 2 machine. # ssh -l root myFreeBSD box Password: Password:

Re: SSH woes

2007-02-02 Thread Vince
Arindam wrote: I have a Pentium III 733 Mhz box with 512 MB RAM running FreeBSD 6.1. I also have a second box with Fedora Core 2. I tried connecting to my FreeBSD box using ssh from my Fedora Core 2 machine. # ssh -l root myFreeBSD box Password: Password: Password: It kept asking me

Re: SSH woes

2007-02-02 Thread cknipe
# ssh -l root myFreeBSD box Password: Password: Password: It kept asking me for Password: although everytime I put the correct value. I tried out clearing the .ssh* files in my home directories and trying to reconnect. None of it worked. Don't login as root... It's not good practise,

Re: SSH woes

2007-02-02 Thread Jeffrey Belles
On Fri, 2 Feb 2007 18:37:14 +0530, Arindam wrote I have a Pentium III 733 Mhz box with 512 MB RAM running FreeBSD 6.1. I also have a second box with Fedora Core 2. I tried connecting to my FreeBSD box using ssh from my Fedora Core 2 machine. # ssh -l root myFreeBSD box Password: Password:

Re: SSH woes

2007-02-02 Thread Brian A. Seklecki
Don't login as root... It's not good practise, SSH on BSD by default does also not allow for it. Add your normal user to the wheel group, use that to login The top Linux distros screw up a bunch of the ssh_config(5) and sshd_config(5) defaults. ~BAS

SSH woes

2003-03-17 Thread John Straiton
I continue to have problems with SSH authentication. The behavior is outside the normal I'm used to. Here's what's going on: I'm trying to ssh from MACHINE1 to MACHINE2 as user testuser. Now here's the funny thing: su Password: MACHINE1# ssh 209.198.xxx.xxx -l testuser Password: Last login:

RE: SSH woes

2003-03-17 Thread John Straiton
I continue to have problems with SSH authentication. The behavior is outside the normal I'm used to. Here's what's going on: I'm trying to ssh from MACHINE1 to MACHINE2 as user testuser. Now here's the funny thing: su Password: MACHINE1# ssh 209.198.xxx.xxx -l testuser

Re: SSH woes

2003-03-17 Thread Edmond Baroud
do you have /root/.ssh/config ? you have skipped this part when pasting your verbose connection with root, I'm just curious. maybe when you're connecting with root, its reading its options from $HOME/.ssh/options + u're specifying -l testuser and from testuser's shell it's reading

RE: SSH woes

2003-03-17 Thread John Straiton
do you have /root/.ssh/config ? No. Between both machines, no files exist in any /root/.ssh or ~/.ssh directory other than known_hosts which apparently is fine based on the verbose logging. For completeness, I'm including the full root connection verbose log. if u dont, could u paste your env

Re: SSH woes

2003-03-17 Thread Edmond Baroud
this doesn't help much :) - su testuser; env this does - su - testuser;env Ed. On Mon, 17 Mar 2003 12:50:52 -0500 John Straiton [EMAIL PROTECTED] wrote: do you have /root/.ssh/config ? No. Between both machines, no files exist in any /root/.ssh or ~/.ssh directory other than known_hosts

RE: SSH woes

2003-03-17 Thread John Straiton
: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Straiton Sent: Monday, March 17, 2003 11:33 AM To: [EMAIL PROTECTED] Subject: SSH woes I continue to have problems with SSH authentication. The behavior is outside the normal I'm used to. Here's what's going on: I'm trying

RE: SSH woes

2003-03-17 Thread John Straiton
: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Straiton Sent: Monday, March 17, 2003 2:14 PM To: [EMAIL PROTECTED] Subject: RE: SSH woes (Problem solved, still confused as to why it didn't work) As a follow up to my own post, I created a new user testing and tried