Script 'mail_helper' called by obssrc Hello community, here is the log from the commit of package stunnel-image for openSUSE:Factory checked in at 2026-01-03 17:27:45 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/stunnel-image (Old) and /work/SRC/openSUSE:Factory/.stunnel-image.new.1928 (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "stunnel-image" Sat Jan 3 17:27:45 2026 rev:10 rq:1325142 version:unknown Changes: -------- --- /work/SRC/openSUSE:Factory/stunnel-image/stunnel-image.changes 2026-01-02 14:28:44.733012852 +0100 +++ /work/SRC/openSUSE:Factory/.stunnel-image.new.1928/stunnel-image.changes 2026-01-03 17:28:12.413675293 +0100 @@ -1,0 +2,10 @@ +Fri Jan 2 10:14:03 UTC 2026 - SUSE Update Bot <[email protected]> + +- add client option + +------------------------------------------------------------------- +Fri Jan 2 10:12:48 UTC 2026 - SUSE Update Bot <[email protected]> + +- order package installation alphabetically + +------------------------------------------------------------------- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ README.md ++++++ --- /var/tmp/diff_new_pack.QplHis/_old 2026-01-03 17:28:13.357713917 +0100 +++ /var/tmp/diff_new_pack.QplHis/_new 2026-01-03 17:28:13.361714080 +0100 @@ -28,7 +28,7 @@ The entry point can set up a single service via environment variables, so that the user doesn't have to write and mount their own configuration file. This can be specified via the environment variables `STUNNEL_SERVICE_NAME`, -`STUNNEL_ACCEPT` and `STUNNEL_CONNECT`: +`STUNNEL_ACCEPT`, `STUNNEL_CONNECT`, and `STUNNEL_CLIENT`: - `STUNNEL_SERVICE_NAME`: name or otherwise unique identifier of the service (used for documentation purposes only) @@ -41,6 +41,12 @@ to which stunnel connects. It can be either a hostname and port number or just a port number (in which case, localhost is assumed) +- `STUNNEL_CLIENT`: sets the client mode (accepts `yes` or `no`). Defaults to + `no`, which means stunnel operates in server mode (accepts encrypted + connections and forwards them unencrypted). When set to `yes`, stunnel + operates in client mode (accepts unencrypted connections and forwards them + encrypted) + For example, to create an SSL endpoint for a Web server listening on port `8000` on localhost, run the following command: ++++++ entrypoint.sh ++++++ --- /var/tmp/diff_new_pack.QplHis/_old 2026-01-03 17:28:13.389715226 +0100 +++ /var/tmp/diff_new_pack.QplHis/_new 2026-01-03 17:28:13.393715390 +0100 @@ -4,6 +4,7 @@ STUNNEL_CERT="${STUNNEL_CERT:-/etc/stunnel/stunnel.pem}" STUNNEL_KEY="${STUNNEL_KEY:-/etc/stunnel/stunnel.key}" +STUNNEL_CLIENT="${STUNNEL_CLIENT:-no}" if [[ -n ${STUNNEL_DEBUG} ]]; then echo "debug = ${STUNNEL_DEBUG}" > /etc/stunnel/conf.d/000debug.conf @@ -19,6 +20,7 @@ echo "[${STUNNEL_SERVICE_NAME}]" > $conf echo "accept = ${STUNNEL_ACCEPT}" >> $conf echo "connect = ${STUNNEL_CONNECT}" >> $conf + echo "client = ${STUNNEL_CLIENT}" >> $conf fi exec "$@"
