3 ms·
The example shows you opening port 80 (HTTP standard port), the comment next to it mentions SSH (default port 22). That's confusing. Also your headline claims
by Tepix 2y ago
The example shows you opening port 80 (HTTP standard port), the comment next to it mentions SSH (default port 22). That's confusing.
Also your headline claims that your system is "better", but it fails to explain why. Modern port knocking also incorporates secure cryptographic hashes.
- rmholt 2y agoI believe the author is comparing their method against just the naive port knocking approach
- mschempp 2y agoyes thats correct. Should have stated that in the headline
- mschempp 2y ago"The example shows you opening port 80 (HTTP standard port)" that's because I run my ssh on port 80, but that's not standard, so I agree that it's confusing. Thanks for pointing it out. I will fix it :)
- mschempp 2y ago"Modern port knocking also incorporates secure cryptographic hashes." Are you referring to fwknop? Thats not "port knocking" but Single Packet Authorization. That is very different from port knocking. How can one incorporate secure cryptographic hashes with simple port knocking?