Open Source

30314 readers

2146 users here now

All about open source! Feel free to ask questions, and share news, and interesting stuff!

Useful Links

Rules

Posts must be relevant to the open source ideology
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon from opensource.org, but we are not affiliated with them.

founded 5 years ago

MODERATORS

[email protected]

202

Malicious Plugin in Pidgin (Chat Application) (pidgin.im)

submitted 3 weeks ago by [email protected] to c/[email protected]

16 comments fedilink hide all child comments

Greetings everyone. It is with much regret that I am writing this post. A plugin, ss-otr, was added to the third party plugins list on July 6th. On August 16th we received a report from 0xFFFC0000 that the plugin contained a key logger and shared screen shots with unwanted parties.

We quietly pulled the plugin from the list immediately and started investigating. On August 22nd Johnny Xmas was able to confirm that a keylogger was present.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 30 points 3 weeks ago (3 children)

Without some sort of reproducible builds (which are really finnickey to actually get) this doesn't really help though. Adding some set of malicious patches before doing the binary release is trivial.

[–] [email protected] 15 points 3 weeks ago

I agree that reproducible builds would be ideal and modifying binary releases is trivial, but any step forward is better than no review process at all.

There's no such thing as a perfect system. It's all about increasing the number of hoops for an attacker to jump through. This is at least a step in the right direction.

[–] [email protected] 9 points 3 weeks ago

True. My point was more that it's an improvement, not really a broad solution.

[–] [email protected] 7 points 3 weeks ago

You don't need reproducible builds. You can get by if you trust whoever compiled it, like your distro's maintainers or the pidgin developers.