clash-verge-rev: move IPC path to /run/clash-verge-rev/service.sock for better security

[Bot-wxt1221]

move socket path to /run/clash-verge-rev/service.sock

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
  • sandbox = relaxed
  • sandbox = true
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• Nixpkgs 25.11 Release Notes (or backporting 24.11 and 25.05 Nixpkgs Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
• NixOS 25.11 Release Notes (or backporting 24.11 and 25.05 NixOS Release notes)
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md, pkgs/README.md, maintainers/README.md and other contributing documentation in corresponding paths.

---

Add a 👍 reaction to pull requests you find important.

[Prince213]

Hi @Bot-wxt1221 can you rephrase your PR description?

Also, please describe what kind of operations are prevented for easier understanding of the significance of the PR.

[Bot-wxt1221]

@Prince213 It's clear. This program will create IPC for other programs in userspace. This systemd harden options is typical.

[Prince213]

AF_UNIX and RestrictNamespaces is for creating IPC ProtectSystem=strict and ProtectTmp prevent it from operation under /tmp

ges please briefly describe the package or provide a link to its homepage.
-->

->

AF_UNIX and RestrictNamespaces is for creating IPC
ProtectSystem=strict and ProtectTmp prevent it from operation under /tmp

Also, https://www.freedesktop.org/software/systemd/man/latest/systemd.exec.html

if ProtectSystem= is set to "strict" and PrivateTmp= is enabled, then /tmp/ and /var/tmp/ will be writable

Does the program try to write to /tmp? If so shouldn't it be allowed to do that?

[Bot-wxt1221]

@Prince213 It place his IPC under /tmp. We need /tmp for everyone to read. Or we move it to another place.

[Prince213]

What about we place this in /run with RuntimeDirectory?

https://0pointer.net/blog/projects/tmp.html

/run (traditionally /var/run) where privileged daemons can store runtime data, such as communication primitives. This is where your daemon should place its sockets.

[Prince213]

Issue has been filed upstream: clash-verge-rev/clash-verge-service#13

[Prince213]

Diff LGTM