0000263: nc cannot use -e when initiating a tcp connection to something else

BusyBox Bug and Patch Tracking

Viewing Issue Simple Details [ Jump to Notes ]

[ View Advanced ] [ Issue History ] [ Print ]

Category

Severity

Reproducibility

Date Submitted

Last Update

0000263

[BusyBox] Networking Support

major

always

05-19-05 09:32

07-31-05 15:34

Reporter

owlman

View Status

public

Assigned To

BusyBox

Priority

normal

Resolution

fixed

Status

closed

Product Version

1.00

Summary

0000263: nc cannot use -e when initiating a tcp connection to something else

Description

Host A is a full linux.
Host B is a busybox.

A$ nc -l -p 3000
B$ nc -e /bin/sh A 3000

The connection goes up and immediately down, because the busybox nc close()s stdin (filedescriptor 0), then socket()s the connection to the next available filedescriptor (0), then starts the filedescriptor duplication spree: dup2(0, 0); close(0); dup2(0,1); dup2(0,2).

The attached patch removes the first close()ing of stdin, because the first dup2() does it for us

Additional Information

Attached Files

nc.c.diff [^] (495 bytes) 05-19-05 09:32

Relationships

Notes
(0000326) pgf 07-20-05 12:40	Committed revision 10883.

Issue History
Date Modified	Username	Field	Change
05-19-05 09:32	owlman	New Issue
05-19-05 09:32	owlman	File Added: nc.c.diff
05-19-05 09:33	owlman	Issue Monitored: owlman
05-22-05 20:06	cwhite102	Issue Monitored: cwhite102
07-20-05 12:40	pgf	Status	assigned => resolved
07-20-05 12:40	pgf	Resolution	open => fixed
07-20-05 12:40	pgf	Note Added: 0000326
07-31-05 15:34	vapier	Status	resolved => closed