TheBigK
Well-known member
Could you please explain in brief what exactly was the issue?Remove all callbacks from your addons
Could you please explain in brief what exactly was the issue?Remove all callbacks from your addons
1. He had a callback in all his addons whereby on install and uninstall, it would callback to his own servers.Could you please explain in brief what exactly was the issue?
He had a callback in all his addons whereby on install and uninstall, it would callback to his own servers.
A simple callback was never a problem and is still included in his add-ons. He checks the installation domain with his database and denies install if not licensed. This is what several developers do.
The FORMER problem with him was that he backloaded additional MySQL and/or PHP code from his server during the installation.
But he changed his installation routine after the guide lines were published and currently does not backload any code and also does not use a callback at uninstall. Hopefully it will stay this way.
That is a decision you need to make. We have no access to most of the add-ons so can't comment on the code.Should we uninstall everything by *******? Is this what XF recommends for security reasons?
Post on the specific add-on thread for support with it.How can we be sure that everything is removed, since they did some strange things from what I understood?
Commission a developer to make any you require, wait for them to be developed independently, continue using ******* add-ons, or do without.What happens now, when some essential plugins we used are gone?
so no definitive answer? I can't read code so the proof isn't in the pudding. All I can make out of that thread is nine pages of back-and-forth. I suppose I'll have another go at rereading it again when I have more time later.That has already been discussed here: https://xenforo.com/community/threa...nship-with-vxf-vn-and-copyright-issues.91524/
so no definitive answer? I can't read code so the proof isn't in the pudding. All I can make out of that thread is nine pages of back-and-forth. I suppose I'll have another go at rereading it again when I have more time later.
It relates to a combination of factors, as mentioned in the first post and reiterated by Mike above.
As stated, we are unable to say whether there are or are not security related issues with the code, for the simple reason that we do not have access to it and have not audited it.
We use essential cookies to make this site work, and optional cookies to enhance your experience.