Significance of `src_addr` when opening "direct-tcpip" channel?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 9.9k
- Forks
- 2.1k
- PR merge metrics
- No merged PRs in 30d
Description
I'm sorry if this is a question with an obvious answer, but I can't wrap my head around this.
What is the functionality behind src_addr parameter in Transport.open_channel('direct-tcpip', ...)?
I.e. what difference does it make, apart from the server logging different originator address, whether I do this:
transport.open_channel('direct-tcpip', (host, port), ('127.0.0.1', 0))
or that:
transport.open_channel('direct-tcpip', (host, port), ("I really don't care", 123))
Both work well for me, so... where is the difference?
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 at the Transport.open_channel('direct-tcpip', ...) entry point mentioned in the issue and read its parameter documentation and the SSH direct-tcpip channel handling. Compare the protocol meaning of the destination and source address values, including whether the source is only reported to the server. Done means the behavior and practical significance of src_addr are clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- networking
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100