When tunneling sshd service, we have double encapsulation of SSH.
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 16.6k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
Please refer to https://github.com/jpillora/chisel/pull/187 for more details.
Note that, if we implemented the feature to avoid double encapsulation we still need to keep the built-in sshd service for encryption to avoid leaking unencrypted data. That is we need to explicitly enable the feature instead of making it the default.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading pull request #187, which contains the detailed context for the double-encapsulation behavior. Done means providing an explicitly enabled way to avoid double SSH encapsulation while retaining the built-in sshd service for encryption by default.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100