Age | Commit message (Collapse) | Author |
|
|
|
Update to upstream version '2.5~beta1'
with Debian dir d53f9a482ac24eb491a294b26c24bb1d87afad24
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Closes: #958315
|
|
system configuration
Closes: #958296
|
|
|
|
|
|
Update to upstream version '2.4.9'
with Debian dir b64ac777b141e10bd0a11149a47506fd704401b8
|
|
|
|
|
|
Refresh d/copyright
|
|
|
|
|
|
|
|
Update to upstream version '2.4.8'
with Debian dir 00c9c7e7fdd8b0a1729f9102507c151f67ca8c5d
|
|
|
|
|
|
|
|
This generally seems to be the wrong knob to protect against runaway
forks (as it does not limit per instance, but per user systemwide), but
a general mediation is still under discussion. Meanwhile bump the limit
for the Debian unit to 100.
Upstream openvpn-client@.service and openvpn-server@.service still use
10
See Bug#861923 for discussion.
|
|
"safe fork mode" (Closes: #772812, #900805, #907452)
|
|
Same change has been done upstream in 2.4.7
Closes: #868806
|
|
|
|
Update to upstream version '2.4.7'
with Debian dir d01da6ef78dc8ce91265e8f319468f6c34d23af8
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|