Github pages 的 HTTPS 是不是出问题了？

WoodenRobot · 2020-03-26T06:14:13Z

所有的 github pages 页面开启 HTTPS 的话证书都变成下面这个了？什么情况？

GitHub

Pages

证书

页面

333 replies • 2024-10-26 19:26:58 +08:00

1 2 3 4

❮

❯

twoyuan

Mar 26, 2020

1

来自 “[email protected]” 的中间人攻击

WoodenRobot

OP

Mar 26, 2020

2

@twoyuan 手机网络也是一样的，WiFi 也一样？有点奇怪啊

imkuang

Mar 26, 2020

3

这个电子邮件地址明显就有问题吧

SpringHack

Mar 26, 2020

4

+1，自己的 github pages 也是这个

alphardex

Mar 26, 2020

5

同样也碰到了这个问题

WoodenRobot

OP

Mar 26, 2020

6

@xiri 对明显的有问题，还能搜到那个人 QQ 号，加好友不通过

Livid

MOD

PRO

Mar 26, 2020

7

解析出来的服务器 IP 是？

bin21st

Mar 26, 2020

8

@WoodenRobot 我也是这样，然后谷歌搜到了这个页面

WoodenRobot

OP

Mar 26, 2020

9

@Livid 185.199.111.153 我自己的是这个，这就是 GitHub 的服务器地址

WoodenRobot

OP

Mar 26, 2020

10

