* Kurt Lieber ([EMAIL PROTECTED]) spake thusly:
> On Monday 03 December 2001 05:35 pm, Dimitri Maziuk wrote:
> > Kurt, check your ssh_config (not sshd_config) and see if you have
> > "Protocol" line in it. We had an ssh client on one of our DeadRat
> > boxen that wouldn't connect to anything until
On Mon, Dec 03, 2001 at 04:21:12PM -0800, Cassandra Lynette Ludwig wrote:
> The latest implementation uses one keyfile for both protocols, but at the
> moment as far as I know, the latest version is yet to hit even unstable in
> Debian. (Good choice in my opinion... let's see how it works before
Kurt Lieber([EMAIL PROTECTED]) is reported to have said:
> On Monday 03 December 2001 05:35 pm, Dimitri Maziuk wrote:
> > Kurt, check your ssh_config (not sshd_config) and see if you have
> > "Protocol" line in it. We had an ssh client on one of our DeadRat
> > boxen that wouldn't connect to anythi
On Monday 03 December 2001 05:35 pm, Dimitri Maziuk wrote:
> Kurt, check your ssh_config (not sshd_config) and see if you have
> "Protocol" line in it. We had an ssh client on one of our DeadRat
> boxen that wouldn't connect to anything until I removed the
> "Protocol 2,1" line (repeat, this is in
* Kurt Lieber ([EMAIL PROTECTED]) spake thusly:
> On Monday 03 December 2001 05:06 pm, Cassandra Lynette Ludwig wrote:
>
> > Okay, that looks like there is a problem with permissions or some such on
> > the files... I'll check my file permissions...
> >
> > Okay, here is the permission list from m
On Monday 03 December 2001 05:06 pm, Cassandra Lynette Ludwig wrote:
> Okay, that looks like there is a problem with permissions or some such on
> the files... I'll check my file permissions...
>
> Okay, here is the permission list from my /etc/ssh directory
[snip]
Yep -- those match my permissio
One more thing, you are running this as the root user are you not?
Because SSHD is not normally suid and sgid root, so it cannot access those
files unless you are the root user.
Regards,
Cassandra
On Mon, 3 Dec 2001, Kurt Lieber wrote:
> Thanks for the response.
No problems - I got the error myself when I upgraded, and it annoyed me
considerably because I have been using SSH V2 for a while to get back to
my server in Australia from the US.
> I tried that, but it's still not working. H
Thanks for the response. I tried that, but it's still not working. However,
now I get a different error message when I execute /usr/sbin/sshd -d -d:
debug1: Seeding random number generator
debug1: sshd version OpenSSH_2.9p2
debug1: private host key: #0 type 0 RSA1
debug1: PEM_read_PrivateKey fa
Kurt - I just signed up this week to the mailing list, so I wasn't around
to respond last week.
The problem you are having is due to the new implementation of SSHD for
woody. What you need to do is modify the /etc/ssh/sshd_config file to
include the dsa key... to do this the following needs to
10 matches
Mail list logo
