Since the Everyblog module has been unpublished, does that mean it is also unmaintained?
I would like to continue using it in the site I am currently developing (not yet in production). I would be willing to try and address the security issues and re-commit a new version if possible. Would you be able to transfer ownership and/or set me up as a maintainer and provide me with info about the security issues?
I understand that you do not want to make the security issues publicly known. I would just need them so I know what needs to be fixed.
thanks
Comments
Comment #1
celadon commentedHello?
I posted this six weeks ago and have not gotten any kind of response. The original maintainer of the everyblog module appears to be MIA, the module has been pulled, but I and others would like to get it fixed and re-posted. I am willing to take it on and will begin doing my own security review and upgrade using the existing code I have (6.x-1.3-beta2) but it would be nice to at least get a response of some sort. If I can get some specific issues I should address, that would make my task a little easier...
thanks - celadon
Comment #2
deekayen commentedThe webmasters aren't going to step on the security team and the security team won't discuss vulnerabilities in the open. I suggest you write to the security team and reference this issue. http://drupal.org/security-team
Comment #3
avpadernoI think celadon just wants to become the maintainer of EveryBlog, which he reports it is not published anymore.
Being this the case, he cannot open a support request to ask to become co-maintainer.
The project page has not been deleted, therefore celadon must open a support request asking to become co-maintainer of the project. The project owner already replied to a similar request made on December First from mrjeeves.
Comment #4
avpadernoI guess the status of the report should be changed to fixed.