From a5f2bce68974cace3ee1600a6f3c9ad30f13068a Mon Sep 17 00:00:00 2001 From: "Ycarus (Yannick Chabanois)" Date: Thu, 11 Mar 2021 16:56:20 +0100 Subject: [PATCH] Restart shadowsocks after setting encrypt method --- openmptcprouter/files/etc/init.d/openmptcprouter-vps | 2 ++ 1 file changed, 2 insertions(+) diff --git a/openmptcprouter/files/etc/init.d/openmptcprouter-vps b/openmptcprouter/files/etc/init.d/openmptcprouter-vps index 2e623ac34..f218d2d81 100755 --- a/openmptcprouter/files/etc/init.d/openmptcprouter-vps +++ b/openmptcprouter/files/etc/init.d/openmptcprouter-vps @@ -1709,6 +1709,7 @@ _config_service() { vps_aes="$(echo "$vps_config" | jsonfilter -q -e '@.vps.aes')" if [ "$vps_aes" != "false" ] && [ "$user_permission" != "ro" ]; then logger -t "OMR-VPS" "CPU support AES, set it by default" + method="$(uci -q get shadowsocks-libev.sss0.method)" uci -q batch <<-EOF >/dev/null set glorytun.vpn.chacha20="0" commit glorytun @@ -1717,6 +1718,7 @@ _config_service() { EOF config_foreach _set_ss_server server "method" "aes-256-gcm" uci -q commit shadowsocks-libev + [ "$method" != "aes-256-gcm" ] && /etc/init.d/shadowsocks-libev restart fi } fi