-
Notifications
You must be signed in to change notification settings - Fork 293
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add *.pif to default list of blocked extensions #17
Comments
I expect you do know that you can modify the list of blocked attachment types in hmailadmin but just in case... |
Of course I know - that's why I wrote "default list". ;) The extension isn't really used anymore, but for infecting users with maleware, so IMHO it should be filtered by default (or better: when the extension filter is activated). |
Thre have been some reports of attachment blocking not always working. I think Martin should look into it. In the mean time I wrote ascript to deal with it. https://www.hmailserver.com/forum/viewtopic.php?f=20&t=26175&sid=43bec6a53eb42821dc4cae834cd020f1 Reports of attachment blocking not working as expected: |
Added *.pif to the default list. Note that this will only affect new installations though. I've also created a new issue to cover what visuaperception describes. *.pif will be included in the next build. |
I got several mails with malicious files, using the ".pif" extension ("Windows Information File").
Notes from Wikipedia:
"Although a file in PIF format does not contain any executable code (it lacks executable files' magic number "MZ"), Microsoft Windows handles all files with (pseudo-)executables' extensions in the same manner: all .COMs, .EXEs, and .PIFs are analyzed by the ShellExecute function and will run accordingly to their content and not extension, meaning a file with the PIF extension can be used to transmit computer viruses."
I think this extension should be added to the default list of blocked extensions.
The text was updated successfully, but these errors were encountered: