Phishing Script and Server Update & Future Plans

[Jerry Benton]

It was not in gzip format because the update server was handing you a 301 that was not being handled correctly. This will no longer happen.


--
Jerry Benton
www.mailborder.com<http://www.mailborder.com>
+1 843-800-8605


From: MailScanner <mailscanner-bounces+jerry.benton=mailborder.com at lists.mailscanner.info> on behalf of Bogdan-Stefan Rotariu <bogdan at rotariu.ro>
Date: Wednesday, November 6, 2024 at 09:36
To: MailScanner Discussion <mailscanner at lists.mailscanner.info>
Subject: Re: Phishing Script and Server Update & Future Plans
Thank you for the recent update. I would like to suggest two changes:

1. Since we have already set the PATH, we can simply use ms-peek without specifying the full path (/usr/sbin/ms-peek).
2. Regarding the enforcement of HTTPS, we have encountered issues with bad .gz files. Currently, the only fix is to remove them manually. I propose that the script either overwrites these .gz files or removes them before downloading new ones to prevent this issue.

gzip: /usr/mailscanner/etc/phishing.safe.sites.conf.master.gz: not in gzip format

I have added a workaround to our script:

if [ -d $CONFIGDIR ]; then
    cd $CONFIGDIR
#delete .gz old gz files if left behind
find "$CONFIGDIR" -name "*.gz" -type f -exec rm -f {} +

Thanks,

--
Bogdan-Stefan Rotariu




On 6 Nov 2024, at 14:20, Jerry Benton <jerry.benton at mailborder.com> wrote:

I have updated the cron script for phishing bad/safe sites to v0.3.1. It is available here:https://phishing.mailscanner.info<https://phishing.mailscanner.info/>

The phishing update server has been updated to use https, but will not force that connection and will now accept http.

Several previous automatic bad site scrubs were removed for the google domain and several subdomains. This means you will need to add them to the phishing safe sites custom file to retain links to google domains.

Uncompressed versions of the bad/safe sites files are no longer available. If you have an old script trying to download those files, it will fail. You will need to use the newer update script or modify any custom scripts to download the compressed versions and then extract them for use.

The phishing bad sites is compiled from Phishtank data. It essentially pulls the domains from the phishing links and puts them into a flat file for use in MailScanner.


Future plan:

I am looking into creating a mechanism to populate a SQLite database with phishing links instead of just domains. I am creating this for use in Mailborder, but will make the database available for MailScanner. In order to be used in MailScanner someone would have to write the code to use it. (I have enough to do.) Once I create a base structure of what the database would look like, I will send out an update here with a link to the SQLite database. Not sure how this would impact scanning speed at this time. It would of course depend on how big that database gets.

The reason why I am looking into this …

I contacted Openphish about licensing cost to get their database. They want $10k per server per year for the “light” version. That is just nuts.

How you can help …

I need source data to compile this database. I can get some from Phishtank and a very small amount from Openphish free sources. I haven’t put a whole lot of cycles into this, but if you have any suggestions, please email me.


--
Jerry Benton
www.mailborder.com<http://www.mailborder.com/>
+1 843-800-8605



--
MailScanner mailing list
mailscanner at lists.mailscanner.info<mailto:mailscanner at lists.mailscanner.info>
http://lists.mailscanner.info/mailman/listinfo/mailscanner

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mailscanner.info/pipermail/mailscanner/attachments/20241106/d500bbf8/attachment.html>