Mihomo_v1.19.7

chore: rollback incompatible changes to updateConfigs api

#Clash #Mihomo

Mihomo
v1.19.8

What's Changed

BUG & Fix

● 6e35cf9 fix: truncated UDP response in system dns #2031 by @wwqgtxx

Maintenance

● 2116640 chore: the updateConfigs api also adds a check for SAFE_PATHS by @wwqgtxx
● 23e2d3a chore: rebuild provider load by @wwqgtxx
● 266fb03 chore: update dependencies by @wwqgtxx
● 76e9607 chore: move start healthcheck.process() from New to Initial in provider avoid panic cause by build-in proxy have not set to tunnel by @wwqgtxx

Full Changelog: v1.19.7...v1.19.8

Mihomo
v1.19.9

What's Changed

● 188372c feat: add tls.ech-key for external-controller-tls by @wwqgtxx
● 5cf0f18 feat: reality add support-x25519mlkem768, it only works with new version server by @wwqgtxx
● a1350d4 feat: add ech-key for listeners by @wwqgtxx
● c6d7ef8 feat: add ech-opts for anytls/shadowsocks/trojan/vmess/vless outbound by @wwqgtxx
● dc958e6 feat: add ech-opts for hysteria/hysteria2/tuic outbound by @wwqgtxx
● Other incompatible updates are the same as v1.19.6~v1.19.8:

● For security reasons, all paths appearing in the configuration file will be limited to workdir (regardless of whether they are relative or absolute). If there is a specific need, please specify additional safe paths by setting the SAFE_PATHS environment variable while ensuring safety. The syntax of this environment variable is the same as the PATH environment variable parsing rules of this operating system (i.e., semicolon-separated under Windows and colon-separated under other systems)
● For security reasons, the "path" parameter of /configs in the restful api has been restricted, and its directory also needs to be in workdir or SAFE_PATHS.
● In addition, support for specifying routing-mark and interface-name for proxy-groups has been removed. Please specify the relevant parameters in proxies directly.
● Note: The workdir mentioned above is specified by the -d parameter when the program is started or the CLASH_HOME_DIR environment variable. If neither of the above is specified, the default is: ● on Unix systems, $HOME/.config/mihomo. ● on Windows, %USERPROFILE%/.config/mihomo.

BUG & Fix

● 41b57af fix: grpc deadline implement by @wwqgtxx
● 608ddb1 fix: external-ui-name must in local by @wwqgtxx
● 90ed01e fix: backoff not reset when the file unchanged by @wwqgtxx
● bb8c47d fix: error typo by @wwqgtxx
● c489c52 fix: hysteria2 hop ports init #2056 by @wwqgtxx
● d036d98 fix: http server does not handle http2 logic correctly by @wwqgtxx
● d5a0390 fix: race in close grpc transport by @wwqgtxx
● d900c71 fix: shadowtls v2 not work with X25519MLKEM768 by @wwqgtxx
● f91a586 fix: inline proxy provider's healthcheck not work by @wwqgtxx

Maintenance

● 1672750 chore: simplifying the old fingerprint processing method by @wwqgtxx
● 257fead docs: update config.yaml follow 5cf0f18 by @wwqgtxx
● 83213d4 chore: adjust min backoff from 1s to 10s by @wwqgtxx
● 8a5f3b8 chore: simplify port hop costs by @wwqgtxx
● 8f92b1d chore: simplify the single root decompression process by @wwqgtxx
● 9f7a2a3 chore: unpack externalUI in a separate temporary directory to avoid malicious compressed packages from polluting workdir by @wwqgtxx

Mihomo
v1.19.10

What's Changed

● The DNS resolution of the overall UDP part has been delayed to the connection initiation stage. It will be triggered only when the IP rule without no-resolve is matched during the rule matching process. ● For direct and wireguard outbound, the same logic as the TCP part will be followed, that is, when direct-nameserver (or DNS configured by wireguard) exists, the resolution result in the rule matching process will be discarded and the domain name will be re-resolved. This re-resolution logic is only effective for fakeip. ● For reject and DNS outbound, no resolution is required. ● For other outbound, resolution will still be performed when the UDP connection is initiated, and the domain name will not be sent directly to the remote server.
● In addition, the memory usage of the UDP part of tun inbound has also been optimized in this version.
● Other incompatible updates are the same as v1.19.6~v1.19.8:

