Closed LucasParsy closed 2 months ago
adding additional info as I am interested in developing this feature and would request your feedback before coding:
On developing the feature, there would be 2 philosophies:
In my opinion, using exec may seem too simple and bad practice, but in the end it is just a matter of trusting a project and using it correctly, and I'm more confident doing so with ip
than with the 2 libraries.
I know how to create interfaces/tunnels on Linux, as you documented it, but not in Windows. Is it possible to create from the command line/ libraries in Windows, or would you accept this feature as Linux only, at least initially?
Good idea. For Windows, the tun interface is automatically created, but not for Linux.
I will implement this functionality soon.
Thanks a lot! (Great talk also 👍) Note that in the example I gave initially, the new tunnel name I gave is apparently not a valid name.
This would be great to fully automate the proxying instead of having to type in manually 3 commands each time :)
Implemented in Ligolo-ng v0.6!
Hi! Just discovered Ligolo, it's an excellent tool! the tool is so useful I only have one feature i'd like:
automatically create tunnels and routing from the tool.
feature description:
let's imagine I have an agent with this interface:
if i'd run the new command
it would do under the hood:
caveats
I don't know how complex it would be to create this feature and integrate it to the tool. It would require Sudo elevation of privilege from with ligolo to set interfaces (run elevated sub-process?)
I don't have knowledge in Go (yet!) and I'm pretty busy these next months, otherwise I would have tried for a pull request. And I think it's more polite to ask feedback for a new feature to the app's creator ;)
By the way, I'm curious, where does the name "ligolo" comes from?