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-05-05 15:16:21 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/stunnel-image (Old) and /work/SRC/openSUSE:Factory/.stunnel-image.new.30200 (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "stunnel-image" Tue May 5 15:16:21 2026 rev:13 rq:1350814 version:unknown Changes: -------- --- /work/SRC/openSUSE:Factory/stunnel-image/stunnel-image.changes 2026-03-27 06:50:43.644986154 +0100 +++ /work/SRC/openSUSE:Factory/.stunnel-image.new.30200/stunnel-image.changes 2026-05-05 15:17:43.016921868 +0200 @@ -1,0 +2,10 @@ +Wed Apr 29 15:45:56 UTC 2026 - SUSE Update Bot <[email protected]> + +- README clarification + +------------------------------------------------------------------- +Wed Apr 29 11:05:27 UTC 2026 - SUSE Update Bot <[email protected]> + +- handle retry and delay + +------------------------------------------------------------------- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ README.md ++++++ --- /var/tmp/diff_new_pack.bz9LDO/_old 2026-05-05 15:17:43.608945417 +0200 +++ /var/tmp/diff_new_pack.bz9LDO/_new 2026-05-05 15:17:43.612945577 +0200 @@ -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`, `STUNNEL_CONNECT`, and `STUNNEL_CLIENT`: +`STUNNEL_ACCEPT`, `STUNNEL_CONNECT`, `STUNNEL_CLIENT`, `STUNNEL_DELAY` and `STUNNEL_RETRY`: - `STUNNEL_SERVICE_NAME`: name or otherwise unique identifier of the service (used for documentation purposes only) @@ -47,6 +47,14 @@ operates in client mode (accepts unencrypted connections and forwards them encrypted) +- `STUNNEL_DELAY`: delay DNS lookup for the `connect` option (accepts `yes` or + `no`). Defaults to `no`. When set to `yes`, it is useful for dynamic DNS + or when the network might not be available at startup. + +- `STUNNEL_RETRY`: retry connecting to the `connect` target (accepts a time in ms, `yes` or + `no`). Defaults to `no`. When set to `yes`, stunnel will retry the connection + if it fails after 1000ms. + 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.bz9LDO/_old 2026-05-05 15:17:43.648947009 +0200 +++ /var/tmp/diff_new_pack.bz9LDO/_new 2026-05-05 15:17:43.652947168 +0200 @@ -21,6 +21,12 @@ echo "accept = ${STUNNEL_ACCEPT}" >> $conf echo "connect = ${STUNNEL_CONNECT}" >> $conf echo "client = ${STUNNEL_CLIENT}" >> $conf + if [[ -n "${STUNNEL_DELAY}" ]]; then + echo "delay = ${STUNNEL_DELAY}" >> $conf + fi + if [[ -n "${STUNNEL_RETRY}" ]]; then + echo "retry = ${STUNNEL_RETRY}" >> $conf + fi fi exec "$@"
