execution problems and executable size questions

[Matt Johnston]

On Mon, Sep 27, 2004 at 03:26:47PM +0200, Alfonso Acosta wrote:
> Ok, that showed what the problem is, I paste what dropbear printed to stderr
> 
> # dropbear -F -p 22
> [461] Jan 01 10:22:42 Not forking
> [462] Jan 01 10:23:28 Child connection from 192.168.200.2:38096
> [462] Jan 01 10:23:37 password auth succeeded for 'admin'
> [462] Jan 01 10:23:37 exit after auth (admin): chmod(/dev/ttyp1, 0622)
> failed: Read-only file system
> [462] Jan 01 10:23:37 chown /dev/ttyp1 0 0 failed: Read-only file system
> [462] Jan 01 10:23:37 chmod /dev/ttyp1 0666 failed: Read-only file system
> 
> /dev is part of the root file system (which is recorded into the flash
> memory and it uses cramfs filesystem, so it can only be read)

Ah. If it's a single user system, the easiest solution might
just be to disable the chown() and chmod() call - it's not
like there're any other users who might be sniffing :)
(sshpty.c is where you'll find those chown/chmods). 

The proper solution would probably be to mount devpts at
/dev/pts, and then let the libc openpty() open the pty
device and handle perms (via the kernel). Of course that
depends on whether the uClibc provides openpty(), and
whether you want to compile in devpts support.

Cheers,
Matt