[atomic] psa-proftpd 1.3.3c

[BruceLee]

Thanks Scott.
What to do if I'm still with Plesk 9.5.2 and get this when running yum check-update?

Code: Select all

psa-proftpd.x86_64                  1.3.3c-2.el5.art                   asl-2.0
psa-proftpd-devel.x86_64            1.3.3c-2.el5.art                   asl-2.0
psa-proftpd-mysql.x86_64            1.3.3c-2.el5.art                   asl-2.0
Obsoleting Packages
psa-proftpd.x86_64                  1.3.3c-2.el5.art                   asl-2.0
psa-proftpd-xinetd.x86_64       1.3.2e-cos5.build95100504.10       installed

Code: Select all

#yum list *proftpd*:
Installed Packages
psa-proftpd.x86_64                  1.3.3c-1.el5.art                   installed
psa-proftpd-devel.x86_64            1.3.3c-1.el5.art                   installed
psa-proftpd-mysql.x86_64            1.3.3c-1.el5.art                   installed
psa-proftpd-xinetd.x86_64           1.3.2e-cos5.build95100504.10       installed
Available Packages
psa-proftpd.x86_64                  1.3.3c-2.el5.art                   asl-2.0
psa-proftpd-devel.x86_64            1.3.3c-2.el5.art                   asl-2.0
psa-proftpd-ldap.x86_64             1.3.3c-2.el5.art                   asl-2.0
psa-proftpd-mod_sftp.x86_64         1.3.3c-2.el5.art                   asl-2.0
psa-proftpd-mysql.x86_64            1.3.3c-2.el5.art                   asl-2.0
psa-proftpd-postgresql.x86_64       1.3.3c-2.el5.art                   asl-2.0

Thanks

[scott]

Right, it should be obsoleteing/providing on the old xinet package. This disappears in Plesk 10 anyway (merged in with the main package).

[BruceLee]

ok thanks.

[faris]

Wow - I just got an email notification from Parallels about the bug and release dates of when they will issue patches. Right at the bottom it mentions the Atomic update and includes install instructions. Website copy here:

http://www.parallels.com/products/plesk/ProFTPD

I've never had an email notification like this before.

Interestingly, by specifically mentioning 9.x and 10.x it seem to imply that Plesk 8.x and earlier do not have a vulnerable ProFTPd.

[biggles]

Wow - I just got an email notification from Parallels about the bug and release dates of when they will issue patches. Right at the bottom it mentions the Atomic update and includes install instructions. Website copy here:

http://www.parallels.com/products/plesk/ProFTPD

I've never had an email notification like this before.

Interestingly, by specifically mentioning 9.x and 10.x it seem to imply that Plesk 8.x and earlier do not have a vulnerable ProFTPd.

+1 for the Wow!

Re the 8.x issue it might also mean that they think 8.x more or less unsupported, but that might just be me showing my usual grumpy Thursday mode...

[Kalimari]

Upgraded psa-proftpd this morning:
Nov 11 09:28:59 Installed: psa-proftpd-1.3.3c-2.el5.art.x86_64
Nov 11 09:28:59 Erased: psa-proftpd-xinetd

Shortly after, noticed spamdyke entries no longer show in /usr/local/psa/var/log/maillog, checked /etc/xinetd.d/smtp_psa and "/usr/local/bin/spamdyke -f /etc/spamdyke.conf" was missing from the server_args. Added them, but no external mail is delivered locally, it stops with "/var/qmail/bin/relaylock". Removed the spamdyke entry and it all works again. Tried moving spamdyle conf BEFORE /var/qmail/bin/relaylock, external message delivery stops again.

Can anyone using spamdyke and the updated psa-proftpd package confirm if spamdyke is still working for them?

Thanks!

[BruceLee]

I have NOT updated to psa-proftpd-1.3.3c-2.el5.art.x86_64 until now but I use spamdyke.
I'm suprised that it should have something to do with this problem?
None of the proftpd packages touch the smtp_psa file. Of course both are run via xinetd.d but thats it.
Have you updated anything else? Or run a yum update that updated Plesk to 9.5.3?

[Kalimari]

Hi BruceLee, thanks for taking the time to respond. psa-proftpd-1.3.3c is the only update this week, spamdyke was working up till then and due to xinetd association, seemed a likely cause.

Have yum removed/installed spamdyke, reinstated same conf files/settings and it's working again...

Updated to Plesk 9.5.3 on 3 November and checked spamdyke settings, restarted xinetd (killall -HUP xinetd & /etc/init.d/xinetd restart) it's been running fine, guess the psa-proftpd update triggered something.

Glad to be up and running again (really noticed the increased server load with Spamassassin taking the brunt of the spam).

Hopefully a heads up for anyone else with same issue.

[scott]

Bizzare, I cant think of anything in the proftpd package that could touch spamdyke's config. Is that spamdyke package from the repo or a src.rpm install?

[mikeshinn]

Yeah nothing in the protftp rpms that would touch spamdyke.

[Kalimari]

Installed from the atomic repo. At least it is running again now.

[faris]

Hmmm.. Spamdyke still working as normal here after the update, but all our systems are on Plesk 8.6/Centos 4.

Faris.

[BruceLee]

spamdyke runs fine after this update (Plesk 9.5.2; Centos5.5-x86_64)

[breun]

Hm, there is an update loop here. With psa-proftpd-1.3.3c-2 from atomic installed the Plesk autoinstaller wants to install 1.3.2e with the micro update patch. This fails unless psa-proftpd-1.3.3c-2 is removed first. However, after installing the Plesk micro update, yum will update to psa-proftpd-1.3.3c-2 again, at which point we're back where we were, because now Plesk's autoinstaller will try to install the micro update again.

Sigh.

[BruceLee]

hmm, maybe excluding
psa-proftpd-1.3.2e-cos5.build95101022.10.x86_64.rpm
and
psa-proftpd-xinetd-1.3.2e-cos5.build95101022.10.x86_64.rpm
in plesk.repo would help?

I don't know how the autoinstaller handles that? Is there any reason to use it?
I always use yum.