Anonymous
My feedback
4 results found
-
180 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.
—
IGAnonymous supported this idea · -
115 votes
Hello,
Thanks for your input, we understand the importance. This Feature request is registered in our tracking system as PPM-344 and it will be included into future Plesk versions. There is no ETA at the moment, but we would really appreciate you voting for this request so that we can accurately assess its popularity relative to other features. Thanks in advance!An error occurred while saving the comment Anonymous supported this idea ·An error occurred while saving the comment Anonymous commentedThis is no feature whose popularity needs to be assessed. I know, the GDPR is not very popular... but we have to abide by it. Using the current "password protection" will render the user liable to prosecution since there is no protection at all. In my opinion calling it "password protection" even is a fraudulent representation.
An error occurred while saving the comment Anonymous commentedIt's soon 2020 and still everything would get uploaded in clear text to Google Drive and others. That is insane!!
This is no feature whose popularity needs to be assessed. I know, the GDPR is not very popular... but we have to abide by it. Using the current "password protection" will render the user liable to prosecution since there is no protection at all. In my opinion calling it "password protection" even is a fraudulent representation.Also it could be as simple as that (using gpg):
Encrypt:
tar -czf - [FOLDERS] | gpg -c --batch --passphrase [PASSWORD] -o backup.tgz.gpgDecrypt:
gpg -d --batch --passphrase [PASSWORD] backup.tgz.gpg | tar -xzf -I'd change it myself if I had access to the source...
An error occurred while saving the comment Anonymous commentedThere is no option to encrypt backups. I do not trust Google or any other cloud service. Yet I could use the (otherwise completely useless) storage to put my backups there.
So please include a proper and secure encryption. Thanks!
Edit:
It could be as easy as running gpg as a last step before uploading:Encrypting (simple tar example):
tar -czf - [FOLDERS] | gpg -c --batch --passphrase [PASSWORD] -o backup.tgz.gpgDecrypting:
gpg -d --batch --passphrase [PASSWORD] backup.tgz.gpg | tar -xzf - -
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.
—
IGAn error occurred while saving the comment Anonymous commentedOn the mail import page there should be a "remove" link next to the "synchronize" link to remove the stored credentials of the source mail account.
Anonymous shared 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.
—
IGAn error occurred while saving the comment Anonymous commentedCurrently when an alias domain is created, the webmail subdomain of this alias domain is not included in the Let's Encrypt certificate. That results in:
http://webmail.example.com being accessible but not safe (http)
https://webmail.example.com not being accessible (certificate error)This should be fixed, since it is a security risk. Also there should be a 301 redirection.
Anonymous shared this idea ·
Most of us do not have access to /var/*, gpg, curl or ftp-pasv...
This is a problem Plesk needs to fix ASAP.