[GH-ISSUE #3910] [Nodejs实现frpc visitor协议]报文长度解密请教 #3101

Closed
opened 2026-05-05 14:00:33 -06:00 by gitea-mirror · 2 comments
Owner

Originally created by @ldjking on GitHub (Jan 5, 2024).
Original GitHub issue: https://github.com/fatedier/frp/issues/3910

Describe the feature request

在login成功后,得到明文的loginMsg,然后是16位的iv
然后是一段长度11的报文,第一位的typeByte 解密成功,后面8位的length解密失败,请教下如何正确解密length
encIv=[254,227,8,89,13,152,208,92,96,1,1,246,23,212,226,165]
encKey=[149,153,7,126,193,218,153,19,241,238,169,213,110,245,169,6]
enc typeDec=[r] typeByte=[114]
lengthBufferEnc=[8] data=[75,18,190,54,122,219,197,234]
lengthBufferDec=[8] data=[77,89,172,136,76,161,30,47]
declength=[5573675715248856623]

Describe alternatives you've considered

No response

Affected area

  • Docs
  • Installation
  • Performance and Scalability
  • Security
  • User Experience
  • Test and Release
  • Developer Infrastructure
  • Client Plugin
  • Server Plugin
  • Extensions
  • Others
Originally created by @ldjking on GitHub (Jan 5, 2024). Original GitHub issue: https://github.com/fatedier/frp/issues/3910 ### Describe the feature request 在login成功后,得到明文的loginMsg,然后是16位的iv 然后是一段长度11的报文,第一位的typeByte 解密成功,后面8位的length解密失败,请教下如何正确解密length encIv=[254,227,8,89,13,152,208,92,96,1,1,246,23,212,226,165] encKey=[149,153,7,126,193,218,153,19,241,238,169,213,110,245,169,6] enc typeDec=[r] typeByte=[114] lengthBufferEnc=[8] data=[75,18,190,54,122,219,197,234] lengthBufferDec=[8] data=[77,89,172,136,76,161,30,47] declength=[5573675715248856623] ### Describe alternatives you've considered _No response_ ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [x] Others
gitea-mirror 2026-05-05 14:00:33 -06:00
Author
Owner

@ldjking commented on GitHub (Jan 5, 2024):

整个报文长度11 一起解密可以成功。
单独解密1个字节,8个字节,2个字节,这样子不行。

<!-- gh-comment-id:1878096918 --> @ldjking commented on GitHub (Jan 5, 2024): 整个报文长度11 一起解密可以成功。 单独解密1个字节,8个字节,2个字节,这样子不行。
Author
Owner

@github-actions[bot] commented on GitHub (Jan 27, 2024):

Issues go stale after 21d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

<!-- gh-comment-id:1912870108 --> @github-actions[bot] commented on GitHub (Jan 27, 2024): Issues go stale after 21d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/frp#3101
No description provided.