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 2025-12-17 17:34:53 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/stunnel-image (Old) and /work/SRC/openSUSE:Factory/.stunnel-image.new.1939 (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "stunnel-image" Wed Dec 17 17:34:53 2025 rev:8 rq:1323177 version:unknown Changes: -------- --- /work/SRC/openSUSE:Factory/stunnel-image/stunnel-image.changes 2025-10-21 11:19:00.033300294 +0200 +++ /work/SRC/openSUSE:Factory/.stunnel-image.new.1939/stunnel-image.changes 2025-12-17 17:39:20.259136101 +0100 @@ -1,0 +2,5 @@ +Tue Dec 16 15:28:01 UTC 2025 - SUSE Update Bot <[email protected]> + +- README.md language cleanups + +------------------------------------------------------------------- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ README.md ++++++ --- /var/tmp/diff_new_pack.xySe5q/_old 2025-12-17 17:39:21.027168378 +0100 +++ /var/tmp/diff_new_pack.xySe5q/_new 2025-12-17 17:39:21.031168547 +0100 @@ -5,7 +5,7 @@ ## Description -Stunnel is an open-source multi-platform application that provides a universal +Stunnel is an open source multi-platform application that provides a universal TLS/SSL tunneling service. @@ -21,28 +21,28 @@ The container entry point configures TLS/SSL automatically by setting the key and certificate to the values of the environment variables `STUNNEL_KEY` and -`STUNNEL_CERT`. If one of the environment variables is unset, then the -entrypoint defaults to `/etc/stunnel/stunnel.key` for `STUNNEL_KEY` and +`STUNNEL_CERT`. If one of the environment variables is unset, the +entry point defaults to `/etc/stunnel/stunnel.key` for `STUNNEL_KEY` and `/etc/stunnel/stunnel.pem` for `STUNNEL_CERT`. -The entrypoint can set up a single service via environment variables, so that +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_SERVICE_NAME`: name or otherwise unique identifier of the service - (used for documentation purpose only) + (used for documentation purposes only) - `STUNNEL_ACCEPT`: address on which new connections should be accepted. It can - be either a hostname and a port number or just a port number (in which case, - localhost is assumed to be the host) + be either a hostname and port number or just a port number (in which case, + localhost is assumed) - `STUNNEL_CONNECT`: address on which the unencrypted service is listening and to which stunnel connects. It can be either a hostname and port number or just - a port number (in which case, localhost is assumed to be the host) + a port number (in which case, localhost is assumed) -For example, to create an SSL endpoint for a webserver listening on port `8000` +For example, to create an SSL endpoint for a Web server listening on port `8000` on localhost, run the following command: ```bash @@ -60,7 +60,7 @@ ### Logging Stunnel supports eight log levels, from 0 (emergency) to 7 (debug) with 5 -(notice) being the default. The log level can be configured via the environment +(notice) as the default. The log level can be configured via the environment variable `STUNNEL_DEBUG` using either the number or the log level name. For the supported logging levels, refer to the [upstream documentation](https://www.stunnel.org/static/stunnel.html#debug-FACILITY.-LEVEL).
