Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | Replace Issuezilla by Bugzilla 3.2 | ||
---|---|---|---|
Product: | Infrastructure | Reporter: | Frédéric Buclin <LpSolit> |
Component: | Bugzilla | Assignee: | issues@www <issues> |
Status: | CLOSED FIXED_WITHOUT_CODE | QA Contact: | issues@www <issues> |
Severity: | Trivial | ||
Priority: | P3 | CC: | issues |
Version: | current | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All | ||
URL: | http://www.bugzilla.org/releases/3.2/ | ||
Issue Type: | TASK | Latest Confirmation in: | --- |
Developer Difficulty: | --- |
Description
Frédéric Buclin
2008-06-08 23:33:09 UTC
/me wonders if Issuezilla is as easy to manipulate as old Bugzilla versions were. Yes, it is! An old bug which has been fixed for years in Bugzilla. You should definitely upgrade. Any traction or willing to upgrade to Bugzilla 3.x? I wonder how many security bugs are exploitable with Issuezilla. It shouldn't be too hard to inject some SQL code in the DB or hack the backend code; I'm pretty sure. When does CollabNet plan to jump into the 21st century and replace this obsolete Issuezilla by Bugzilla 3.2? There are currently tons of missing features, and Issuezilla cannot work with existing external tools or bots, making it pretty useless. I don't see the point for OpenOffice to still use a proprietary software when open-source provides all it needs, a.k.a Bugzilla. Nice, 3.2.9 is definitely much better than 2.11. :) |