shadowsocks/shadowsocks-windows

支持不经过密钥派生，直接设定加密密钥

Open

#2,927 opened on Aug 2, 2020

View on GitHub
 (2 comments) (1 reaction) (0 assignees)C# (59,558 stars) (16,275 forks)batch import
good first issuenew feature

Description

简要描述问题

windows10，.net组件正常，能够正常运行冰使用Shadowsocks 4.1.10， 只是最近朋友给我的ss节点，其密码都是64位的字符串，填入Shadowsocks 4.1.10，客户端中，结果连接不上，节点的加密方式为chacha20-ietf-poly1305。朋友说是这个认证方式是 shadowsocks-libev 引入的。

用朋友给我的一个命令行程序（[demon.zip]https://github.com/shadowsocks/shadowsocks-windows/files/5012306/demon.zip) ）能够连上。

shadowsocks-windows将来能支持这种类型的节点嘛？

Contributor guide

Tech stack
csharp
Domain
securityauthentication
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Understanding of Shadowsocks protocolFamiliarity with C#Knowledge of cryptographic key derivation
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
Start by examining the encryption handling code in the shadowsocks windows repository, likely in the `Shadowsocks.Net` or `Cryptor` classes. Review how AEAD encryption (chacha20 ietf poly1305) is currently implemented and how the key is derived from the password using HKDF. Check the issue comments for any maintainer discussion (e.g., #2927). Look at the referenced `demon.zip` tool to understand how it bypasses key derivation. The goal is to add an option to accept a pre derived key directly, which may require changes to the configuration parsing and encryption initialization.