Restoring quarantined hacks
 

Please try to be faster when restoring fixed hacks from quarantine.

People is asking me via PMs what's going on with one of my hacks which is quarantined, but has been fixed yesterday. It just needs to be approved by Staff.

Thanks

Easter weekend Cyb... ;)

people who request too much things have no real life, we have a problem here!

Usually, we leave it up to the person who quarantined it, and since I don't know the exploits (don't think exact details were posted), I personally can't check it.

Items will be restored as and when the person involved has time to check them, posting in the forum will not speed that process up (indeed, it may slow it down as it creates more work reading your posts).

I think the request here was a more general one. I think the process of how hacks are quarantined could be improved.

for example when the hack/thread is quarantined the mod could leave details that only the staff could see, so then other staff could restore the thread when the hack has been fixed much faster.

this is the site feedback section afterall.

That already happens - its the whole point of the quarantine process. However, staff need to have the time to check the modification one last time, this includes any other unrelated exploits.

In this case, as it happened over Easter - I think you can forgive us. :)

you can not be forgiven, you are perfect, you are without failures, you are robots...

did i do a typo here?

It's all ok with me, don't get me wrong, but users are waiting for an update. ;)

nexialys, you should be warned for spamming. :p

Cyb, you are not a moderator... ROFL

Personally, I think a much bigger problem is how to get non-working mods put in quarantine. I can think of at least two that are still being sold & installed, but they haven't worked in ages (if ever).

Quarantine is for modifications that can be exploited, and hence, affecting the security of a member's board. If you can present reasons how a non-working modification affects the security of a board, sure, they can go there as well. :)

Staff don't know if a modification is vulnerable until a member reports the issue to us. Once reported a staff member will check the code to verify if there i a vulnerability. If it is confirmed, the modification will be quarantined until staff does not spot any vulnerabilities. Depending on the size of the modification this can be a long process as we have to manually go over all the coding and see if we can spot any vulnerable coding. And once it has been corrected by the author, we will need to do another check to see if everything is resolved. This is not something that can be done in a hurry. Very often a modification that has 1 vulnerable part of code, also will have more issues. But we only know that after we went over all the (new) code again. And yes, this is much easier if the same person who did the first check (and knows best what he found), does the 2nd check. In cases like a weekend or holiday, this can take a bit longer then normal but is really needed to ensure the quality. If the handling staff member is offline too long, then another staff member will take over, but we prefer to have it handled by a single person.

Oh the irony here. :D

<3