leap_platform.git/puppet/modules/site_stunnel, branch master [leap_platform] Install stunnel4 from jessie-backports 2017-02-27T09:09:09+00:00 varac varacanero@zeromail.org 2017-02-27T09:09:09+00:00 dea0638d978b4fab1f6ebe9f20ba51a3cb0effdd The jessie version randonly closes the connection prematurely see https://0xacab.org/leap/platform/issues/8746 - Resolves: #8746 
The jessie version randonly closes the connection prematurely
see https://0xacab.org/leap/platform/issues/8746

- Resolves: #8746
switch to two-space soft tabs to fix lint error 2016-06-16T18:41:58+00:00 Micah micah@leap.se 2016-06-14T16:51:08+00:00 8532c9656eba93a10601421089502e39aa23b753 Change-Id: Ic12b243b195e40482a70dd70219212c3697899ba 
Change-Id: Ic12b243b195e40482a70dd70219212c3697899ba
make sure required x509 bits are there before stunnel is started 2016-06-16T18:41:58+00:00 Micah micah@leap.se 2016-06-14T16:37:10+00:00 25cdee309d4ad749d633c8b4d5bf7e65f83fb75b Change-Id: I772c3b6e489e3c1848c45c6bcaa240324fc88928 
Change-Id: I772c3b6e489e3c1848c45c6bcaa240324fc88928
[style] lint further more 2016-04-25T19:41:20+00:00 varac varacanero@zeromail.org 2016-04-25T16:21:48+00:00 f2f2c7391056c252523730cd76ab759db9117c9c - ignore puppet lint error about inheriting from different namespace 
- ignore puppet lint error about inheriting from different namespace
[style] lint some custom manifests 2016-04-18T16:19:44+00:00 varac varacanero@zeromail.org 2016-04-18T16:19:44+00:00 22b788920defdd42b4abda144afd8ca69d0a9d37 I used `puppet-lint -f FILE` to fix most issues, while finishing with manual intervention. 
I used `puppet-lint -f FILE` to fix most issues, while
finishing with manual intervention.
Log stunnel server logs same as client (#8021) 2016-04-12T18:20:46+00:00 Micah micah@leap.se 2016-04-12T14:22:40+00:00 64635ed7ccf287ae0d6bab71837b5213b6790613 stunnel server logs were not going to /var/log/stunnel4/*, but to /var/log/syslog instead. This was different from stunnel client logging, now its the same. Change-Id: I2dc2024b77dbb65554fc7865b0e46aedf930c6d8 
stunnel server logs were not going to /var/log/stunnel4/*, but to
/var/log/syslog instead. This was different from stunnel client
logging, now its the same.

Change-Id: I2dc2024b77dbb65554fc7865b0e46aedf930c6d8
stunnel shouldn't use syslog, and leap_mx can't. 2015-04-17T03:57:11+00:00 elijah elijah@riseup.net 2015-04-17T03:57:11+00:00 c7e12fd3cfe482e22e337eaea80ca7994dea7524 






clean up logging mess: add 'logfile' define, mv openvpn and stunnel logs to their own files, fix mx logwatch path.
2015-04-16T18:10:59+00:00

elijah
elijah@riseup.net

2015-04-15T23:12:11+00:00

bb07407485ed1626221a1190cc2fb2789f95ed22












Make sure that stunnel restarts when cert/key change (#6181)
2014-11-20T20:22:09+00:00

Micah Anderson
micah@leap.se

2014-11-20T20:22:09+00:00

896dd69710fa24a0235fc70081a71f35adbf9af1

Change-Id: I5085247a87018e18e73833119ac73225afbfea1e





Change-Id: I5085247a87018e18e73833119ac73225afbfea1e







add missing TLSv1 sslversion parameter to site_stunnel::serviers
2014-11-03T01:53:34+00:00

Micah Anderson
micah@leap.se

2014-11-03T01:53:34+00:00

38d7c80fae4efc1d365ec9f982cb025dc67a4386

Change-Id: I48dc8135943393bd11c7181853985f4a5799011e





Change-Id: I48dc8135943393bd11c7181853985f4a5799011e