I guess it was useful for downloading individual tables, in addition to the CSV backup. But I don't think I've ever heard of anyone's site being compromised through that specific feature. I mean, once you have admin access, there's better ways into the server.
If you have only adminCP access, not really. It doesn't necessarily follow that those credentials get you into the server too.
I definitely agree with blind-eddie and you this was a major security flaw in v3.
If you have only adminCP access, not really. It doesn't necessarily follow that those credentials get you into the server too.
I definitely agree with blind-eddie and you this was a major security flaw in v3.
It would be pretty trivial to re-add the functionality via a creative plugin, or template, or a bit of both. So it all depends on how skilled an admin is and if you're giving them access to stuff like plugins/templates and trust them.
We removed the backup functionality because it was not dependable to create quality backups. Instead of spending additional time improving it, it was removed. We'd recommend that customer use better tools like the raw MySQLdump command line too, or software designed to do backups like mysqldumper.
Right but, being able to download the tables is unique to v3 and earlier. Plus, the ability to run queries must be permissioned in config file.
It doesn't seem to be something that was ever used, at least not proficiently. And it was in vB 3 as far back as I can remember. I'm not entirely sure it isn't tied to a script permission, but I'd have to check. It just seems like it was so unreliable not even hackers bothered with it.
It doesn't seem to be something that was ever used, at least not proficiently. And it was in vB 3 as far back as I can remember. I'm not entirely sure it isn't tied to a script permission, but I'd have to check. It just seems like it was so unreliable not even hackers bothered with it.
Or they might not have known about it. It IS a obscure function.
It doesn't seem to be something that was ever used, at least not proficiently. And it was in vB 3 as far back as I can remember. I'm not entirely sure it isn't tied to a script permission, but I'd have to check. It just seems like it was so unreliable not even hackers bothered with it.
It was used pretty often by some customers, I remember getting complaints about it early on in vB4's life cycle. But honestly, people who used the tool rarely got full backups, which caused more problems.
We removed it for the sake of causing less problems in the long run, IIRC.