Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

新版本使用geosite导致winstore无法加载 #2974

Closed
zed76r opened this issue Oct 3, 2020 · 9 comments · Fixed by #2982
Closed

新版本使用geosite导致winstore无法加载 #2974

zed76r opened this issue Oct 3, 2020 · 9 comments · Fixed by #2982

Comments

@zed76r
Copy link

zed76r commented Oct 3, 2020

简要描述问题

更新版本后使用新版的geosite数据,在pac模式下无法正常打开winstore,并且大略的查询几个常见的地址都并非被墙网站。
希望能换回之前的gfwlist或者提供选项。

环境

  • Shadowsocks客户端版本:4.2.0.1
  • 操作系统版本:Win10 2004
  • .NET版本:

操作步骤

  1. 更新ss-win + 使用geosite更新本地pac
  2. 设置为pac模式
  3. 打开winstore

期望的结果

正常打开

实际结果

疑似因为通过代理请求导致winstore无法正常加载

配置文件和日志文件(请隐去敏感信息)

在此粘贴日志
@database64128
Copy link
Contributor

database64128 commented Oct 3, 2020

According to your description, I think it's an intended behavior that traffic to certain Windows Store sites are routed to the proxy. The problem you encountered is actually due to UWP loopback restrictions. Please use https://telerik-fiddler.s3.amazonaws.com/fiddler/addons/enableloopbackutility.exe to allow Windows Store and other store apps access to localhost.

@chenshaoju
Copy link
Collaborator

chenshaoju commented Oct 3, 2020

测试了一下,的确是本地环回的问题,按照楼上提供的方法可以解决。

如果不希望使用本地环回(或让商店代理),可采取下面的临时方案:

临时方案1:
请尝试退出SS,将此文件保存到 Shadowsocks.exe 所在目录,然后再启动SS即可。
pac.txt

临时方案2:
请尝试退回到 4.1.10.0 版本:https://github.com/shadowsocks/shadowsocks-windows/releases/tag/4.1.10.0 ,退回后请记得删除 pac.txt 并重新更新本地PAC。

@ghost ghost added the third-party bug label Oct 5, 2020
@ghost
Copy link

ghost commented Oct 5, 2020

@ghost ghost closed this as completed Oct 5, 2020
@zed76r
Copy link
Author

zed76r commented Oct 6, 2020

@studentmain

我不认为这是简单的第三方bug。在你ref的issue里原contributor有提到一个关键内容

似乎自 v2fly/domain-list-community#215 起开始生成新文件供其它项目使用了?缓兵之计或许是在生成文件时去除标记有@cn的域名。但geolocation-!cn与gfwlist的定位似乎相差较大。

这里原作者的说法与我的想法基本一致,即便不考虑启动uwp loopback带来的安全隐患,也需要考虑大部分属于微软和xbox的域名并不需要代理的情况。譬如,微软商店的内容实际上有大陆的CDN,xbox亦如此。

我的结论是:现阶段根据 v2fly/domain-list-community 定位与 gfwlist/gfwlist 相差较远的情况下,不应该简单的使用前者替代后者。或者至少给出一个切换的方案。

@database64128
Copy link
Contributor

  1. Allowing loopback access for UWP apps is not a security concern. In fact, most 3rd party proprietary software is way worse than you think regarding security.
  2. shadowsocks-windows now uses dlc directly instead of using the generated txt file.

@zed76r
Copy link
Author

zed76r commented Oct 11, 2020

@database64128 我认为替换回gfwlist或者保留可选项是相对更好的方式。无论在uwp需要额外设置回环,还是domain-list的设计用途上,直接使用替代gfwlist都不是一个很合适的方案。

或者更进一步的采取类似v2rayN那样通过用户自行设置路由来满足不同场景的需要。

@database64128
Copy link
Contributor

gfwlist has been poorly maintained for too long. It's not coming back. As for routing, PR is always welcome.

@chenshaoju
Copy link
Collaborator

请不要到处发,移动到:#3020 (comment)

@zed76r
Copy link
Author

zed76r commented Dec 19, 2020

请不要到处发,移动到:#3020 (comment)

呵呵

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants