ports/179939: www/gatling does not work with TLS in default installation
Lothar Braun
lothar at lobraun.de
Mon Jun 24 20:50:01 UTC 2013
>Number: 179939
>Category: ports
>Synopsis: www/gatling does not work with TLS in default installation
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-ports-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Mon Jun 24 20:50:00 UTC 2013
>Closed-Date:
>Last-Modified:
>Originator: Lothar Braun
>Release: FreeBSD 9.1-RELEASE
>Organization:
>Environment:
FreeBSD horst-root 9.1-RELEASE-p4 FreeBSD 9.1-RELEASE-p4 #0: Mon Jun 17 11:42:37 UTC 2013 root at amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64
>Description:
The gatling webserver does not work in its default configuration if TLS is enabled, throwing messages like:
Jun 24 22:26:51 horst-root gatling[57153]: accept 7 XXX.XXX.XXX.XXX 50018 1 https
Jun 24 22:26:51 horst-root gatling[57153]: ssl_protocol_error 7
Jun 24 22:26:51 horst-root gatling[57153]: close/readerr 7
This is due to the fact that /usr/local/etc/rc.d/gatling starting gating with the option -c (chroot). TLS support requires access to /dev/urandom to work properly
>How-To-Repeat:
Install gatling. Create a server.pem certificate by running "make cert" from the source (or generate a pem file by hand). Install the pem file at $gatling_root/server.pem. Start gatling and connect to the HTTPs port.
>Fix:
Mount the devfs in the chroot in the init script
mkdir -p $gatling_root/dev
mount -t devfs devfs $gatling_root/dev
before starting tlsgating
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-ports-bugs
mailing list