Preventing your application from becoming a Trojan Horse
Issue: 14.3 (May/June 2016)
Author: Sam Rowlands
Author Bio: Sam is a pixelMancer and codeWeaver at Ohanaware.
Article Description: No description available.
Article Length (in bytes): 9,964
Starting Page Number: 22
Article Number: 14304
14304project.zip Updated: 2016-05-02 11:15:49
Related Link(s): None
Excerpt of article text...
Earlier on this year,
Transmission(a popular application used for downloading BitTorrents) was hacked, turned into a Trojan Horse, and re-posted on the publisher's website. The hackers even infiltrated the update system so that the modified version was then automatically downloaded by existing users.
I started a thread on the Xojo forums in an effort to get the community to think about computer security and how we as developers can we reduce the likelihood of becoming transit mechanisms for nefarious purposes.
Below is a quote from Reuters' report on the incident:
Transmission representative John Clay told Reuters via email that the ransomware was added to the disk-image of its software after the project's server was compromised in a cyber attack.
"We're not commenting on the avenue of attack, other than to say that it was our main server that was compromised," he said. "The normal disk image (was) replaced by the compromised one."
...End of Excerpt. Please purchase the magazine to read the full article.