Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I was thinking - if poseidon is written in Go, why it is not suitable for windows? So I decided to fix that.
Of course it doesnt have as much amount of features for Windows as apollo, but in some cases you just need to do a basic recon/build tunnels. Poseidon should perfectly fit in that cases (especially as long as apollo and poseidon cannot talk to each other).
It is kind of tested on Windows 10, and should not break anything on Linux/macOS.
Known limitations:
shellfunction is kind of buggy. It works with powershell.exe (however I didnt manage to make it work with cmd.exe), but the output is a bit messypty- i am not sure if it can be natively implemented for windows, so it is an area to research for me