Zh:Protocol Encryption - Revision history

imported>Hendrix-Shen: /* Authentication */

2021-08-26T09:27:04Z

Authentication

← Older revision		Revision as of 09:27, 26 August 2021
Line 51:		Line 51:
	[[File:Icon_exclaim.gif\|:!:]] Note that the AES cipher is updated continuously, not finished and restarted every packet.		[[File:Icon_exclaim.gif\|:!:]] Note that the AES cipher is updated continuously, not finished and restarted every packet.

	== ~~Authentication~~ ==		== 认证 ==

	~~Both server and client need to make a request to~~ sessionserver.mojang.com ~~if the server is in online-mode.~~		若服务端为正版验证模式，则客户端端和服务端都需要向 sessionserver.mojang.com 发起请求。

	=== ~~Client~~ ===		=== 客户端 ===

	~~After generating the shared secret~~, ~~the client generates the following hash~~:		在生成公共秘钥后, 客户端端将产生如下的哈希值:

	sha1 := Sha1()		sha1 := Sha1()
	sha1.update(~~ASCII encoding of the server id string from Encryption Request~~)		sha1.update(来自加密请求中使用ASCII编码的服务器ID)
	sha1.update(~~shared secret~~)		sha1.update(公共秘钥)
	sha1.update(~~server's encoded public key from Encryption Request~~)		sha1.update(来自加密请求中服务端编码的公钥)
	hash := sha1.hexdigest() # ~~String of hex characters~~		hash := sha1.hexdigest() # 16进制字符串

	[[File:Icon_exclaim.gif\|:!:]] Note that the Sha1.hexdigest() method used by minecraft is non standard. It doesn't match the digest method found in most programming languages and libraries. It works by treating the sha1 output bytes as one large integer in two's complement and then printing the integer in base 16, placing a minus sign if the interpreted number is negative. Some examples of the minecraft digest are found below:		[[File:Icon_exclaim.gif\|:!:]] Note that the Sha1.hexdigest() method used by minecraft is non standard. It doesn't match the digest method found in most programming languages and libraries. It works by treating the sha1 output bytes as one large integer in two's complement and then printing the integer in base 16, placing a minus sign if the interpreted number is negative. Some examples of the minecraft digest are found below:

imported>Lambol: /* 附加连接 */

2019-12-20T11:57:20Z

附加连接

← Older revision		Revision as of 11:57, 20 December 2019
Line 127:		Line 127:
	* Rust: https://git.io/fj6P0		* Rust: https://git.io/fj6P0

	== ~~附加连接~~ ==		== 参考链接 ==
	[https://msdn.microsoft.com/en-us/library/windows/desktop/bb648640(v=vs.85).aspx DER Encoding of ASN.1 Types]		[https://msdn.microsoft.com/en-us/library/windows/desktop/bb648640(v=vs.85).aspx DER Encoding of ASN.1 Types]

imported>Lambol: /* Additional Links */

2019-12-20T11:56:33Z

Additional Links

← Older revision		Revision as of 11:56, 20 December 2019
Line 127:		Line 127:
	* Rust: https://git.io/fj6P0		* Rust: https://git.io/fj6P0

	== ~~Additional Links~~ ==		== 附加连接 ==
	[https://msdn.microsoft.com/en-us/library/windows/desktop/bb648640(v=vs.85).aspx DER Encoding of ASN.1 Types]		[https://msdn.microsoft.com/en-us/library/windows/desktop/bb648640(v=vs.85).aspx DER Encoding of ASN.1 Types]

imported>Lambol: /* 样例代码 */

2019-12-20T11:55:47Z

样例代码

← Older revision		Revision as of 11:55, 20 December 2019
Line 117:		Line 117:

	Examples of generating Minecraft-style hex digests:		Examples of generating Minecraft-style hex digests:
	~~一些关于生成Minecraft风格的以二进制呈现的十六进制数据例子~~		一些关于生成Minecraft风格的十六进制数据的例子

	* C#: https://git.io/fhjp6		* C#: https://git.io/fhjp6

imported>Lambol: /* 样例代码 */

2019-12-14T07:47:45Z

样例代码

← Older revision		Revision as of 07:47, 14 December 2019
Line 117:		Line 117:

	Examples of generating Minecraft-style hex digests:		Examples of generating Minecraft-style hex digests:
	~~一些例子关于生成Minecraft风格的以二进制呈现的十六进制数据~~		一些关于生成Minecraft风格的以二进制呈现的十六进制数据例子

	* C#: https://git.io/fhjp6		* C#: https://git.io/fhjp6

imported>Lambol: /* Sample Code */

2019-12-14T07:47:00Z

Sample Code

← Older revision		Revision as of 07:47, 14 December 2019
Line 114:		Line 114:
	"11111111222233334444555555555555" which needs to be changed into format "11111111-2222-3333-4444-555555555555" before sending it back to the client.		"11111111222233334444555555555555" which needs to be changed into format "11111111-2222-3333-4444-555555555555" before sending it back to the client.

	=== ~~Sample Code~~ ===		=== 样例代码 ===

	Examples of generating Minecraft-style hex digests:		Examples of generating Minecraft-style hex digests:
			一些例子关于生成Minecraft风格的以二进制呈现的十六进制数据

	* C#: https://git.io/fhjp6		* C#: https://git.io/fhjp6

imported>Lambol: /* 密钥交换 */

2019-12-14T07:43:40Z

密钥交换

← Older revision		Revision as of 07:43, 14 December 2019
Line 23:		Line 23:
	== 密钥交换 ==		== 密钥交换 ==

	~~The server generates a 1024-bit RSA keypair on startup~~. ~~The public key is sent in the Encryption Request packet in DER encoding format. More technically, it is in ASN.1 format as defined by x.509 with the structure looking as follows~~.		在服务端启动的时候，服务端会生成一个1024位的RSA密钥对。服务端会以DER编码将公钥写进经加密的数据请求包中。从技术实现层面上讲，这个公钥是以由x.509定义的ASN.1形式呈现，其具体的数据结构如下所示：

	SubjectPublicKeyInfo ::= SEQUENCE {		SubjectPublicKeyInfo ::= SEQUENCE {
Line 38:		Line 38:
	}		}

	If you're struggling to import this using a crypto library, try to find a function that loads a DER encoded public key. If you can't find one, you can convert it to the more common PEM encoding by base64-encoding the raw bytes and wrapping the base64 text in '-----BEGIN PUBLIC KEY-----' and '-----END PUBLIC KEY-----'. See this example of a PEM encoded key: https://git.io/v7Ol9		如果你还在为如何使用加密库导入上述数据而苦恼的话，不妨尝试着去找个（或自己写个）函数来解码DER形式的公钥。如果你无法找到这样的函数，可以先通过base64将DER编码的公钥转化为PEM编码的公钥，然后再将转化好的公钥放在'-----BEGIN PUBLIC KEY-----'和'-----END PUBLIC KEY-----'之间。访问https://git.io/v7Ol9就能看到一个经PEM编码的公钥的例子。
			<font size=0.5>If you're struggling to import this using a crypto library, try to find a function that loads a DER encoded public key. If you can't find one, you can convert it to the more common PEM encoding by base64-encoding the raw bytes and wrapping the base64 text in '-----BEGIN PUBLIC KEY-----' and '-----END PUBLIC KEY-----'. See this example of a PEM encoded key: https://git.io/v7Ol9</font>

	== Symmetric Encryption ==		== Symmetric Encryption ==

imported>Kaniol at 02:56, 11 December 2019

2019-12-11T02:56:43Z

← Older revision		Revision as of 02:56, 11 December 2019
Line 1:		Line 1:
	~~自快照12w17a起，我的世界对开启正版验证的服务器使用加密的连接。~~		自快照12w17a起，Minecraft对开启正版验证的服务器使用加密的连接。

	== 概览 ==		== 概览 ==
Line 19:		Line 19:
	客户端似乎会生成错误的哈希值，如果传入的服务器ID字符串包含了一些无法被打印的字符。所以为了得到正常的哈希值,我们应该只发送 [U+0021，U+007E] 范围内的Unicode字符。这一范围对应于除了“空格”（U+0020）以及起控制作用的字符(U+0000-U+001F, U+007F)外其他所有的ASCII字符。		客户端似乎会生成错误的哈希值，如果传入的服务器ID字符串包含了一些无法被打印的字符。所以为了得到正常的哈希值,我们应该只发送 [U+0021，U+007E] 范围内的Unicode字符。这一范围对应于除了“空格”（U+0020）以及起控制作用的字符(U+0000-U+001F, U+007F)外其他所有的ASCII字符。

	客户端似乎也会生成错误的哈希值，如果传入的服务器ID字符串太短。经监视与Notchian Server（<font color=red>？</font>~~）发送不同长度服务器ID字符串的试验验证，在我的的世界1~~.5.2中[12，20]长度范围内的服务器ID字符串可以正常工作。		客户端似乎也会生成错误的哈希值，如果传入的服务器ID字符串太短。经监视与Notchian Server（<font color=red>？</font>）发送不同长度服务器ID字符串的试验验证，在Minecraft 1.5.2中[12，20]长度范围内的服务器ID字符串可以正常工作。

	== 密钥交换 ==		== 密钥交换 ==

imported>Lambol at 23:43, 10 December 2019

2019-12-10T23:43:18Z

← Older revision		Revision as of 23:43, 10 December 2019
Line 21:		Line 21:
	客户端似乎也会生成错误的哈希值，如果传入的服务器ID字符串太短。经监视与Notchian Server（<font color=red>？</font>）发送不同长度服务器ID字符串的试验验证，在我的的世界1.5.2中[12，20]长度范围内的服务器ID字符串可以正常工作。		客户端似乎也会生成错误的哈希值，如果传入的服务器ID字符串太短。经监视与Notchian Server（<font color=red>？</font>）发送不同长度服务器ID字符串的试验验证，在我的的世界1.5.2中[12，20]长度范围内的服务器ID字符串可以正常工作。

	== ~~Key Exchange~~ ==		== 密钥交换 ==

	The server generates a 1024-bit RSA keypair on startup. The public key is sent in the Encryption Request packet in DER encoding format. More technically, it is in ASN.1 format as defined by x.509 with the structure looking as follows.		The server generates a 1024-bit RSA keypair on startup. The public key is sent in the Encryption Request packet in DER encoding format. More technically, it is in ASN.1 format as defined by x.509 with the structure looking as follows.

imported>Kaniol: /* 概览 */

2019-12-10T11:50:02Z

概览

← Older revision		Revision as of 11:50, 10 December 2019
Line 9:		Line 9:
	(Server Auth, Both enable encryption)		(Server Auth, Both enable encryption)
	S->C : Login Success		S->C : Login Success
	#参见[[~~协议常见问题~~]]来获取更多关于下文内容的信息（<font color=red>'''about what happens next'''</font>）。		#参见[[ZH:Protocol FAQ\|协议FAQ]]来获取更多关于下文内容的信息（<font color=red>'''about what happens next'''</font>）。

	==服务器的ID字符串==		==服务器的ID字符串==