feat: expand and randomize Telnet IAC negotiation sequences#17
Open
vinayaktyagi10 wants to merge 1 commit intohoneynet:mainfrom
Open
feat: expand and randomize Telnet IAC negotiation sequences#17vinayaktyagi10 wants to merge 1 commit intohoneynet:mainfrom
vinayaktyagi10 wants to merge 1 commit intohoneynet:mainfrom
Conversation
- Replace fixed 3-byte negotiations array with iacOption struct supporting variable length sequences (2 or 3 bytes) - Expand option pool from 6 to 11 entries - Add NOP and GA as 2-byte sequences to vary traffic fingerprint - Makes tarpit harder to fingerprint by automated scanners
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.
Summary
Replaces the fixed, fingerprintable Telnet IAC negotiation sequences
with a larger, variable-length pool to reduce scanner detectability.
Changes
negotiations[][3]array withiacOptionstructsupporting variable-length sequences (2 or 3 bytes)
options[optionIndex].lengthinstead ofhardcoded length
Why
The original implementation sent the same 6 IAC sequences, always
exactly 3 bytes each. This creates a consistent traffic fingerprint
that automated scanners can detect and use to immediately disconnect
from the tarpit. A more varied negotiation pool makes the tarpit
harder to distinguish from a real Telnet server.
Testing
Tested locally with
nc localhost 2323. Confirmed varied bytesequences being sent and clean connect/disconnect behavior.