Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add support for incoming connections #116

Open
evilsocket opened this issue Apr 6, 2018 · 3 comments
Open

add support for incoming connections #116

evilsocket opened this issue Apr 6, 2018 · 3 comments
Assignees
Labels
feature a whole new feature

Comments

@evilsocket
Copy link
Owner

Right now the daemon will only intercept and manage outgoing connections, add support for incoming connections ( ip address x.x.x.x is connecting to port 80 of httpd )

@evilsocket evilsocket self-assigned this Apr 6, 2018
@evilsocket evilsocket added the feature a whole new feature label Apr 6, 2018
@Northern-Lights
Copy link
Contributor

Northern-Lights commented Aug 23, 2018

What exactly is the reason that incoming connections are not being queued? I can't find the info I'm looking for in any netfilter documentation.

Edit: after digging through the code more, it looks like the reason is simply because of the rule placement (all rules are -A in rules.go.) Would it be too much to stick our rules into the chains as number 1, for example:

		rule := []string{
			"-I",
			"INPUT",
			"1",
			"--protocol", "udp",
			"--sport", "53",
			"-j", "NFQUEUE",
			"--queue-num", fmt.Sprintf("%d", queueNum),
			"--queue-bypass",
		}

@GreenLunar
Copy link

This is important. I've made a connection using SSH and I was surprised that OpenSnitch didn't prevent me from connecting.

@robinmayol
Copy link

Hello! Any update on this please?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature a whole new feature
Projects
None yet
Development

No branches or pull requests

4 participants