Sean Whalen

Because I work for Cardinal Health :)

I ended up writing my own SPF validation code before I knew `pyspf` existed. I could make another PR that replaces `pyspf` with this code. Things to consider ## Pros...

@h-m-f-t It already does :) https://domainaware.github.io/checkdmarc/ It includes most of the same DMARC code we just merged too...it was just easier to copy/paste those checks than rewrite your stuff around...

@bknowles Until this gets fixed, try out my SPF and DMARC parser/validator, `checkdmarc` the only thing it does not do that `trustymail` does is check for `STARTTLS` on the SMTP...

Close. That line should `proxy_pass http://misp_web` not `proxy_pass http://misp-web`. Thanks I've actually run into so many problems with this Docker Compose project that I've started my own https://github.com/seanthegeek/misp-docker

@coolacid I just failed to import my secret PGP key. Any suggestions? ```bash root@0130065ac283:/var/www/MISP# sudo -u www-data gpg --homedir /var/www/MISP/app/Config/.gnupg --import /tmp/threatintel.asc gpg: key 81CB89AFEDECD842: "Threat Intel " not changed...

> `error reading '/tmp/threatintel.asc': Permission denied` > > Is the file there, is it readable by `www-data` user? Yep. That's the weird part. ```bash root@0130065ac283:/var/www/MISP# ls -al /tmp/threatintel.asc -rw-------. 1...

And, it imported the public key just fine ```bash root@0130065ac283:/var/www/MISP# gpg --homedir /var/www/MISP/app/Config/.gnupg -k /var/www/MISP/app/Config/.gnupg/pubring.kbx ------------------------------------------- pub ed25519 2020-02-25 [SC] C59A7A8C07AD3CFB5521BDCF81CB89AFEDECD842 uid [ultimate] Threat Intel sub cv25519 2020-02-25 [E] ```...

I just tried as root for the hell of it and it still failed ```bash root@0130065ac283:/var/www/MISP# gpg --homedir /var/www/MISP/app/Config/.gnupg --import /tmp/threatintel.asc gpg: WARNING: unsafe ownership on homedir '/var/www/MISP/app/Config/.gnupg' gpg: key...

I figured it out https://github.com/MISP/MISP/issues/2372 tipped me off. So `sudo` breaks the special terminal input that `gpg` uses for the passphrase input prompt. Running `gpg` inside a `screen` session works...