Closed
Bug 777532
Opened 13 years ago
Closed 9 years ago
Governmental trojan Claims to be Firefox
Categories
(Marketing :: Trademark Violations, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jan, Assigned: liz)
Details
According to this tweet, a sample of a governmental software to spy people claims to be Firefox: https://twitter.com/mikko/status/228157834980913152
Comment 1•13 years ago
|
||
I see no further proof of the screenshot actually being legitimate, but the person who tweeted it (mikko) is the CEO of F-Secure, which makes me more inclined to believe such a statement.
Summary: Governmental Spyware Claims to be Firefox → Governmental trojan Claims to be Firefox
| Assignee | ||
Comment 2•13 years ago
|
||
Gerv - Do you think this is more of a potential MPL violation than trademark issue?
Tomcat - If this is a potential trademark issue, could you check out the "FinSpy governmental trojan sample" to see if it is violating our trademark in any way?
Comment 3•13 years ago
|
||
Liz: if they aren't using MPLed code, it can't be an MPL violation. I only have the tweet to go on, but I assume this trojan isn't based on the Firefox codebase, it has just adopted our name. Which would put it in trademark territory.
I don't know details about FinSpy, but if we can be certain who is responsible for it, I can see a case for a trademark suit, if we want to bring one :-)
Gerv
Comment 4•13 years ago
|
||
(In reply to Liz Compton from comment #2)
> Gerv - Do you think this is more of a potential MPL violation than trademark
> issue?
>
> Tomcat - If this is a potential trademark issue, could you check out the
> "FinSpy governmental trojan sample" to see if it is violating our trademark
> in any way?
Hi Liz (and Gerv) will check it out. Do not have a current sample of the trojan but will see if i get one in a safe vm to check out for trademark issues
| Assignee | ||
Comment 5•9 years ago
|
||
This was taken care of long ago, I just forgot to close the bug.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•