Interestingly, I thought the comment could just as easily be read as a dig at the team.
One of those inkblot problems, I guess.
One of those inkblot problems, I guess.
When I first saw it. It made me wonder about SMF upper managements inability to retain those skillful enough to be core devs.
Basically, I think what SMF should be going, if it HOPES to have a chance at surviving, is moving its SVN to git, and allowing anyone to commit patches for the lead devs to check and push into the core.
Since the SMF devs are obviously unable to do the amount of work they're expected to do, I'm sure the SMF team will eventually rely on this.[nb]
Hi Mark,
Could you share the vulnerability itself...?
Since the SMF devs are obviously unable to do the amount of work they're expected to do, I'm sure the SMF team will eventually rely on this.[nb]
I really hope that's sarcasm.
Any sufficiently complex piece of software has bugs, some of which are possibly security related. This particular one is because technology moved on and applications haven't caught up yet. Interestingly this particular vulnerability probably applies to other forums and other applications.