HTTPS Honeypot Enterprise Community

HTTPS is identical to HTTP with the addition of TLS encryption. Trapster generates a self-signed certificate on startup if the key or certificate file is missing.

Configuration

"https": [
  {
    "port": 443,
    "skin": "default_apache",
    "basic_auth": false,
    "username": null,
    "password": null,
    "country_name": null,
    "state_or_province_name": null,
    "locality_name": null,
    "organization_name": null,
    "common_name": "server.internal",
    "key": "trapster/data/ssl/https/key.pem",
    "certificate": "trapster/data/ssl/https/certificate.pem"
  }
]

Parameters

All HTTP parameters apply, plus:

Parameter	Type	Default	Description
country_name	string	omitted	X.509 subject country
state_or_province_name	string	omitted	X.509 subject state or province
locality_name	string	omitted	X.509 subject locality
organization_name	string	omitted	X.509 subject organization
common_name	string	server.internal	Certificate CN
key	string	trapster/data/ssl/https/key.pem	PEM private key path
certificate	string	trapster/data/ssl/https/certificate.pem	PEM certificate path

Certificate behavior

If key or certificate is missing, Trapster creates the parent directory and writes a new 2048-bit RSA self-signed certificate.

To use a CA-issued certificate instead, provide your own PEM files at key and certificate and adjust the module if you need to skip regeneration.

Skins and credential capture

Same skins and logging behavior as HTTP. Credentials are captured from the decrypted HTTP layer before TLS terminates at Trapster.