v2ray-core VS sops

Hey there! Lots of experience with this having lived in China for 2 years. I recommend you look into xray-core or v2ray.

https://github.com/v2fly/v2ray-core

https://github.com/XTLS/Xray-core

Here are my configs: https://github.com/acheong08/notes/tree/main/xray

cd ~ wget https://github.com/v2fly/v2ray-core/releases/download/v5.7.0/v2ray-linux-64.zip sudo apt install -y unzip unzip v2ray-linux-64.zip cp geoip/output/dat/* . ./v2ray uuid

If the changing por trick work you can try shadowsocks or v2ray.

Normal VPNs that you can see ads all over the place like N*rdVPN won't work, period. The correct way is to rent a few servers from different providers, make sure their ips are not blocked, and build your own V2Ray or Trojan service first. The Chinese gov will not be able to distinguish your Trojan traffic from ordinary https traffic, so the only thing that's sus to them would be the fact that all your traffic goes to one foreign ip, but I've been doing it for a few years without officials knocking on my door so yeah I think it will work for you as well. I don't take responsibility tho, do your research.

Given that every other client is mostly using https://github.com/v2fly/v2ray-core that can be compiled for every architecture/platform that Outline client supports, maybe it's worth investing time into allowing it as a backend. It can even be used for pure shadowsocks since it's for sure more updated than the old golang shadowsocks implementation.

v2Ray: https://v2fly.org

My script just sets up default .sops.yaml for https://github.com/getsops/sops

You can further edit .sops.yaml(eg have multiple of them) and decide how you split secrets in your directory tree to further customize who can decrypt the secrets.

It works pretty well for prod/dev splits, etc

Mozilla SOPS (Secrets OPerationS) is an open-source command-line tool for managing and storing secrets. It uses secure encryption methods to encrypt secrets at rest and decrypt them at runtime. SOPS supports a variety of key management systems, including AWS KMS, GCP KMS, Azure Key Vault, and PGP. It's particularly useful in a DevOps context where sensitive data like API keys, passwords, or certificates need to be securely managed and seamlessly integrated into application workflows.

Encrypted secrets thanks to SOPS and Age

We do the exact same thing to keep track of some credentials we use sops[1] and AWS KMS to separate credentials by sensitivity, then use the git differ to view the diffs between the encrypted secrets

Definitely not best practice security-wise, but it works well

[1] https://github.com/getsops/sops

For anyone new to SOPS like I was - https://github.com/getsops/sops

I've found this is largely solved by strictly separating plain config and secrets, and then having secrets pull from GCP secret manager / vault / whatever.

You can then commit all the config (including the secret identifiers) and it all just works so long as you're authenticated with your secret storage system.

We do this for the live configuration as well in line with Gitops and find it to work well.

If you don't want to use a cloud secret manager you can also use something like https://github.com/getsops/sops to commit the encrypted secrets safely

Basically, the simpler the better --just encrypt your secrets and check them in to version control.

We use SOPS[0] for this, and have found it to be pretty nice.

[0]: https://github.com/getsops/sops

The answer is that secrets shouldn't be stored in the git repo at all, but somewhere safe like a password manager or Mozilla's SOPS which people seem to love.

Unfortunately, the SOPS project is in some sort of a limbo state and there has been quite a long period with limited maintenance and unclear position from Mozilla. Despite the project being accepted into the CNCF, it's still unclear what will happen with it going forward.