Opened 13 years ago

Closed 13 years ago

#1209 closed Bug (fixed)

shttpd crash when setting port to one already in use

Reported by: Waldorf Owned by: charles
Priority: Normal Milestone: 1.40
Component: libtransmission Version: 1.33
Severity: Critical Keywords:
Cc:

Description

Both on GTK and Mac client.

Change History (8)

comment:1 Changed 13 years ago by jinzo

that's probably because ports belov 1024 ( or soewhere there ) are reserved for daemons and thus root user (at least on linux some time ago )? or did you run it as root ?

comment:2 Changed 13 years ago by charles

This is an shttpd bug. shttpd doesn't have a mechanism to test the port before setting it, and when setting it, crashes the program instead of returning an error if there's a problem.

comment:3 Changed 13 years ago by smmalis

  • Summary changed from Crash when setting webgui/rpc port to 80 to Crash when setting webgui/rpc port to already used port

It isn't just port 80, its any port already used by something. I had crashes when setting it to the port Transmission was using and the port my SSH was using.

comment:4 Changed 13 years ago by charles

I've been attempting to contact the shttpd author about this.

comment:5 Changed 13 years ago by charles

  • Summary changed from Crash when setting webgui/rpc port to already used port to shttpd crash when setting port to one already in use

comment:6 Changed 13 years ago by charles

Waldorf: could you please test out a nightly build of r6645 or higher? I've upgraded Transmission's copy of shttpd to version 1.42.

comment:7 Changed 13 years ago by charles

  • Milestone changed from None Set to 1.40
  • Status changed from new to assigned
  • Version changed from 1.32+ to 1.33

comment:8 Changed 13 years ago by charles

  • Resolution set to fixed
  • Status changed from assigned to closed

fixed in r6697

Note: See TracTickets for help on using tickets.