● For security reasons, all paths appearing in the configuration file will be limited to workdir (regardless of whether they are relative or absolute). If there is a specific need, please specify additional safe paths by setting the SAFE_PATHS environment variable while ensuring safety. The syntax of this environment variable is the same as the PATH environment variable parsing rules of this operating system (i.e., semicolon-separated under Windows and colon-separated under other systems)
● For security reasons, the "path" parameter of /configs in the restful api has been restricted, and its directory also needs to be in workdir or SAFE_PATHS.
● In addition, support for specifying routing-mark and interface-name for proxy-groups has been removed. Please specify the relevant parameters in proxies directly.
● Note: The workdir mentioned above is specified by the -d parameter when the program is started or the CLASH_HOME_DIR environment variable. If neither of the above is specified, the default is: ● on Unix systems, $HOME/.config/mihomo. ● on Windows, %USERPROFILE%/.config/mihomo.

BUG & Fix

● 15eda70 fix: hysteria2 panic by @wwqgtxx
● 1db89da fix: quic sniffer should not replace domain when no valid host is read by @wwqgtxx
● 213d80c fix: quic sniffer should consider skipDomain by @wwqgtxx
● 33590c4 fix: destination should unmap before find interface by @wwqgtxx
● 4741ac6 fix: in-port not work with shadowsocks listener by @wwqgtxx
● 5a21bf3 fix: listener close panic by @wwqgtxx
● 6c9abe1 fix: vmess listener error by @wwqgtxx
● d2e255f fix: some error in tun by @wwqgtxx

Maintenance

● 12e3952 chore: code cleanup by @wwqgtxx
● 199fb8f chore: update quic-go to 0.52.0 by @wwqgtxx
● 28c387a chore: restore break change in sing-tun by @wwqgtxx
● 34de62d chore: better get localAddr by @wwqgtxx
● 3ed6ff9 chore: export pipeDeadline by @wwqgtxx
● 4ed8303 chore: remove confused code by @wwqgtxx
● 60ae9dc chore: recover log leval for preHandleMetadata by @wwqgtxx
● 689c58f chore: clear dstIP when overrideDest in sniffer by @wwqgtxx
● 88419cb chore: better parse remote dst by @wwqgtxx
● 9e3bf14 chore: handle two interfaces have the same prefix but different address by @wwqgtxx
● a0c46bb chore: remove the redundant layer of udpnat in sing-tun to reduce resource usage when processing udp by @wwqgtxx
● a1c7881 chore: rebuild udp dns resolve by @wwqgtxx
● b1d12a1 chore: proxy's ech should fetch from proxy-nameserver by @wwqgtxx
● c0f452b chore: more unmap for 4in6 address by @wwqgtxx

大佬们都在用啥Telegram客户端（第三方）

开启Telegram的部分增强功能，支持官方与大部分第三方客户端

#Xposed模块

地址 所属机构 是否支持 DoH 是否支持 DoH3（HTTP/3） 是否官方 DoH 服务地址

https://120.53.53.53/dns-query 腾讯 ✅ 是 ✅ 是（支持 HTTP/3） ✅ 是（DoH-IP 接入点）
https://1.12.12.12/dns-query 腾讯 ❌ 否 ❌ 否 ❌ 仅支持普通 DNS
https://119.29.29.29/dns-query 腾讯 ❌ 否 ❌ 否 ❌ 仅支持普通 DNS

以上回复来自chatgpt

刚刚发现 PlayIntegrityFix 删库跑路啦

A new AList Fork to Anti Trust Crisis

Important
THIS IS A FORK VERSION !!!
We sincerely thank the original author xhofe/alist for his substantial prior contributions.
This fork is not yet stable. A large number of external links point to unaudited content, posing a supply chain attack risk, including related documentation websites, etc. Do not trust!
Currently, only links confirmed to be outside the original author's control (such as alistgo.com) have been removed, The detailed migration progress of the project can be viewed in the OpenList Migration Summary.