EhudZ
My feedback
47 results found
-
112 votes
An error occurred while saving the comment An error occurred while saving the comment EhudZ
commented
You may have port 8443 opened only to certain fixed IPs, done on the AWS hosting level which is not accessible via Plesk or server SSH access.
EhudZ
supported this idea
·
-
2 votes
Thank you for your idea! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
-- PD
An error occurred while saving the comment EhudZ
commented
This is what OpenAI has to say about this issue:
To oversign the From, To, and CC headers in DKIM for outgoing emails in Postfix, you can make use of the OpenDKIM milter integration. Here's a general outline of the steps involved:
Install OpenDKIM: Begin by installing the OpenDKIM package on your Postfix server. The installation steps can vary depending on your operating system. For example, on Ubuntu, you can use the following command:
shell
Copy code
sudo apt-get install opendkim opendkim-tools
Generate DKIM Key: Generate a DKIM key pair using the opendkim-genkey tool. Replace example.com with your domain name:shell
Copy code
opendkim-genkey -b 2048 -d example.com -s selector1
This will create two files: selector1.private (private key) and selector1.txt (DNS record).Configure OpenDKIM: Open the OpenDKIM configuration file (/etc/opendkim.conf) and make the following changes:
vbnet
Copy code
Domain example.com
KeyFile /etc/opendkim/selector1.private
Selector selector1
OversignHeaders From,To,Cc
Adjust the paths and selectors as per your key and configuration.Configure Postfix: Edit the Postfix configuration file (/etc/postfix/main.cf) and add or modify the following lines:
makefile
Copy code
milter_default_action = accept
milter_protocol = 2
smtpd_milters = inet:localhost:8891
non_smtpd_milters = inet:localhost:8891
These lines instruct Postfix to use the OpenDKIM milter on localhost port 8891.Restart Services: Restart both Postfix and OpenDKIM to apply the changes:
shell
Copy code
sudo systemctl restart postfix
sudo systemctl restart opendkim
With these steps completed, Postfix will send outgoing emails to the OpenDKIM milter for DKIM signing. The OversignHeaders directive in the OpenDKIM configuration will ensure that the From, To, and CC headers are included in the DKIM signature, even if they are not present in the original message.Make sure to test your setup and monitor the mail logs for any errors or issues. Adjust the configuration as needed for your specific environment and requirements.
EhudZ
shared this idea
·
-
2 votes
Thank you for your idea! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
-- PD
EhudZ
shared this idea
·
-
25 votes
Thank you for your input! We will consider this functionality in upcoming releases, if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
—
IGEhudZ
supported this idea
·
-
28 votes
Thank you for your input! We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
--
IG
An error occurred while saving the comment EhudZ
commented
I consider this as a PLESK BUG, as the absence of DKIM, causes a strict DMARC policy to fail.
EhudZ
supported this idea
·
-
41 votes
Thank you for your input! We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
--
IG
An error occurred while saving the comment EhudZ
commented
Plesk server notifications are sent without a DKIM signature, even if the Plesk domain is configured to be a mail server, and even if DKIM is configured for it.
This is done, at the same time Fail2Ban or server PHPMailers emails sent via Amazon webmail /SMTP get signed.
The absence of DKIM signature, is considered by me as a Plesk BUG, as it not being on some emails, harms the user, preventing implementation of a strict DMARC policy, due to the absence of DKIM on some emails sent to outside servers.
An error occurred while saving the comment EhudZ
commented
I find the as a Plesk BUG.
EhudZ
supported this idea
·
-
4 votes
Thank you for your input! We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
--
IG
An error occurred while saving the comment EhudZ
commented
This should have been done automatically...
As the mail is configured for it, and its only mail server that fails.EhudZ
supported this idea
·
-
75 votes
Thank you for your input! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
— AY
EhudZ
supported this idea
·
-
2 votes
-
36 votes
We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
However, please be aware that rate-limiting web traffic can and should normally be done using iptables as it is much more effective and resource savvy doing it on the operating system/kernel level. If there are issues with web traffic, it is best to not to let it get to the web server in the first place.
-- PD
EhudZ
supported this idea
·
-
3 votes
Thank you for your input! We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
--
IG
EhudZ
supported this idea
·
-
17 votes
An error occurred while saving the comment EhudZ
commented
Very important.
EhudZ
supported this idea
·
-
7 votes
Thank you for your input. We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
—
IGAn error occurred while saving the comment EhudZ
commented
Any news?
EhudZ
supported this idea
·
-
1,305 votes
An error occurred while saving the comment EhudZ
commented
Hi,
I'm a user and not of Plesk support.
CalmAV is to the best of my understanding enabled on Plesk for Plesk hosted mail protection:
https://www.plesk.com/blog/guides/how-to-protect-email-servers-against-spam-viruses/I have implemented CalmAV manually to scan uploaded files, using ModSecurity as base technology.
inspectFile
Description: Executes an external program for every variable in the target list. The contents of the variable is provided to the script as the first parameter on the command line. The program must be specified as the first parameter to the operator. As of version 2.5.0, if the supplied program filename is not absolute, it is treated as relative to the directory in which the configuration file resides. Also as of version 2.5.0, if the filename is determined to be a Lua script (based on its .lua extension), the script will be processed by the internal Lua engine. Internally processed scripts will often run faster (there is no process creation overhead) and have full access to the transaction context of ModSecurity.The @inspectFile operator was initially designed for file inspection (hence the name), but it can also be used in any situation that requires decision making using external logic.
The OWASP ModSecurity Core Rule Set (CRS) includes a utility script in the /util directory called runav.pl ModSecurity that allows the file approval mechanism to integrate with the ClamAV virus scanner. This is especially handy to prevent viruses and exploits from entering the web server through file upload.
#!/usr/bin/perl
#
# runav.pl
# Copyright (c) 2004-2011 Trustwave
#
# This script is an interface between ModSecurity and its
# ability to intercept files being uploaded through the
# web server, and ClamAV$CLAMSCAN = "clamscan";
if ($#ARGV != 0) {
print "Usage: runav.pl <filename>\n";
exit;
}my ($FILE) = shift @ARGV;
$cmd = "$CLAMSCAN --stdout --no-summary $FILE";
$input = `$cmd`;
$input =~ m/^(.+)/;
$error_message = $1;$output = "0 Unable to parse clamscan output [$1]";
if ($error_message =~ m/: Empty file\.?$/) {
$output = "1 empty file";
}
elsif ($error_message =~ m/: (.+) ERROR$/) {
$output = "0 clamscan: $1";
}
elsif ($error_message =~ m/: (.+) FOUND$/) {
$output = "0 clamscan: $1";
}
elsif ($error_message =~ m/: OK$/) {
$output = "1 clamscan: OK";
}print "$output\n";
Example: Using the runav.pl script:
# Execute external program to validate uploaded files
SecRule FILES_TMPNAMES "@inspectFile /path/to/util/runav.pl" "id:159"
Example of using Lua script (placed in the same directory as the configuration file):SecRule FILES_TMPNAMES "@inspectFile inspect.lua" "id:160"
The contents of inspect.lua:function main(filename)
-- Do something to the file to verify it. In this example, we
-- read up to 10 characters from the beginning of the file.
local f = io.open(filename, "rb");
local d = f:read(10);
f:close();-- Return null if there is no reason to believe there is ansything
-- wrong with the file (no match). Returning any text will be taken
-- to mean a match should be trigerred.
return null;
end
Note : Starting in version 2.9 ModSecurity will not fill the FILES_TMPNAMES variable unless SecTmpSaveUploadedFiles directive is On, or the SecUploadKeepFiles directive is set to RelevantOnly.
Note: Use @inspectFile with caution. It may not be safe to use @inspectFile with variables other than FILES_TMPNAMES. Other variables such as "FULL_REQUEST" may contains content that force your platform to fork process out of your control, making possible to an attacker to execute code using the same permissions of your web server. For other variables you may want to look at the Lua script engine. This observation was brought to our attention by "Gryzli", on our users mailing list.
Version: 2.xSupported on libModSecurity: TBI
file upload modsecurity protection
I have installed ClamAV according to instruction
I have set the script in place.
The script is called by a new rule added via Plesk manual rules:
SecRule FILES_TMPNAMES "@inspectFile /etc/apache2/modsecurity.d/modsec_clamav.pl" \
"id:'99999932471', \
phase:2, \
t:none, \
deny, \
log, \
msg:'Infected File upload detected', \
tag:'MALICIOUS_SOFTWARE/VIRUS'"
tested syntax and restarted Apache servercould not test file upload as those were not IMAGE or PDF
Script has to get execution permissions
An error occurred while saving the comment EhudZ
commented
It's very important.
EhudZ
supported this idea
·
-
1 vote
Thank you for your input! We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
--
IG
-
47 votes
Thank you for your input. We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
—
IGEhudZ
supported this idea
·
-
35 votes
We will consider this functionality in upcoming releases if it will be popular. However, in part of integration with 3rd party, probably it will be faster if you create Plesk extension. Please refer to https://docs.plesk.com/en-US/17.0/extensions-guide/what-are-plesk-extensions%3F.76331/ to know how.
Everyone, please continue voting for this feature if you consider it important.
—
ETAn error occurred while saving the comment EhudZ
commented
This is possible.
Have a look at:
https://talk.plesk.com/threads/abuseipdb-with-fail2ban.348869/ -
1 vote
Thank you for your input! We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
--
IG
-
8 votes
Thank you for your input! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
—
IGAn error occurred while saving the comment EhudZ
commented
Hi,
If you would like to get an email notification for ModSecurity, you can do so, by setting a Fail2Ban jail for ModSecurity, and then get the email notifications.
So in Fail2Ban, what worked for me was adding second line under action =....
to be:
```
sendmail[mailcmd='/usr/sbin/sendmail -f "<sender>" "<dest>"', dest="email@recipient.com", sender="fail2ban", sendername="Fail2Ban", name="jail_name"]
```Note: You may do so for various jails.
EhudZ
supported this idea
·
-
1 vote
Thank you for your input! We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
--
IG
A bigger threat could possibly be, if Plesk update is hacked, and Plesk firewall is changed. I recommend using also the AWS firewall to block access to certain ports as 22, 8443,8447, to all IPs but certain fixed ones.