openpty : no such file or directory error

[Sriram Chadalavada]

Hi everyone,
   Its been a while since I continued work with
dropbear on my uClinux 2.4.24(Arcturus uCdimm -
Motorola M68VZ328) with uClibc compilation.

I now have it working as a daemon. And a SSH client
seems to connect to it(though Diffie Helman exchange
on the 33MHz uCdimm takes about 8-10 mins).

But the password is not authenticated. On turning on
-E option, I found:

[38] Nov 30 00:09:57 pty_allocate: openpty: No such
file or directory
(invoked in sshpty.c)

My relevant kernel options are:
CONFIG_UNIX98_PTYS=y
CONFIG_UNIX98_PTY_COUNT=256
CONFIG_DEVPTS_FS=y

and the config.h file is:

/* Have openpty() function */
#define HAVE_OPENPTY 1
/* Define to 1 if you have the <pty.h> header file. */
#define HAVE_PTY_H  1

/* Define to 1 if you have the `_getpty' function. */
#define HAVE__GETPTY 1
/* Use /dev/ptmx */
#undef USE_DEV_PTMX

Any suggestions to solve this problem would be most
welcome.

Thanks in advance,
Sriram

--- Matt Johnston <matt at ucc.asn.au> wrote:

> On Tue, Dec 28, 2004 at 05:14:10PM -0800, Sriram
> Chadalavada wrote:
> > I have cross-compiled dropbear as a MULTI and
> STATIC
> > program and use a symbolic link dropbear. The DSS
> host
> > key has been put into /etc/dropbear(appropriate
> > location) of the uCdimm filesystem.
> > The application has been compiled to execute under
> > inetd control. 
> > 
> > My problem is that when I try connecting to the
> board
> > using ssh, I get the message:
> > 
> > [root at dhcp001 uClinux-dist]# ssh
> root at 129.237.125.90
> > ssh_exchange_identification: Connection closed by
> > remote host
> 
> Does your system have syslog available? If so, could
> you
> have a look at the logs and see what error message
> Dropbear
> is giving? 
> 
> If syslog isn't available, the best bet is probably
> to
> compile Dropbear to try and run standalone (not from
> inetd),
> and run it with '-F -E' flags so that logging
> information is
> written to your terminal. (I'm not entirely sure if
> this
> will work with uClibc - you might want to remove the
> "fork()" from svr-main.c).
> 
> If the logging information doesn't give any hints,
> you can
> enable DEBUG_TRACE in debug.h, which will spit out
> very
> verbose debugging information. (Note that this will
> probably
> cause problems if you run from inetd).
> 
> Let me know how it goes.
> 
> Matt
> 
> 



		
__________________________________ 
Do you Yahoo!? 
The all-new My Yahoo! - What will yours do?
http://my.yahoo.com