Last modified: 2007-01-05 00:53:44 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T10486, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 8486 - someone's uploaded a virus onto the bugzilla system
someone's uploaded a virus onto the bugzilla system
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
PC All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-01-04 13:54 UTC by Duncan Harris
Modified: 2007-01-05 00:53 UTC (History)
0 users

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Duncan Harris 2007-01-04 13:54:05 UTC
I don't know but the following is mentioned in the quip system:

*** VIRUS Warning ***

(I think):  do not try this without wearing protection:

*** VIRUS warning (again, just to make sure) ***

http://bugzilla.wikimedia.org/attachment.cgi?id=2696

This needs to be deleted and removed from the quip system (which incidentally
could do with a bit of tidying).  It's been there for a little while with no-one
noticing.  

Sorry I know this probably isn't the way I'm supposed to handle it but atleast
this way it'll get seen by the appropriate person(s).  I tried uploading a quip
to say so but that was ignored.
Comment 1 Brion Vibber 2007-01-05 00:53:44 UTC
Note that it doesn't do any harm sitting there, it's just a PHP script (with no
way of being executed either server or client-side unless you go to a huge, huge
amount of trouble).

Since it's a huge pain in the ass to delete anything from bugzilla, there's
little point to digging in the database to kill it and I didn't feel like
shuffling around for the database password at the time. :)

If it makes you feel better, though, I've gone ahead and done it now.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links