's Topics:
1. Re: SSH Problem (funtom)
2. RE: rh9 samba + ldap NOT THERE (Toby Schaefer)
3. Re: Trouble With APT (Joe Giles)
4. RE: Trying to recover MRTG (Nick White)
5. RE: Dual boot configuration (again) (Matthew Saltzman)
6. RE: Dual boot configuration (again) (Matthew
: Rich Lichvar
Subject: Re: SSH Problem
I believe the protocol version defaults differ, used to be 1,2 in config and
is either 2,1 or 2 by default now (I compile my own so am not 100% sure of
distribution defaults). You can probably force the version to either and get
it to work.. another
alhost -l root" as loopback test.
>
> regards,
> thomas
> - Original Message -
> From: "Rich Lichvar" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Friday, June 06, 2003 11:03 PM
> Subject: SSH Problem
>
> > Got a new 9.0
Hi,
If you use "ssh -v hostname -l username", you have more output...
or you can make "ssh -v localhost -l root" as loopback test.
regards,
thomas
- Original Message -
From: "Rich Lichvar" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: F
Got a new 9.0 installation on which SSH seems to be acting up. (Yes, the
service is started.) It seems we can reach it from Windows machines using,
for example, VanDyke's SecureFX and SecureCRT, but when we try to access it
from other Linux machines (RH 7.3 in our case) using SSH/SCP, the connectio
Hi
I have a problem that i think is pam related,
If i log in and get the password correct on the first attempt it lets me
in. however, if i get the password wrong, even if i get it correct on
the next two attempts it still fails to let me in. (If i enter no
password the first time and then enter
On Wed, 2002-11-13 at 09:55, Rune Berge wrote:
>
> When I log into my linux box via ssh, some characters are displayed
> incorrectly.
...
> Example from "man grep":
> grep [options] [−e PATTERN | −f FILE] [FILE...]
Your terminal is not configured to interpret UTF-8 characters. I don't
know
On Thu, 14 Nov 2002, Teodor Georgiev wrote:
> > On Wed, 2002-11-13 at 12:55, Rune Berge wrote:
> > >
> > > When I log into my linux box via ssh, some characters are displayed
> > > incorrectly. This does not happen when I'm working directly on the
> > > machine. Does anybody know what might be ca
this the below lines in your .bashrc file at the bottom.
LANG=c
export LANG
- Original Message -
From: "Rune Berge" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, November 13, 2002 12:55 PM
Subject: SSH problem
>
> When I log into my linux box
I am using SecureCRT and I have the same issue.
-Original Message-
From: Rune Berge [mailto:rune@;krokodille.com]
Sent: Wednesday, November 13, 2002 1:45 PM
To: RedHat List
Subject: Re: SSH problem
On 13 Nov 2002, Jerry Sloan wrote:
> On Wed, 2002-11-13 at 12:55, Rune Berge wr
- Original Message -
From: "Jerry Sloan" <[EMAIL PROTECTED]>
To: "RedHat List" <[EMAIL PROTECTED]>
Sent: Wednesday, November 13, 2002 8:16 PM
Subject: Re: SSH problem
> On Wed, 2002-11-13 at 12:55, Rune Berge wrote:
> >
> > When I log
On 13 Nov 2002, Jerry Sloan wrote:
> On Wed, 2002-11-13 at 12:55, Rune Berge wrote:
> >
> > When I log into my linux box via ssh, some characters are displayed
> > incorrectly. This does not happen when I'm working directly on the
> > machine. Does anybody know what might be causing this?
> >
> >
Thanks to Emmanuel for the suggestion on getting ssh for my older version
(6.2). I got the pcmcia problem solved and already used RH 7.2 and ssh to
work on the server this afternoon. I got into the setup on the Toshiba
laptop, there was a section about setting up the pc card slots and it had 3
c
On 12 Jun 2002, Gordon Messmer wrote:
> On Wed, 2002-06-12 at 18:32, Keith Morse wrote:
> >
> >
> > >From the openssh 3.1 documentation. For the interim, I've been symlinking
> > authorized_keys to authorized_keys2.
> >
> > ln -s authorized_keys authorized_keys2
>
> Yeah, but why? Open
On Wed, 2002-06-12 at 18:32, Keith Morse wrote:
>
>
> >From the openssh 3.1 documentation. For the interim, I've been symlinking
> authorized_keys to authorized_keys2.
>
> ln -s authorized_keys authorized_keys2
Yeah, but why? Openssh 3.0 and better look in authorized_keys, so the
auth
Thanks for the info! I have done the same :)
-Jon "GenKiller" Gaudette
Keith Morse wrote:
On Thu, 13 Jun 2002, Jon Gaudette wrote:
May I ask where you have gotten this information from?
-Jon "GenKiller" Gaudette
>From the openssh 3.1 documentation. For the interi
On Thu, 13 Jun 2002, Jon Gaudette wrote:
> May I ask where you have gotten this information from?
>
> -Jon "GenKiller" Gaudette
>
>From the openssh 3.1 documentation. For the interim, I've been symlinking
authorized_keys to authorized_keys2.
ln -s authorized_keys authorized_keys2
On 12 Jun 2002, Gordon Messmer wrote:
> On Wed, 2002-06-12 at 16:32, Keith Morse wrote:
> > On 12 Jun 2002, Javier Gostling wrote:
> >
> > > On Wed, 2002-06-12 at 17:58, Gordon Messmer wrote:
> > > > Update if you can, use only DSA keys, and store them in
> > > > .ssh/authorized_keys.
> > >
> >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jon Gaudette wrote:
> A tangent here; I note that the man page makes no mention of
>authorized_keys2, but that file is still consulted for now. For those
>not aware of this, authorized_keys2 is being phased out. Anyone using
>authorized_keys2 shoul
May I ask where you have gotten this information from?
-Jon "GenKiller" Gaudette
David Talkington wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gordon Messmer wrote:
Update if you can, use only DSA keys, and store them in
.ssh/authorized_keys.
A tangent here;
On Wed, 2002-06-12 at 16:32, Keith Morse wrote:
> On 12 Jun 2002, Javier Gostling wrote:
>
> > On Wed, 2002-06-12 at 17:58, Gordon Messmer wrote:
> > > Update if you can, use only DSA keys, and store them in
> > > .ssh/authorized_keys.
> >
> > What's wrong with RSA keys?
>
> And protocol 2 for
On Wed, 2002-06-12 at 15:42, Javier Gostling wrote:
> On Wed, 2002-06-12 at 17:58, Gordon Messmer wrote:
> > Update if you can, use only DSA keys, and store them in
> > .ssh/authorized_keys.
>
> What's wrong with RSA keys?
Some people doubt that RSA will continue to be a strong cryptographic
alg
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gordon Messmer wrote:
>Update if you can, use only DSA keys, and store them in
>.ssh/authorized_keys.
A tangent here; I note that the man page makes no mention of
authorized_keys2, but that file is still consulted for now. For those
not aware of th
On 12 Jun 2002, Javier Gostling wrote:
> On Wed, 2002-06-12 at 17:58, Gordon Messmer wrote:
> > Update if you can, use only DSA keys, and store them in
> > .ssh/authorized_keys.
>
> What's wrong with RSA keys?
And protocol 2 for that matter?
___
Re
On Wed, 2002-06-12 at 17:58, Gordon Messmer wrote:
> Update if you can, use only DSA keys, and store them in
> .ssh/authorized_keys.
What's wrong with RSA keys?
--
Javier Gostling
Ingeniero de Sistemas
Virtualia S.A.
[EMAIL PROTECTED]
Fono: +56 (2) 202-6264 x 130
Fax: +56 (2) 342-8763
Av. Kenn
On Wed, 2002-06-12 at 13:23, [EMAIL PROTECTED] wrote:
> that it is all I have to do to work it, However, here is the error that I
> got:
...
> The authenticity of host 'node-a (192.168.58.201)' can't be established.
> RSA key fingerprint is 2c:31:1e:22:28:7a:af:e0:93:a8:b1:55:85:e4:4c:3d.
> Are
call the authorized_keys file authorized_keys2
say "yes" at that point as long as your are sure that it is the server you
are trying to connect to.
-Jon "GenKiller" Gaudette
[EMAIL PROTECTED] wrote:
Hi I'm very confused because I can't get that my ssh work with the
authorized_keys f
Edward Marczak wrote:
>
> On 2/14/02 7:59 AM, "Janyne Kizer" [EMAIL PROTECTED] pressed the keys
> forming the message:
>
> > The thing is, I have four servers that are set up exactly the same way
> > (copied from tape) and three of them work fine. This one does not. I
> > have confirmed that t
On 2/14/02 7:59 AM, "Janyne Kizer" [EMAIL PROTECTED] pressed the keys
forming the message:
> The thing is, I have four servers that are set up exactly the same way
> (copied from tape) and three of them work fine. This one does not. I
> have confirmed that the files in /etc/ssh are exactly the
The thing is, I have four servers that are set up exactly the same way
(copied from tape) and three of them work fine. This one does not. I
have confirmed that the files in /etc/ssh are exactly the same size and
date. I thought that was were the configuration info for SSH was stored
but maybe n
On Wed, 2002-02-13 at 12:34, Janyne Kizer wrote:
> The line "debug1: authentications that can continue: " was interesting
> to me because the "good" server says "debug1: authentications that can
> continue: publickey,password" the first time thate message is displayed.
>
> [root@firstserver root]
The line "debug1: authentications that can continue: " was interesting
to me because the "good" server says "debug1: authentications that can
continue: publickey,password" the first time thate message is displayed.
[root@firstserver root]# ssh -v servername
OpenSSH_2.9p2, SSH protocols 1.5/2.0, O
On 2/12/02 2:45 PM, "Janyne Kizer" [EMAIL PROTECTED] pressed the keys
forming the message:
> hmmm, I am having a similar problem.
>
> What does "Authenticated with partial success" mean?
Dunno - could it be failing it's first auth type, and falling back to the
next (e.g. Trying ssh2, then falli
hmmm, I am having a similar problem.
What does "Authenticated with partial success" mean? I installed three
(they were installed here and then put in place at the beta sites within
on Friday and Monday) beta servers in the past two days and two of them
SSH fine but one is giving us grief. I c
On 2/11/02 12:52 AM, "Maynard B. Fernando" [EMAIL PROTECTED] pressed the
keys forming the message:
> still the same sir... PASSWORD AUTHENTICATION FAILED
> error but for sure, im entering the correct password...
>
> note: all of these conditions are followed
> 1. all three servers use the same v
differ on the three servers;
4. using the same client to try to connect to all three servers.
- Original Message -
From: "David Talkington" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, February 11, 2002 1:41 PM
Subject: Re: ssh problem (was: error)
&
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Talkington wrote:
>Then I will suspect that on the server to which you cannot connect,
>you chose to use a firewall during install, and that is preventing you
>from connecting. If you are safely isolated from hostile networks,
>then do this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Maynard B. Fernando wrote:
>i say so because i can ssh to server1 and server2 but
>not in server3 that's why i think its only a misconfig
>in server3...
Ah. As you see, detail is good. Then I shall assume, based on what
you've told us so far:
1.
to my knowledge yes... is that what is looks like to you ??? maybe I missed
a option in the compile statement... although I did include the pam stuff...
I'll try recompiling it...
is there anything special I should have included besides PAM?
Dave
At 01:20 AM 1/20/2002 -0800, you wrote:
>-BE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dave Lewis wrote:
>I recently upgraded from the version of ssh that comes with Redhat 6.2 to
>SSH-1.5-OpenSSH_3.0.2p1
>I had everything working normally before the upgrade... I took the source
>for 3.0.2p1 and compiled
>and installed... now nobody
I recently upgraded from the version of ssh that comes with Redhat 6.2 to
SSH-1.5-OpenSSH_3.0.2p1
I had everything working normally before the upgrade... I took the source
for 3.0.2p1 and compiled
and installed... now nobody can authenticate...
This is an example of what the log shows when some
On Sat, 30 Sep 2000, Chuck Mead wrote:
>
> Either you've been lied to or the folks telling you do not know what
> they're talking about.
>
The version I downloaded from the OpenBSD site did NOT
interface with the scp functionality from the "real"
Windows SSH client 'Course this was a few wee
Chuck Mead wrote:
> On Sat, 30 Sep 2000, John Aldrich spewed into the bitstream:
>
> JA>On Fri, 29 Sep 2000, Chuck Milam wrote:
> JA>>
> JA>> Eh? Could you explain this a bit further? What scp functionality does
> JA>> OpenSSH not have?
> JA>>
> JA>The windows SSH client has a built-in SCP clie
On Sat, 30 Sep 2000, John Aldrich spewed into the bitstream:
JA>On Fri, 29 Sep 2000, Chuck Milam wrote:
JA>>
JA>> Eh? Could you explain this a bit further? What scp functionality does
JA>> OpenSSH not have?
JA>>
JA>The windows SSH client has a built-in SCP client. So does
JA>the "real" SSH se
On Sat, 30 Sep 2000, Mikkel L. Ellertson wrote:
> I am not sure about using the .tar source files and compiling it
> yourself, but if you use the .src.rpm file, and compile if yourself, or
> use the pre-compiled rpms, scp is included. scp is a seperate command
> from ssh, but both commands are i
On Sat, 30 Sep 2000, John Aldrich wrote:
> On Fri, 29 Sep 2000, Chuck Milam wrote:
> >
> > Eh? Could you explain this a bit further? What scp functionality does
> > OpenSSH not have?
> >
> The windows SSH client has a built-in SCP client. So does
> the "real" SSH server for linux. OpenSSH doe
On Fri, 29 Sep 2000, Chuck Milam wrote:
>
> Eh? Could you explain this a bit further? What scp functionality does
> OpenSSH not have?
>
The windows SSH client has a built-in SCP client. So does
the "real" SSH server for linux. OpenSSH doesn't have that
built-in. It's an add-on that you have to
On Fri, 29 Sep 2000, John Aldrich wrote:
> NO THANKS! It doesn't have the same functionality as the "real" SSH.
> I've tried that at home due to some problems with the "real" SSH. I
> talked to an SSH rep at Networld+Interop and was told there was a bug
> in the version I was likely running. The
On Fri, 29 Sep 2000, Jonathan Wilson wrote:
> That's certainly NOT the first b0rked src.rpm of ssh I've ever had :-)
>
> They seem to regularly mess up their src.rpms. What's the deal on that?
>
> Try OpenSSH. I find it hard to belive the tar.gz works when the src.rpm doesn't.
>
I'm sorry, but
On Fri, 29 Sep 2000, Nic Steussy wrote:
> Actually, I just installed the tarball (ssh-1.2.30.tar.gz) on multiple
> machines ( 8 x SGI, 5 x Tru64Unix, 3 x Linux RH6.2 ). It all worked
> fine. But be careful about ownership and permissions of sshd.
>
Thanks. I think I'll try that...
John
On Fri, 29 Sep 2000, Jeff Hogg wrote:
> Is /bin in your current path? type echo $PATH at the prompt to check. If
> not, you need to add it to do this. Thats about all I can imagine would
> cause that.. Are you compiling as root or a normal user?
>
I'm pretty sure /bin is in my current path, e
On Fri, 29 Sep 2000, Gordon Messmer wrote:
> If it builds, but fails to install, then use the --nodeps flag when
> installing. Otherwise, use openssh (http://www.openssh.com)
>
Ah. Why didn't I think of that. :-) Thanks. (And OpenSSH is
NOT an option as far as I"m concerned... see my previous
ra
On Fri, 29 Sep 2000, Mr FW User wrote:
>
> That's a bad thing. If you're worried about security
> (and obviously you are if you're using ssh) then make
> sure to upgrade many packages which were found to be
> vulnerable in RH62.
>
I know. I'm behind a firewall at work and am NAT-ed behind
an ISDN
PROTECTED]
>From: John Aldrich <[EMAIL PROTECTED]>
>Organization: Chattanooga Online Internet
>To: [EMAIL PROTECTED]
>Subject: ssh problem
>Date: Fri, 29 Sep 2000 13:22:53 -0400
>X-Mailer: KMail [version 1.0.29]
>X-MIME-Autoconverted: from quoted-printable to 8bit by mail.re
Actually, I just installed the tarball (ssh-1.2.30.tar.gz) on multiple
machines ( 8 x SGI, 5 x Tru64Unix, 3 x Linux RH6.2 ). It all worked
fine. But be careful about ownership and permissions of sshd.
duke out
John Aldrich wrote:
>
> I know this would probably be better on the ssh list, but t
On Fri, 29 Sep 2000, John Aldrich wrote:
> The problem is that it errors out thinking it can't find /bin/sh, and
> it's clearly there... I even deleted it and copied /bin/bash to
> /bin/sh to avoid a symlink in case the symlink was fooling it somehow!
If it builds, but fails to install, then use
> Anyway, here's my question. I've got RH 6.2 (mostly
> stock... no major upgrades or anything) and I'm
That's a bad thing. If you're worried about security
(and obviously you are if you're using ssh) then make
sure to upgrade many packages which were found to be
vulnerable in RH62.
> Any ideas
-Original Message-
From: John Aldrich <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Friday, September 29, 2000 3:34 PM
Subject: ssh problem
>I know this would probably be better on the ssh list, but that list
>is SOOO slow and so busy, I'
I know this would probably be better on the ssh list, but that list
is SOOO slow and so busy, I'd rather not re-sub to that list, if at
all possible...
Anyway, here's my question. I've got RH 6.2 (mostly stock... no major
upgrades or anything) and I'm trying to recompile the SRC.RPM file
for SSH-
I've got OpenSSH installed on my RedHat 6.2 machine. I
installed it because I was only able to connect via SSH1
client from my Windows box. Now, I'm able to SSH in and get
a console. However, I can no longer do secure file
transfers. While this isn't really an issue from my local
lan, I'd *like* t
Update:
I installed all the OpenSSH stuff (after recompiling) and
it all seems to work fine now. Maybe I had a corrupt config
file or a corrupt host key or something, but it wasn't
working with SSH2 from SSH.COM, so. :-)
John
___
Redhat-li
On Mon, 04 Sep 2000, Angel L. Mateo wrote:
> First, you can try to copy your public key into the linux
> box, but to the ssh2 directory. This could be one reason of problem.
>
I read the same FAQ you probably got this from. It didn't
work. :-(
> If this does not solve the problem, t
El día Sun, 3 Sep 2000 14:19:23 -0400 John Aldrich escribió:
> I've got a problem with SSH -- I've got the SSH for windows
> client and my linux box is running ssh2 (also has ssh1
> capability.)
>
> Now all of a sudden, I can't log into my linux box with ssh
> any more from any of the machines
I've got a problem with SSH -- I've got the SSH for windows
client and my linux box is running ssh2 (also has ssh1
capability.)
Now all of a sudden, I can't log into my linux box with ssh
any more from any of the machines on my lan. It gives me an
authentication error and then another box pops u
On Thu, 2 Dec 1999, Fallout wrote:
> is there a seperate rpm for sshd?
Yes.
> I looked on freshmeat, but didn't find
> any sshd daemon. Where should I go now?
ftp://ftp.redhat.de/pub/rh-addons/security/RPMS
LLaP
bero
--
Nobody will ever need more than 640 kB RAM.
-- Bill Ga
On Thu, 2 Dec 1999, Bernhard Rosenkraenzer wrote:
> You need to start the ssh server.
> /etc/rc.d/init.d/sshd start
There is no sshd in that directory.
I installed:
ssh-1.2.27-5us
is there a seperate rpm for sshd? I looked on freshmeat, but didn't find
any sshd daemon. Where should I go now?
On Thu, 2 Dec 1999, Fallout wrote:
> I installed the ssh rpms, everything went find, but when I try to ssh in,
> it gives me this:
>
> Secure connection to 192.168.0.4 refused; reverting to insecure method.
> Rsh not available.
You need to start the ssh server.
/etc/rc.d/init.d/sshd start
LLaP
On Thu, Dec 02, 1999 at 02:38:22AM -0800, Fallout wrote:
> I installed the ssh rpms, everything went find, but when I try to ssh in,
> it gives me this:
>
> Secure connection to 192.168.0.4 refused; reverting to insecure method.
> Rsh not available.
>
> and dumps me back to my shell.
>
Probabl
I installed the ssh rpms, everything went find, but when I try to ssh in,
it gives me this:
Secure connection to 192.168.0.4 refused; reverting to insecure method.
Rsh not available.
and dumps me back to my shell.
?
tia.
/me
-
Mike Erickson <[EMAI
69 matches
Mail list logo
