Forwarded from Surge's Changelog
#iOS #TestFlight
Surge 5 5.21.0 (2961) is ready to test on iOS.
What to Test:
5.8.1 RC1
- 发现有用户遇到 VIF Virtual IP 分配数量极高的问题，怀疑有 App 通过 DNS 查询偷传数据，该版本中加入了 DNS 查询频率检测，若 10 秒内出现了 1000 个新域名的 DNS 查询将在日志中打印警告。有遇到可以反馈，如果有必要将加入进一步的阻止措施。
Surge 5 5.21.0 (2961) is ready to test on iOS.
What to Test:
5.8.1 RC1
- 发现有用户遇到 VIF Virtual IP 分配数量极高的问题，怀疑有 App 通过 DNS 查询偷传数据，该版本中加入了 DNS 查询频率检测，若 10 秒内出现了 1000 个新域名的 DNS 查询将在日志中打印警告。有遇到可以反馈，如果有必要将加入进一步的阻止措施。
Forwarded from Surge's Changelog
#Mac #Beta
Version 5.4.1-2492
#### Rule Engine Optimizations
- The implementation of RULE-SET and DOMAIN-SET has been completely rewritten. Now, Surge automatically preprocesses and indexes rule sets during resource updates, significantly increasing the matching speed.
1. There is no longer any difference in performance and memory usage between RULE-SET and DOMAIN-SET types of rule sets, allowing flexible usage.
2. There is no longer a restriction in DOMAIN-SET rule sets that prevents the use of eTLDs.
3. The matching speed for DOMAIN, DOMAIN-SUFFIX, IP-CIDR, and IP-CIDR6 rules in RULE-SET has been greatly improved.
- A DOMAIN/DOMAIN-SUFFIX rule set with approximately 100,000 entries used to take 100ms for a single match in the old version; now, it only takes single-digit ms.
- An IP-CIDR rule set with approximately 10,000 entries used to take about 0.1ms for a single match in the old version. The new version only needs 0.0002ms, an improvement of about 500 times. The performance improvement for IP-CIDR6 rules is even greater.
4. In the new version, building a regional IP address collection using the IP-CIDR rule set offers the same performance as directly using the internal GEOIP rule.
5. The Inline Ruleset added in the previous version does not benefit from this optimization, but there is virtually no difference at the scale of hundreds of entries.
6. In previous versions, rules within a Ruleset were matched one by one from top to bottom. If rules requiring DNS resolution were included, DNS would only be triggered when starting to match that sub-rule. In the new version, if any rule requiring DNS resolution is included in the rule set, DNS resolution will occur before testing that rule set. (In most cases, there is no difference)
- Main ruleset matching efficiency has been slightly optimized.
- The efficiency of IP-CIDR6 rules has been significantly improved even in non-indexed situations.
- RULE-SET rules can now be configured directly with parameters no-resolve and extended-matching, which are equivalent to configuring all sub-rules with these parameters.
- DOMAIN-SET rule sets also support configuration with extended-matching.
#### Minor Optimizations
- Now, when performing MITM, the certificate used for signing will be sent to the client together, to support using intermediate certificates for MITM.
- All comments (at the beginning and end of lines) can now use
- Profile error message prompt optimization, now it can give the exact line number where the error occurred more accurately.
- Bug fixes.
Version 5.4.1-2492
#### Rule Engine Optimizations
- The implementation of RULE-SET and DOMAIN-SET has been completely rewritten. Now, Surge automatically preprocesses and indexes rule sets during resource updates, significantly increasing the matching speed.
1. There is no longer any difference in performance and memory usage between RULE-SET and DOMAIN-SET types of rule sets, allowing flexible usage.
2. There is no longer a restriction in DOMAIN-SET rule sets that prevents the use of eTLDs.
3. The matching speed for DOMAIN, DOMAIN-SUFFIX, IP-CIDR, and IP-CIDR6 rules in RULE-SET has been greatly improved.
- A DOMAIN/DOMAIN-SUFFIX rule set with approximately 100,000 entries used to take 100ms for a single match in the old version; now, it only takes single-digit ms.
- An IP-CIDR rule set with approximately 10,000 entries used to take about 0.1ms for a single match in the old version. The new version only needs 0.0002ms, an improvement of about 500 times. The performance improvement for IP-CIDR6 rules is even greater.
4. In the new version, building a regional IP address collection using the IP-CIDR rule set offers the same performance as directly using the internal GEOIP rule.
5. The Inline Ruleset added in the previous version does not benefit from this optimization, but there is virtually no difference at the scale of hundreds of entries.
6. In previous versions, rules within a Ruleset were matched one by one from top to bottom. If rules requiring DNS resolution were included, DNS would only be triggered when starting to match that sub-rule. In the new version, if any rule requiring DNS resolution is included in the rule set, DNS resolution will occur before testing that rule set. (In most cases, there is no difference)
- Main ruleset matching efficiency has been slightly optimized.
- The efficiency of IP-CIDR6 rules has been significantly improved even in non-indexed situations.
- RULE-SET rules can now be configured directly with parameters no-resolve and extended-matching, which are equivalent to configuring all sub-rules with these parameters.
- DOMAIN-SET rule sets also support configuration with extended-matching.
#### Minor Optimizations
- Now, when performing MITM, the certificate used for signing will be sent to the client together, to support using intermediate certificates for MITM.
- All comments (at the beginning and end of lines) can now use
#, //, ; three common comment symbols.- Profile error message prompt optimization, now it can give the exact line number where the error occurred more accurately.
- Bug fixes.
Forwarded from Surge's Changelog
#Mac #Beta
Version 5.4.1-2493
#### Rule Engine Optimizations
- The implementation of RULE-SET and DOMAIN-SET has been completely rewritten. Now, Surge automatically preprocesses and indexes rule sets during resource updates, significantly increasing the matching speed.
1. There is no longer any difference in performance and memory usage between RULE-SET and DOMAIN-SET types of rule sets, allowing flexible usage.
2. There is no longer a restriction in DOMAIN-SET rule sets that prevents the use of eTLDs.
3. The matching speed for DOMAIN, DOMAIN-SUFFIX, IP-CIDR, and IP-CIDR6 rules in RULE-SET has been greatly improved.
- A DOMAIN/DOMAIN-SUFFIX rule set with approximately 100,000 entries used to take 100ms for a single match in the old version; now, it only takes single-digit ms.
- An IP-CIDR rule set with approximately 10,000 entries used to take about 0.1ms for a single match in the old version. The new version only needs 0.0002ms, an improvement of about 500 times. The performance improvement for IP-CIDR6 rules is even greater.
4. In the new version, building a regional IP address collection using the IP-CIDR rule set offers the same performance as directly using the internal GEOIP rule.
5. The Inline Ruleset added in the previous version does not benefit from this optimization, but there is virtually no difference at the scale of hundreds of entries.
6. In previous versions, rules within a Ruleset were matched one by one from top to bottom. If rules requiring DNS resolution were included, DNS would only be triggered when starting to match that sub-rule. In the new version, if any rule requiring DNS resolution is included in the rule set, DNS resolution will occur before testing that rule set. (In most cases, there is no difference)
- Main ruleset matching efficiency has been slightly optimized.
- The efficiency of IP-CIDR6 rules has been significantly improved even in non-indexed situations.
- RULE-SET rules can now be configured directly with parameters no-resolve and extended-matching, which are equivalent to configuring all sub-rules with these parameters.
- DOMAIN-SET rule sets also support configuration with extended-matching.
#### Minor Optimizations
- Now, when performing MITM, the certificate used for signing will be sent to the client together, to support using intermediate certificates for MITM.
- All comments (at the beginning and end of lines) can now use
- Profile error message prompt optimization, now it can give the exact line number where the error occurred more accurately.
- Bug fixes.
Version 5.4.1-2493
#### Rule Engine Optimizations
- The implementation of RULE-SET and DOMAIN-SET has been completely rewritten. Now, Surge automatically preprocesses and indexes rule sets during resource updates, significantly increasing the matching speed.
1. There is no longer any difference in performance and memory usage between RULE-SET and DOMAIN-SET types of rule sets, allowing flexible usage.
2. There is no longer a restriction in DOMAIN-SET rule sets that prevents the use of eTLDs.
3. The matching speed for DOMAIN, DOMAIN-SUFFIX, IP-CIDR, and IP-CIDR6 rules in RULE-SET has been greatly improved.
- A DOMAIN/DOMAIN-SUFFIX rule set with approximately 100,000 entries used to take 100ms for a single match in the old version; now, it only takes single-digit ms.
- An IP-CIDR rule set with approximately 10,000 entries used to take about 0.1ms for a single match in the old version. The new version only needs 0.0002ms, an improvement of about 500 times. The performance improvement for IP-CIDR6 rules is even greater.
4. In the new version, building a regional IP address collection using the IP-CIDR rule set offers the same performance as directly using the internal GEOIP rule.
5. The Inline Ruleset added in the previous version does not benefit from this optimization, but there is virtually no difference at the scale of hundreds of entries.
6. In previous versions, rules within a Ruleset were matched one by one from top to bottom. If rules requiring DNS resolution were included, DNS would only be triggered when starting to match that sub-rule. In the new version, if any rule requiring DNS resolution is included in the rule set, DNS resolution will occur before testing that rule set. (In most cases, there is no difference)
- Main ruleset matching efficiency has been slightly optimized.
- The efficiency of IP-CIDR6 rules has been significantly improved even in non-indexed situations.
- RULE-SET rules can now be configured directly with parameters no-resolve and extended-matching, which are equivalent to configuring all sub-rules with these parameters.
- DOMAIN-SET rule sets also support configuration with extended-matching.
#### Minor Optimizations
- Now, when performing MITM, the certificate used for signing will be sent to the client together, to support using intermediate certificates for MITM.
- All comments (at the beginning and end of lines) can now use
#, //, ; three common comment symbols.- Profile error message prompt optimization, now it can give the exact line number where the error occurred more accurately.
- Bug fixes.
Forwarded from Surge's Changelog
#iOS #TestFlight
Surge 5 5.21.0 (2962) is ready to test on iOS.
What to Test:
- 完成了上个版本提到的 DNS 请求频率自动检测与屏蔽功能，并将警告级别提高到通知
5.8.1 RC2
Surge 5 5.21.0 (2962) is ready to test on iOS.
What to Test:
- 完成了上个版本提到的 DNS 请求频率自动检测与屏蔽功能，并将警告级别提高到通知
5.8.1 RC2
Forwarded from Surge's Changelog
#Mac #Beta
Version 5.4.1-2494
#### Rule Engine Optimizations
- The implementation of RULE-SET and DOMAIN-SET has been completely rewritten. Now, Surge automatically preprocesses and indexes rule sets during resource updates, significantly increasing the matching speed.
1. There is no longer any difference in performance and memory usage between RULE-SET and DOMAIN-SET types of rule sets, allowing flexible usage.
2. There is no longer a restriction in DOMAIN-SET rule sets that prevents the use of eTLDs.
3. The matching speed for DOMAIN, DOMAIN-SUFFIX, IP-CIDR, and IP-CIDR6 rules in RULE-SET has been greatly improved.
- A DOMAIN/DOMAIN-SUFFIX rule set with approximately 100,000 entries used to take 100ms for a single match in the old version; now, it only takes single-digit ms.
- An IP-CIDR rule set with approximately 10,000 entries used to take about 0.1ms for a single match in the old version. The new version only needs 0.0002ms, an improvement of about 500 times. The performance improvement for IP-CIDR6 rules is even greater.
4. In the new version, building a regional IP address collection using the IP-CIDR rule set offers the same performance as directly using the internal GEOIP rule.
5. The Inline Ruleset added in the previous version does not benefit from this optimization, but there is virtually no difference at the scale of hundreds of entries.
6. In previous versions, rules within a Ruleset were matched one by one from top to bottom. If rules requiring DNS resolution were included, DNS would only be triggered when starting to match that sub-rule. In the new version, if any rule requiring DNS resolution is included in the rule set, DNS resolution will occur before testing that rule set. (In most cases, there is no difference)
- Main ruleset matching efficiency has been slightly optimized.
- The efficiency of IP-CIDR6 rules has been significantly improved even in non-indexed situations.
- RULE-SET rules can now be configured directly with parameters no-resolve and extended-matching, which are equivalent to configuring all sub-rules with these parameters.
- DOMAIN-SET rule sets also support configuration with extended-matching.
#### Minor Optimizations
- Now, when performing MITM, the certificate used for signing will be sent to the client together, to support using intermediate certificates for MITM.
- All comments (at the beginning and end of lines) can now use
- Profile error message prompt optimization, now it can give the exact line number where the error occurred more accurately.
- Bug fixes.
Version 5.4.1-2494
#### Rule Engine Optimizations
- The implementation of RULE-SET and DOMAIN-SET has been completely rewritten. Now, Surge automatically preprocesses and indexes rule sets during resource updates, significantly increasing the matching speed.
1. There is no longer any difference in performance and memory usage between RULE-SET and DOMAIN-SET types of rule sets, allowing flexible usage.
2. There is no longer a restriction in DOMAIN-SET rule sets that prevents the use of eTLDs.
3. The matching speed for DOMAIN, DOMAIN-SUFFIX, IP-CIDR, and IP-CIDR6 rules in RULE-SET has been greatly improved.
- A DOMAIN/DOMAIN-SUFFIX rule set with approximately 100,000 entries used to take 100ms for a single match in the old version; now, it only takes single-digit ms.
- An IP-CIDR rule set with approximately 10,000 entries used to take about 0.1ms for a single match in the old version. The new version only needs 0.0002ms, an improvement of about 500 times. The performance improvement for IP-CIDR6 rules is even greater.
4. In the new version, building a regional IP address collection using the IP-CIDR rule set offers the same performance as directly using the internal GEOIP rule.
5. The Inline Ruleset added in the previous version does not benefit from this optimization, but there is virtually no difference at the scale of hundreds of entries.
6. In previous versions, rules within a Ruleset were matched one by one from top to bottom. If rules requiring DNS resolution were included, DNS would only be triggered when starting to match that sub-rule. In the new version, if any rule requiring DNS resolution is included in the rule set, DNS resolution will occur before testing that rule set. (In most cases, there is no difference)
- Main ruleset matching efficiency has been slightly optimized.
- The efficiency of IP-CIDR6 rules has been significantly improved even in non-indexed situations.
- RULE-SET rules can now be configured directly with parameters no-resolve and extended-matching, which are equivalent to configuring all sub-rules with these parameters.
- DOMAIN-SET rule sets also support configuration with extended-matching.
#### Minor Optimizations
- Now, when performing MITM, the certificate used for signing will be sent to the client together, to support using intermediate certificates for MITM.
- All comments (at the beginning and end of lines) can now use
#, //, ; three common comment symbols.- Profile error message prompt optimization, now it can give the exact line number where the error occurred more accurately.
- Bug fixes.
Forwarded from Surge's Changelog
#iOS #TestFlight
Surge 5 5.21.0 (2964) is ready to test on iOS.
What to Test:
- 修正两处崩溃
- 在检测到设备重启后，主动清理 Fake IP 映射表，避免映射表无限增大
- 在进行 Fake IP 检查 DNS 查询域名的有效性，对无效查询不再分配地址
5.8.1 RC3
Surge 5 5.21.0 (2964) is ready to test on iOS.
What to Test:
- 修正两处崩溃
- 在检测到设备重启后，主动清理 Fake IP 映射表，避免映射表无限增大
- 在进行 Fake IP 检查 DNS 查询域名的有效性，对无效查询不再分配地址
5.8.1 RC3
Forwarded from Surge's Changelog
Forwarded from Surge's Changelog
#Mac #Beta
Version 5.4.1-2495
#### Rule Engine Optimizations
- The implementation of RULE-SET and DOMAIN-SET has been completely rewritten. Now, Surge automatically preprocesses and indexes rule sets during resource updates, significantly increasing the matching speed.
1. There is no longer any difference in performance and memory usage between RULE-SET and DOMAIN-SET types of rule sets, allowing flexible usage.
2. There is no longer a restriction in DOMAIN-SET rule sets that prevents the use of eTLDs.
3. The matching speed for DOMAIN, DOMAIN-SUFFIX, IP-CIDR, and IP-CIDR6 rules in RULE-SET has been greatly improved.
- A DOMAIN/DOMAIN-SUFFIX rule set with approximately 100,000 entries used to take 100ms for a single match in the old version; now, it only takes single-digit ms.
- An IP-CIDR rule set with approximately 10,000 entries used to take about 0.1ms for a single match in the old version. The new version only needs 0.0002ms, an improvement of about 500 times. The performance improvement for IP-CIDR6 rules is even greater.
4. In the new version, building a regional IP address collection using the IP-CIDR rule set offers the same performance as directly using the internal GEOIP rule.
5. The Inline Ruleset added in the previous version does not benefit from this optimization, but there is virtually no difference at the scale of hundreds of entries.
6. In previous versions, rules within a Ruleset were matched one by one from top to bottom. If rules requiring DNS resolution were included, DNS would only be triggered when starting to match that sub-rule. In the new version, if any rule requiring DNS resolution is included in the rule set, DNS resolution will occur before testing that rule set. (In most cases, there is no difference)
- Main ruleset matching efficiency has been slightly optimized.
- The efficiency of IP-CIDR6 rules has been significantly improved even in non-indexed situations.
- RULE-SET rules can now be configured directly with parameters no-resolve and extended-matching, which are equivalent to configuring all sub-rules with these parameters.
- DOMAIN-SET rule sets also support configuration with extended-matching.
#### Minor Optimizations
- Now, when performing MITM, the certificate used for signing will be sent to the client together, to support using intermediate certificates for MITM.
- All comments (at the beginning and end of lines) can now use
- Profile error message prompt optimization, now it can give the exact line number where the error occurred more accurately.
- Optimize Surge Ponte error handling process, correct the issue where device information is not automatically updated under certain errors.
- Bug fixes.
Version 5.4.1-2495
#### Rule Engine Optimizations
- The implementation of RULE-SET and DOMAIN-SET has been completely rewritten. Now, Surge automatically preprocesses and indexes rule sets during resource updates, significantly increasing the matching speed.
1. There is no longer any difference in performance and memory usage between RULE-SET and DOMAIN-SET types of rule sets, allowing flexible usage.
2. There is no longer a restriction in DOMAIN-SET rule sets that prevents the use of eTLDs.
3. The matching speed for DOMAIN, DOMAIN-SUFFIX, IP-CIDR, and IP-CIDR6 rules in RULE-SET has been greatly improved.
- A DOMAIN/DOMAIN-SUFFIX rule set with approximately 100,000 entries used to take 100ms for a single match in the old version; now, it only takes single-digit ms.
- An IP-CIDR rule set with approximately 10,000 entries used to take about 0.1ms for a single match in the old version. The new version only needs 0.0002ms, an improvement of about 500 times. The performance improvement for IP-CIDR6 rules is even greater.
4. In the new version, building a regional IP address collection using the IP-CIDR rule set offers the same performance as directly using the internal GEOIP rule.
5. The Inline Ruleset added in the previous version does not benefit from this optimization, but there is virtually no difference at the scale of hundreds of entries.
6. In previous versions, rules within a Ruleset were matched one by one from top to bottom. If rules requiring DNS resolution were included, DNS would only be triggered when starting to match that sub-rule. In the new version, if any rule requiring DNS resolution is included in the rule set, DNS resolution will occur before testing that rule set. (In most cases, there is no difference)
- Main ruleset matching efficiency has been slightly optimized.
- The efficiency of IP-CIDR6 rules has been significantly improved even in non-indexed situations.
- RULE-SET rules can now be configured directly with parameters no-resolve and extended-matching, which are equivalent to configuring all sub-rules with these parameters.
- DOMAIN-SET rule sets also support configuration with extended-matching.
#### Minor Optimizations
- Now, when performing MITM, the certificate used for signing will be sent to the client together, to support using intermediate certificates for MITM.
- All comments (at the beginning and end of lines) can now use
#, //, ; three common comment symbols.- Profile error message prompt optimization, now it can give the exact line number where the error occurred more accurately.
- Optimize Surge Ponte error handling process, correct the issue where device information is not automatically updated under certain errors.
- Bug fixes.
Forwarded from Surge's Changelog
#iOS #TestFlight
Surge 5 5.21.0 (2968) is ready to test on iOS.
What to Test:
- 修正当对 RULE-SET 配置 no-resolve 或 extended-matching 参数时，对子规则中的 IP-ASN/GEOIP/DOMAIN-KEYWORD 规则无法覆盖其参数的问题
5.8.1 RC5
如果一直频繁遇到更新后需要重置或重启的问题，请从 RC4 更新到 RC5 并参与下该调查：https://t.me/SurgeTestFlightFeed/53
Surge 5 5.21.0 (2968) is ready to test on iOS.
What to Test:
- 修正当对 RULE-SET 配置 no-resolve 或 extended-matching 参数时，对子规则中的 IP-ASN/GEOIP/DOMAIN-KEYWORD 规则无法覆盖其参数的问题
5.8.1 RC5
如果一直频繁遇到更新后需要重置或重启的问题，请从 RC4 更新到 RC5 并参与下该调查：https://t.me/SurgeTestFlightFeed/53
Telegram
Surge TestFlight Feed
如果你先前版本中，经常在更新 Surge iOS 后遇到需要重启或者重置才能使用的问题，请尝试在更新今日的 5.8.1 RC4 (Build 2965)后，再更新 RC5，观察是否还会出现这个问题。
之前频繁出现，从 RC4 更新到 RC5 没有再出现 / 之前频繁出现，从 RC4 更新到 RC5 依然出现了问题 / 几乎没有遇到过该问题
之前频繁出现，从 RC4 更新到 RC5 没有再出现 / 之前频繁出现，从 RC4 更新到 RC5 依然出现了问题 / 几乎没有遇到过该问题
Forwarded from Surge's Changelog
#Mac #Release
Version 5.4.1-2495
#### Rule Engine Optimizations
- The implementation of RULE-SET and DOMAIN-SET has been completely rewritten. Now, Surge automatically preprocesses and indexes rule sets during resource updates, significantly increasing the matching speed.
1. There is no longer any difference in performance and memory usage between RULE-SET and DOMAIN-SET types of rule sets, allowing flexible usage.
2. There is no longer a restriction in DOMAIN-SET rule sets that prevents the use of eTLDs.
3. The matching speed for DOMAIN, DOMAIN-SUFFIX, IP-CIDR, and IP-CIDR6 rules in RULE-SET has been greatly improved.
- A DOMAIN/DOMAIN-SUFFIX rule set with approximately 100,000 entries used to take 100ms for a single match in the old version; now, it only takes single-digit ms.
- An IP-CIDR rule set with approximately 10,000 entries used to take about 0.1ms for a single match in the old version. The new version only needs 0.0002ms, an improvement of about 500 times. The performance improvement for IP-CIDR6 rules is even greater.
4. In the new version, building a regional IP address collection using the IP-CIDR rule set offers the same performance as directly using the internal GEOIP rule.
5. The Inline Ruleset added in the previous version does not benefit from this optimization, but there is virtually no difference at the scale of hundreds of entries.
6. In previous versions, rules within a Ruleset were matched one by one from top to bottom. If rules requiring DNS resolution were included, DNS would only be triggered when starting to match that sub-rule. In the new version, if any rule requiring DNS resolution is included in the rule set, DNS resolution will occur before testing that rule set. (In most cases, there is no difference)
- Main ruleset matching efficiency has been slightly optimized.
- The efficiency of IP-CIDR6 rules has been significantly improved even in non-indexed situations.
- RULE-SET rules can now be configured directly with parameters no-resolve and extended-matching, which are equivalent to configuring all sub-rules with these parameters.
- DOMAIN-SET rule sets also support configuration with extended-matching.
#### Minor Optimizations
- Now, when performing MITM, the certificate used for signing will be sent to the client together, to support using intermediate certificates for MITM.
- All comments (at the beginning and end of lines) can now use
- Profile error message prompt optimization, now it can give the exact line number where the error occurred more accurately.
- Optimize Surge Ponte error handling process, correct the issue where device information is not automatically updated under certain errors.
- Bug fixes.
Version 5.4.1-2495
#### Rule Engine Optimizations
- The implementation of RULE-SET and DOMAIN-SET has been completely rewritten. Now, Surge automatically preprocesses and indexes rule sets during resource updates, significantly increasing the matching speed.
1. There is no longer any difference in performance and memory usage between RULE-SET and DOMAIN-SET types of rule sets, allowing flexible usage.
2. There is no longer a restriction in DOMAIN-SET rule sets that prevents the use of eTLDs.
3. The matching speed for DOMAIN, DOMAIN-SUFFIX, IP-CIDR, and IP-CIDR6 rules in RULE-SET has been greatly improved.
- A DOMAIN/DOMAIN-SUFFIX rule set with approximately 100,000 entries used to take 100ms for a single match in the old version; now, it only takes single-digit ms.
- An IP-CIDR rule set with approximately 10,000 entries used to take about 0.1ms for a single match in the old version. The new version only needs 0.0002ms, an improvement of about 500 times. The performance improvement for IP-CIDR6 rules is even greater.
4. In the new version, building a regional IP address collection using the IP-CIDR rule set offers the same performance as directly using the internal GEOIP rule.
5. The Inline Ruleset added in the previous version does not benefit from this optimization, but there is virtually no difference at the scale of hundreds of entries.
6. In previous versions, rules within a Ruleset were matched one by one from top to bottom. If rules requiring DNS resolution were included, DNS would only be triggered when starting to match that sub-rule. In the new version, if any rule requiring DNS resolution is included in the rule set, DNS resolution will occur before testing that rule set. (In most cases, there is no difference)
- Main ruleset matching efficiency has been slightly optimized.
- The efficiency of IP-CIDR6 rules has been significantly improved even in non-indexed situations.
- RULE-SET rules can now be configured directly with parameters no-resolve and extended-matching, which are equivalent to configuring all sub-rules with these parameters.
- DOMAIN-SET rule sets also support configuration with extended-matching.
#### Minor Optimizations
- Now, when performing MITM, the certificate used for signing will be sent to the client together, to support using intermediate certificates for MITM.
- All comments (at the beginning and end of lines) can now use
#, //, ; three common comment symbols.- Profile error message prompt optimization, now it can give the exact line number where the error occurred more accurately.
- Optimize Surge Ponte error handling process, correct the issue where device information is not automatically updated under certain errors.
- Bug fixes.
Forwarded from Surge TestFlight Feed
正式版版本更新
· Surge iOS 5.8.1 正式版本已在 App Store 上线，预计数小时后可进行更新。
· Surge Mac 5.4.1 正式版本也已一同发布。
· Surge iOS 5.8.1 正式版本已在 App Store 上线，预计数小时后可进行更新。
· Surge Mac 5.4.1 正式版本也已一同发布。
Forwarded from Surge's Changelog
#iOS #TestFlight
Surge 5 5.21.0 (2971) is ready to test on iOS.
What to Test:
- 修正 LAN 规则集无法触发 DNS 解析的问题
Surge 5 5.21.0 (2971) is ready to test on iOS.
What to Test:
- 修正 LAN 规则集无法触发 DNS 解析的问题
Forwarded from Surge's Changelog
#iOS #TestFlight
Surge 5 5.21.0 (2973) is ready to test on iOS.
What to Test:
- 修正在处理一些畸形的 UDP 时可能导致崩溃的问题。
- 与 Hysteria 2 作者沟通确认，服务端由于涉及上游库的调整，短时间内无法完成更新，为此在客户端侧加入了一项 workaround 以支持 QUIC 转发。
- 修正在更新大体积 DOMAIN-SET 时，建立索引的突发内存占用可能超限导致退出的问题。
- 修正可能意外判断系统已被重启导致 Fake IP 表被清理的问题。
- 兼容部分不太标准的 SOCKS5 UDP 服务端实现，将错误调整为了警告。
- 修正 iOS UI 编辑 IP-CIDR6 规则时，输入无效内容会崩溃的问题。
- 当 Surge iOS 不是首选 VPN Profile 时，通过 Widget 进行开启将给于通知提示错误
- 修正通过 iOS App 快捷菜单进入的网络诊断页面依然是旧版诊断的问题
Surge 5 5.21.0 (2973) is ready to test on iOS.
What to Test:
- 修正在处理一些畸形的 UDP 时可能导致崩溃的问题。
- 与 Hysteria 2 作者沟通确认，服务端由于涉及上游库的调整，短时间内无法完成更新，为此在客户端侧加入了一项 workaround 以支持 QUIC 转发。
- 修正在更新大体积 DOMAIN-SET 时，建立索引的突发内存占用可能超限导致退出的问题。
- 修正可能意外判断系统已被重启导致 Fake IP 表被清理的问题。
- 兼容部分不太标准的 SOCKS5 UDP 服务端实现，将错误调整为了警告。
- 修正 iOS UI 编辑 IP-CIDR6 规则时，输入无效内容会崩溃的问题。
- 当 Surge iOS 不是首选 VPN Profile 时，通过 Widget 进行开启将给于通知提示错误
- 修正通过 iOS App 快捷菜单进入的网络诊断页面依然是旧版诊断的问题
Forwarded from Surge's Changelog
#iOS #TestFlight
Surge 5 5.21.0 (2976) is ready to test on iOS.
What to Test:
- 暂时移除了前几个版本加入的 Fake IP 映射表自动清理功能以避免产生问题
- 其他细节问题修正
5.8.2 RC1
Surge 5 5.21.0 (2976) is ready to test on iOS.
What to Test:
- 暂时移除了前几个版本加入的 Fake IP 映射表自动清理功能以避免产生问题
- 其他细节问题修正
5.8.2 RC1
Forwarded from Surge's Changelog
#iOS #TestFlight
Surge 5 5.21.0 (2979) is ready to test on iOS.
What to Test:
- 修正了与特定 HTTP 服务器的一个兼容性问题（如 115 播放视频）
5.8.2 RC2
Surge 5 5.21.0 (2979) is ready to test on iOS.
What to Test:
- 修正了与特定 HTTP 服务器的一个兼容性问题（如 115 播放视频）
5.8.2 RC2