Setup

Requirements

Muraena relies on Redis for data persistence. Redis is expected at tcp://127.0.0.1:6379 (no SSL, no auth).

Once the installation is done, you can start the redis server and Muraena will take care of the rest.

Testing

With dnsmasq handling a new TLD that we use just for testing, for example .muraena, you have the following in /usr/local/etc/dnsmasq.conf:

address=/.muraena/127.0.0.1

Once verified that you can resolve anything.goes.to.muraena, you need a wildcard certificate for your phishing domain.

For testing purposes it's more than enough this awesome tool: mkcert. "A simple zero-config tool to make locally trusted development certificates with any names you'd like"

Once certificates are sorted, just include them within the configuration file:

[tls]
    enabled = true
    expand = false
    certificate = "./config/cert.pem"
    key = "./config/privkey.pem"
    root = "./config/fullchain.pem"

or Base64 encode the certificates:

alias cert2base64='awk '\''{printf "%s\\n", $0}'\'' '
cert2base64 <certificate.pem> | pbcopy

and paste in their configuration fields:

[tls]
    enabled = true
    expand = false
    certificate = "-----BEGIN CERTIFICATE-----[...]]"
    key = "-----BEGIN RSA PRIVATE KEY-----[...]"
    root = "-----BEGIN CERTIFICATE-----[...]"

Public

In real life you will need a certificate from a public CA, unless your target already has your custom CA as trusted.

A free option is to use LetsEncrypt. Once you obtained your wildcard certificate, just point the key and certificate material to the config file in the same way as described above.

Similarly, dnsmasq is not an option, so you will need to tune the DNS Zone file of your phishing domain (which you partially already did to get the LetsEncrypt, see A record) in order to have a wildcard CNAME like the following:

* 10800 IN CNAME phishing.muraena.