You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My idea originally was about a kernel module mode specifically nftables' module.
Your ideas about multi-node port knocking was really good; I never thought about them.
My idea is that we would write a firewall rule, and because it's a firewall rule, we could enable more features and not just ports.
The port numbers sequence would be a hash combination of:
username (optional)
password
maybe a domain name? (optional)
timestamp (to make sure Man In The Middle Attack is not possible and no one can get the port sequence)
MAC Address (optional)
Or maybe even custom fields of values
With firewall, we can have many more features for free, for example we can deny access for specific days of the week.
I never thought about using pcap for this, but when I saw your project that gave me some ideas too. Now I'm thinking maybe using pcap for this can have some benefits, but we have to write a lot more codes to be able to match all the features of a firewall-based solution.
The text was updated successfully, but these errors were encountered:
Hi;
I thought we'd continue our talks here.
My idea originally was about a kernel module mode specifically nftables' module.
Your ideas about multi-node port knocking was really good; I never thought about them.
My idea is that we would write a firewall rule, and because it's a firewall rule, we could enable more features and not just ports.
The port numbers sequence would be a hash combination of:
With firewall, we can have many more features for free, for example we can deny access for specific days of the week.
I never thought about using pcap for this, but when I saw your project that gave me some ideas too. Now I'm thinking maybe using pcap for this can have some benefits, but we have to write a lot more codes to be able to match all the features of a firewall-based solution.
The text was updated successfully, but these errors were encountered: