That is what I needed to do. I am running dropbear in a "jail" and
/dev/pts was not being mounted correctly. It was there but I guess it
was not working correctly. I know almost nothing about how devpts is
used by ssh so I had not previously made the connection.<br>
Thanks,<br><font color="#888888">Iztok</font><br><br><div class="gmail_quote">On Mon, Mar 31, 2008 at 8:03 AM, Mike Frysinger <<a href="mailto:vapier@gentoo.org">vapier@gentoo.org</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Monday 31 March 2008, Iztok Marjanovic wrote:<br>
> I have the same problem as described by a previous post by Stefan (see<br>
> below). Stefan fixed his problem by using a --disable-openpty<br>
> configuration parameter. I do not know where to specify the<br>
> --disable-openpty. Is this specified in a dropbear config file somwhere?<br>
<br>
</div>why dont you just mount /dev/pts correctly ? and make sure your kernel<br>
supports the newer pty stuff ? otherwise you'll just have to deal with the<br>
fun problems of old bsd pty and static # of device nodes.<br>
<font color="#888888">-mike<br>
</font></blockquote></div><br>