• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Search results

  1. M

    Issue PCI Failure OpenSSH < 7.6

    Certainly Brujo. In sshd_config, I removed the line: Subsystem sftp /usr/libexec/openssh/sftp-server and replaced it with: Subsystem sftp internal-sftp Then I added the following rules to sshd_config, one for each user: Match User username ChrootDirectory /var/www/vhosts...
  2. M

    Issue PCI Failure OpenSSH < 7.6

    Thank you everyone. This issue with trustwave has finally been resolved.
  3. M

    Issue PCI Failure OpenSSH < 7.6

    Why on earth would I ever want to implement port knocking to simply to pass a PCI test designed for my protection when all I have to do is implement a security update which is unavailable to plesk because the maintainers only support an outdated library?
  4. M

    Issue PCI Failure OpenSSH < 7.6

    I might add that the failure is not a result of penetration testing. The failure is generated by a simple check of the OpenSSH version number. Otherwise, the server passes all other PCI checks.
  5. M

    Issue PCI Failure OpenSSH < 7.6

    Thanks, but no, that does not apply. My issues is described in CVE-2017-15906. IP blocking will not work for me because we have drivers on the road accessing over public networks.
  6. M

    Issue PCI Failure OpenSSH < 7.6

    Linux version 3.10.0-327.36.3.el7.x86_64 (builder@kbuilder.dev.centos.org) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-4) (GCC)
  7. M

    Issue PCI Failure OpenSSH < 7.6

    We are failing our PCI testing due to OpenSSH 7.4p1, which is the latest in yum. PCI compliance requires a minimum of 7.6. Please help.
Back
Top