Intl domain configuration #41
Loading…
Reference in New Issue
No description provided.
Delete Branch "134-intl-configuration"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Currently WIP, needs testing.Already working.
2ec85bfa16
to4bbf162a87
df24c92e54
toeb7a22729a
eb7a22729a
to7ecabeaadc
7ecabeaadc
todda6a06454
dda6a06454
to683a565a1d
WIP: Intl domain configurationto Intl domain configuration@ -0,0 +6,4 @@
encap = no
mobike = no
send_certreq = no
proposals = aes128gcm128-sha256-prfsha256-curve25519,aes128gcm128-sha256-prfsha256-ecp256
That many?
Legacy from https://git.m-labs.hk/M-Labs/it-infra/src/branch/master/remote-ipsec.txt .
I'm not fan of tweaking swanctl files
@ -0,0 +91,4 @@
ufw allow 587/tcp
ufw limit 500,4500/udp
ufw route allow in on gre1 out on eth0
This is already done in gretun.sh
Do we really need ufw at all anyway? Only ports open on VPS should be 22/80/443 anyway. What problem is ufw supposed to solve?
UFW is persistent and just has simpler UX (it uses iptables anyway) -> less chances to misconfigure something and easier to read
If it's persistent then it should not be in the gretun scripts?
The other question is not answered.
683a565a1d
toc7c6e56a1e