PowerShell / PowerShell/Win32-OpenSSH
Feature request: Add logging to log ssh tunneling
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 8.3k
- Forks
- 819
- PR merge metrics
- No merged PRs in 30d
Description
Today sshd will not properly log a tunnel command.
By running ssh -J user@jumphost user@target you can jump through the jumphost, it will however not produce a good log of it. You can see that the user connected but you can't see the outbound connection command for the jump to the next system.
In my eyes this makes auditing of jumphosts harder and could be a sec. issue due to inability to detect improper attempts.
I have found a patch for older ssh versions at http://blog.rootshell.be/2009/03/01/keep-an-eye-on-ssh-forwarding/ that seems to be about the same issue (I'm not C developer)
Contributor guide
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 with sshd handling for the ssh -J user@jumphost user@target entry point and compare it with the older SSH forwarding patch linked in the issue. Determine how to record the outbound jump connection and add coverage for the tunnel command; done means the jump host log identifies that outbound connection clearly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- networking, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100