里面 QQ 搜到是这个![image.png]( https://i.loli.net/2020/03/26/NDZPbLHsCl4ptIe.png)

Livid

MOD

PRO

Mar 26, 2020

11

贴一下 curl -k -v 访问你的 GitHub Pages 的记录？

Melodyer

Mar 26, 2020

12

同！！

Melodyer

Mar 26, 2020

13

@Livid
➜ ~ curl -k -v githubstatus.com
* Trying 185.199.109.153...
* TCP_NODELAY set
* Connected to githubstatus.com (185.199.109.153) port 80 (#0)
> GET / HTTP/1.1
> Host: githubstatus.com
> User-Agent: curl/7.64.1
> Accept: */*
>
< HTTP/1.1 301 Moved Permanently
< Content-Type: text/html
< Server: GitHub.com
< Location: https://githubstatus.com/
< X-GitHub-Request-Id: F20A:6F7C:2B28AA:2D7250:5E7C4D04
< Content-Length: 162
< Accept-Ranges: bytes
< Date: Thu, 26 Mar 2020 06:34:44 GMT
< Via: 1.1 varnish
< Age: 0
< Connection: keep-alive
< X-Served-By: cache-hnd18728-HND
< X-Cache: MISS
< X-Cache-Hits: 0
< X-Timer: S1585204484.464009,VS0,VE170
< Vary: Accept-Encoding
< X-Fastly-Request-ID: 1a3048f21b2a3e7f00c0e09aeae99a8a47d088ed
<
<html>
<head><title>301 Moved Permanently</title></head>
<body>
<center><h1>301 Moved Permanently</h1></center>
<hr><center>nginx</center>
</body>
</html>
* Connection #0 to host githubstatus.com left intact
* Closing connection 0
➜ ~

Xusually

Mar 26, 2020

14

@WoodenRobot 根据 qq 信息的域名
Domain Name: 138qb.cn
ROID: 20091121s10001s80146151-cn
Domain Status: clientTransferProhibited
Registrant ID: 120411033010813
Registrant: 广州名扬信息科技有限公司
Registrant Contact Email: **[email protected]
Sponsoring Registrar: 广州名扬信息科技有限公司
Name Server: ns1.dnparking.com
Name Server: ns2.dnparking.com
Name Server: ns3.dnparking.com
Name Server: ns4.dnparking.com
Registration Time: 2009-11-21 04:27:12
Expiration Time: 2020-11-21 04:27:12
DNSSEC: unsigned

showmethetalk

Mar 26, 2020

15

+1 我也这样了。。

leadream4

Mar 26, 2020

16

我的也是，全局可以访问，好奇怪。

fuergaosi

Mar 26, 2020

17

访问 jestjs.io 遇到了同样的问题
![GStyMq.png]( https://s1.ax1x.com/2020/03/26/GStyMq.png)
Server: 114.114.114.114
Address: 114.114.114.114#53

Non-authoritative answer:
Name: jestjs.io
Address: 185.199.108.153
Name: jestjs.io
Address: 185.199.111.153
Name: jestjs.io
Address: 185.199.110.153
Name: jestjs.io
Address: 185.199.109.153
看起来是跟上面一样解析到了一个 ip 上，是 dns 劫持，还是 dns 有问题呢？
另外手机访问也同样遇到了这个证书。

WoodenRobot

OP

Mar 26, 2020

18

@Livid
```
$ curl -k -v https://woodenrobot.me
* Rebuilt URL to: https://woodenrobot.me/
* Trying 185.199.108.153...
* TCP_NODELAY set
* Connected to woodenrobot.me (185.199.108.153) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
* CAfile: /etc/ssl/cert.pem
CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Client hello (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-ECDSA-AES128-GCM-SHA256
* ALPN, server did not agree to a protocol
* Server certificate:
* subject: C=CN; ST=GD; L=SZ; O=COM; OU=NSP; CN=SERVER; [email protected]
* start date: Sep 26 09:33:13 2019 GMT
* expire date: Sep 23 09:33:13 2029 GMT
* issuer: C=CN; ST=GD; L=SZ; O=COM; OU=NSP; CN=CA; [email protected]
* SSL certificate verify result: self signed certificate in certificate chain (19), continuing anyway.
> GET / HTTP/1.1
> Host: woodenrobot.me
> User-Agent: curl/7.54.0
> Accept: */*
```

WoodenRobot

OP

Mar 26, 2020

19

@fuergaosi 这些地址都是 GitHub pages 的服务器，他应该用的 GitHub pages

Windelight

Mar 26, 2020 via Android

20

遇到了同样的问题，河北联通。

U7Q5tLAex2FI0o0g

Mar 26, 2020

21

亲测，不番羽确实那样，番羽了只后不会

Livid

MOD

PRO

Mar 26, 2020

22

@WoodenRobot 那么 curl 加了 -k 之后能加载出来你网站上本来的内容么？

WoodenRobot

OP

Mar 26, 2020

23

@Livid sorry, 代码块有问题
不能每个回复都有外链，我把下面我的域名用 xxxx 代替了
$ curl -k -v xxxx
* Rebuilt URL to: xxxx
* Trying 185.199.108.153...
* TCP_NODELAY set
* Connected to xxxx (185.199.108.153) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
* CAfile: /etc/ssl/cert.pem
CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Client hello (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-ECDSA-AES128-GCM-SHA256
* ALPN, server did not agree to a protocol
* Server certificate:
* subject: C=CN; ST=GD; L=SZ; O=COM; OU=NSP; CN=SERVER; [email protected]
* start date: Sep 26 09:33:13 2019 GMT
* expire date: Sep 23 09:33:13 2029 GMT
* issuer: C=CN; ST=GD; L=SZ; O=COM; OU=NSP; CN=CA; [email protected]
* SSL certificate verify result: self signed certificate in certificate chain (19), continuing anyway.
> GET / HTTP/1.1
> Host: xxxx
> User-Agent: curl/7.54.0
> Accept: */*

xg4

Mar 26, 2020

24

+1 刚刚访问提示网站风险，还以为输错了地址，看了下证书，发现有个 qq 号的邮箱，google qq 号找到这个

showmethetalk

Mar 26, 2020

25

@Livid #22 可以加载

Windelight

Mar 26, 2020

1

26

pi@raspberrypi:~ $ curl -k -v https://zongsoft.github.io
* Expire in 0 ms for 6 (transfer 0x1a44770)
-------- Something Similar --------
* Expire in 200 ms for 1 (transfer 0x1a44770)
* Trying 185.199.111.153...
* TCP_NODELAY set
* Expire in 148365 ms for 3 (transfer 0x1a44770)
* Expire in 200 ms for 4 (transfer 0x1a44770)
* Connected to zongsoft.github.io (185.199.111.153) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: none
CApath: /etc/ssl/certs
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-ECDSA-AES128-GCM-SHA256
* ALPN, server did not agree to a protocol
* Server certificate:
* subject: C=CN; ST=GD; L=SZ; O=COM; OU=NSP; CN=SERVER; [email protected]
* start date: Sep 26 09:33:13 2019 GMT
* expire date: Sep 23 09:33:13 2029 GMT
* issuer: C=CN; ST=GD; L=SZ; O=COM; OU=NSP; CN=CA; [email protected]
* SSL certificate verify result: self signed certificate in certificate chain (19), continuing anyway.
> GET / HTTP/1.1
> Host: zongsoft.github.io
> User-Agent: curl/7.64.0
> Accept: */*
>

奇怪的是不能加载出任何内容

lovedebug

Mar 26, 2020

27

江苏电信测试结果也是重定向到 185.199.111.153

WoodenRobot

OP

Mar 26, 2020

1

28

@Livid 国内访问加载不全，只能加载一部分就出现下面内容中断了，国外访问没问题

* LibreSSL SSL_read: SSL_ERROR_SYSCALL, errno 54
* stopped the pause stream!
* Closing connection 0
curl: (56) LibreSSL SSL_read: SSL_ERROR_SYSCALL, errno 54

WoodenRobot

OP

Mar 26, 2020

29

@lovedebug
185.199.108.153
185.199.109.153
185.199.110.153
185.199.111.153

上面这些地址都是 GitHub pages 的服务器

AoTmmy

Mar 26, 2020 via Android

30

联通复现

caola

Mar 26, 2020

31

我的好几个域名都这样，造成无法访问，持续了大半天时间

YS5RhZIi09QH7T9D

Mar 26, 2020

32

@twoyuan https://i.loli.net/2020/03/25/82TVeI4WkrjS95A.png
我昨天看自己的网站，也发现了这个人的 QQ 邮箱

mcone

Mar 26, 2020

33

怎么感觉是中间人公鸡

LaTero

Mar 26, 2020

34

dns 没问题的，海外 curl --resolve xxx:443:185.199.108.153 xxxps://xxx 可以正常访问。

jiejiss

Mar 26, 2020

35

移动没有复现

TL;DR
issuer: C=US; O=Let's Encrypt; CN=Let's Encrypt Authority X3;
issuer: C=US; O=DigiCert Inc; OU=www.digicert.com; CN=DigiCert SHA2 High Assurance Server CA

* Rebuilt URL to: https://woodenrobot.me/
* Trying 185.199.108.153...
* TCP_NODELAY set
* Connected to woodenrobot.me (127.0.0.1) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
* CAfile: /etc/ssl/cert.pem
CApath: none
* // ... ...
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* ALPN, server accepted to use h2
* Server certificate:
* subject: CN=woodenrobot.me
* start date: Feb 2 09:35:52 2020 GMT
* expire date: May 2 09:35:52 2020 GMT
* issuer: C=US; O=Let's Encrypt; CN=Let's Encrypt Authority X3
* SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x7fa13b004400)
> GET / HTTP/2
> Host: woodenrobot.me
> User-Agent: curl/7.54.0
> Accept: */*
>
* Connection state changed (MAX_CONCURRENT_STREAMS updated)!
^C

* Rebuilt URL to: https://zongsoft.github.io/
* Trying 185.199.111.153...
* TCP_NODELAY set
* Connected to zongsoft.github.io (127.0.0.1) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
* CAfile: /etc/ssl/cert.pem
CApath: none
* // ... ...
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* ALPN, server accepted to use h2
* Server certificate:
* subject: C=US; ST=California; L=San Francisco; O=GitHub, Inc.; CN=www.github.com
* start date: Jun 27 00:00:00 2018 GMT
* expire date: Jun 20 12:00:00 2020 GMT
* issuer: C=US; O=DigiCert Inc; OU=www.digicert.com; CN=DigiCert SHA2 High Assurance Server CA
* SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x7feb0b000000)
> GET / HTTP/2
> Host: zongsoft.github.io
> User-Agent: curl/7.54.0
> Accept: */*
>
* Connection state changed (MAX_CONCURRENT_STREAMS updated)!
^C

Windelight

Mar 26, 2020 via Android

36

这个 ip 地址的确是连接到了 Github 的服务器，美国 GitHub#Fastly，纯真查的，然后这个证书信息有个大概的地址写的是 CN GD SZ COM NSP，QQ 号 346608453，一个哈尔滨大哥

J0G57faC6uPo75W0

Mar 26, 2020

37

没有代理时遇到了同样的问题.
错误是:" FetchEvent.respondWith received an error TypeError: 此服务器的证书无效. 您可能正在连接到一个伪装成"网址"的服务器.

嗯, 提示很明显了.

上了代理就正常了.

hah, 这件事终于要发生了嘛...

imkuang

Mar 26, 2020

38

上面你们发的那几个地址加上代理就没有问题，国内直接访问确实证书都存在问题，有人在大范围劫持？中间人攻击？

gz911122

Mar 26, 2020

39

我的也是这样 ,从 google 搜到了这个帖子

SomeBottle

Mar 26, 2020

40

博客上了亚太 cdn 倒是没问题，大陆访问直接就证书错误了...那个 QQ 号看上去也像是顶锅的

lishu5566

Mar 26, 2020

41

全局代理证书就正常了；有什么大的事情要发生吗？

SaigyoujiYuyuko

Mar 26, 2020

42

看起来是中间人?... 使用 55r 代理证书正常直接连接证书错误

chinvo

Mar 26, 2020

43

解析出来的 IP 是对的, 但是访问过去证书错误

这么大规模的 IP 劫持, 细思恐极

Greatshu

Mar 26, 2020

44

吓死我了，还以为我的博客被认证了。结果是大规模劫持啊，放心了。

genezx

Mar 26, 2020

45

上海、浙江、湖北、广东、电信、联通全部中招，看来国内都中招了

zackwu

Mar 26, 2020

46

浙江移动，未能复现。

HXM

Mar 26, 2020 via Android

47

可复现

angles6645

Mar 26, 2020 via Android

48

电信 4G 复现了

Windelight

Mar 26, 2020

49

这大哥也太不认真了，叫啥住哪长啥样都靠一个 qq 出来了。
但是我认为他可能只是一个运维或者码农，签了一个内部测试用的证书
然后不知道被谁拿去配置错了-_-||
结果还是可能某个中间的 CDN 或者审查服务器上。
希望这大哥能保住工作吧，就算给他祈福了。
希望 Fastly 可以不太 Fastly

imkuang

Mar 26, 2020

50

刚刚发现不只是这些博客，https://pages.github.com/ 也证书错误了

caishuhao2000

Mar 26, 2020

51

上海电信复现

billchenchina

Mar 26, 2020 via Android

52

https://i.loli.net/2020/03/26/KRsIaBXol4yjzDf.jpg

443 端口 mtr
恭喜 github 和北京电信直连（ doge

rayhy

Mar 26, 2020

53

山西联通复现

isukkaw

Mar 26, 2020

2

54

Fastly 其他服务都没影响，唯独 GitHub 交给 Fastly 代播的 IP 炸了，多半是国内哪个 xx 不小心路由风暴了

mom0a

Mar 26, 2020

55

辽宁联通复现

est

Mar 26, 2020

56

向当地通管局举报。破坏信息系统。

billchenchina

Mar 26, 2020

57

#54 @isukkawicmp mtr 没炸，

lishu5566

Mar 26, 2020

58

有没有大神，人肉一下这个 QQ ！估计是个背锅侠。

billchenchina

Mar 26, 2020

59

#54 @isukkaw
icmp mtr 没炸，仍然是 ntt - fastly 。单纯 TCP 劫持了

chenshaoju

Mar 26, 2020

1

60

导出的证书：

https://gist.github.com/chenshaoju/52bb7a12572a752433bd51a4dce79d94

jhdsgfww

Mar 26, 2020

61

补充一下，山东移动也不行（至少我所在的地区不行）

isukkaw

Mar 26, 2020

62

@billchenchina #59 看了一下，仅 443 TCP 会在广州电信这一跳被劫持掉。

U7Q5tLAex2FI0o0g

Mar 26, 2020

63

最新：github.com 也中了

xolor

Mar 26, 2020

64

希望是暂时的，不要变为常态呀...

rayhy

Mar 26, 2020

65

@littleylv 我这里 github.com 暂时没炸，只有 github pages

YS5RhZIi09QH7T9D

Mar 26, 2020

66

@xolor 我昨天下午就遇到了。。。

U7Q5tLAex2FI0o0g

Mar 26, 2020

67

@littleylv #63
@rayhy #65
抱歉，是 desktop.github.com

FIyingSky

Mar 26, 2020

68

浙江移动，未能复现……

unifier

Mar 26, 2020

69

山东联通中招

Howard2000

Mar 26, 2020

1

70

广东移动复现

fanyuxi

Mar 26, 2020

71

刚刚发现同样的问题，在 bing 搜了一下这个邮箱，搜到这个帖子。
（广州电信）

mzlogin

Mar 26, 2020

72

+1，武汉电信复现

```
~$ curl -k -v https://mazhuang.org [master]
* Trying 185.199.108.153...
* TCP_NODELAY set
* Connected to mazhuang.org (185.199.108.153) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/ssl/cert.pem
CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-ECDSA-AES128-GCM-SHA256
* ALPN, server did not agree to a protocol
* Server certificate:
* subject: C=CN; ST=GD; L=SZ; O=COM; OU=NSP; CN=SERVER; [email protected]
* start date: Sep 26 09:33:13 2019 GMT
* expire date: Sep 23 09:33:13 2029 GMT
* issuer: C=CN; ST=GD; L=SZ; O=COM; OU=NSP; CN=CA; [email protected]
* SSL certificate verify result: self signed certificate in certificate chain (19), continuing anyway.
```

zackwu

Mar 26, 2020

73

完了，用 https://17ce.com/ 测试下来，全国大部分地区都中招了。

fenghuang

Mar 26, 2020

74

这个劫持是怎么实现的呢

Valid

Mar 26, 2020

75

在座的各位肯定都查了那个 qq

linnaea

Mar 26, 2020

76

@fenghuang 基于策略路由（ PBR ），ip rule 了解一下

Windelight

Mar 26, 2020

77

@lishu5566 新法规已于 3 月 1 号实行了 :-)
icmp4 跳的是
AS4837 - AS2914 - AS54113

17ce 测试，全国只有中部个别地区正常
http://www.17ce.com/site/http/20200326_7ee6f8306f3411eab8bc2bbb7b33a12c:1.html

hpx9797

Mar 26, 2020

78

内蒙联通复线 github 相关一些域名经常打不开

dven

Mar 26, 2020

79

大概是某个 ISP 或 IDC 漏路由，但具体是谁，不好确定

rapiz

Mar 26, 2020

80

@linnaea 真的么。路由只能管 ip 转发，不能改包吧。

002jnm

Mar 26, 2020

81

C:\Users\admin>tcping 185.199.109.153 443

Probing 185.199.109.153:443/tcp - Port is open - time=6.733ms
Probing 185.199.109.153:443/tcp - Port is open - time=6.790ms
Probing 185.199.109.153:443/tcp - Port is open - time=5.762ms
Probing 185.199.109.153:443/tcp - Port is open - time=5.417ms

EdPlaysMC

Mar 26, 2020

82

广东电信复现，似乎是劫持了 443 端口，80 端口正常日本 NTT

hszhakka2ex

Mar 26, 2020

83

镜像话题： https://www.v2ex.com/t/656394

Ansonyi

Mar 26, 2020

84

浙江金华移动电信复现

LokiSharp

Mar 26, 2020

85

@Xusually #14 域名过期回收了吧

chenshaoju

Mar 26, 2020

4

86

tracert / tcptracert 了一下，在某节点后就直接到达了，延迟很低，推测是国内劫持了这个 IP 端口。

https://imgur.com/a/qxQe7V8

xnotepad

Mar 26, 2020

87

浙江联通流量好像可以访问了，速度还挺快的，不知道是不是暂时的。

Sk3y

Mar 26, 2020

88

大连电信已复现该错误。

这个 QQ 是哪位高人的...

lishu5566

Mar 26, 2020

89

@Windelight Got it ！

Kangnakamuyi

Mar 26, 2020

90

河北联通 4G 也炸了
这 Fastly 今天是怎么回事啊......

Esen

Mar 26, 2020

91

暂时关闭了 https，虽然没人访问我的 pages

jiejiss

Mar 26, 2020

92

北京移动，https://desktop.github.com/ 中招，估计别的网址也一样

skyeycirno

Mar 26, 2020

93

黑龙江电信没问题。一切正常。。

codingAlex

Mar 26, 2020

94

安徽电信，一切正常啊。

INTEL2333

Mar 26, 2020

95

广州电信挂了，应该是劫持到本地的了，平均 tcping443 的延迟 3ms

linnaea

Mar 26, 2020

96

@rapiz PBR 转发到拦截机上，拦截机无视目标地址接受连接（ Linux 下的 TPROXY ）

yEhwG10ZJa83067x

Mar 26, 2020

97

浙江电信，复现

yulihao

Mar 26, 2020

98

阿里云上海复现
Tracing route to github.io:443
1 2044 ms timed out
1 2001 ms timed out
1 2002 ms timed out
2 21 ms 11.53.4.217 TimeExceeded
3 2002 ms timed out
3 2001 ms timed out
3 2001 ms timed out
4 2 ms 10.255.106.101 TimeExceeded
5 24 ms 103.49.76.110 TimeExceeded
6 3 ms 116.251.113.189 TimeExceeded
7 2003 ms timed out
7 2001 ms timed out
7 2002 ms timed out
8 7 ms 101.95.208.33 TimeExceeded
9 13 ms 124.74.166.9 TimeExceeded
10 16 ms 101.95.120.198 TimeExceeded
11 11 ms 185.199.109.153:443 Synchronize, Acknowledgment (port open)

rssvtwoex

Mar 26, 2020

99

深圳电信复现

alect

Mar 26, 2020

100

套一层 CloudFlare 可以解决吧？

1 2 3 4

❮

❯