Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
M
Minipots
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 16
    • Issues 16
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • Turris
  • Sentinel
  • Minipots
  • Issues
  • #46

Closed
Open
Opened Nov 15, 2020 by Vojtech Myslivec@vmyslivec🚀Owner

Limit announced versions in minipots

HTTP and FTP minipots introduce itself (in headers) as:

Server: Apache/2.4.38 (Debian)

and

220 (vsFTPd 3.0.3)

respectively.

Although it's not so crucial in a honeypot to "hide" simulated version, it is a good practice in real world to limit these information to strip literal version or the version at all.

e.g. in Apache, there is a common configuration option called ServerTokens which is recommended to set as ProductOnly, Major or Minor.

In our minipots, the announced version would obsolete a lot and attackers can also distinguish us based on it.

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: turris/sentinel/minipot#46