| |||||||||||||
|
| |||||||||||||
Follow up: How to write a Linux virusFollow up: How to write a Linux virusPosted Feb 13, 2009 8:37 UTC (Fri) by roblucid (subscriber, #48964)In reply to: Follow up: How to write a Linux virus by dkite Parent article: Follow up: How to write a Linux virus
> The problem that the .desktop files tried to solve was to have an icon and
> application title associated with an executable file.
If that was all they were intended to provide, the descriptive file could use a map db file for paths to icons and titles. Then .desktop files just need, position info and the look up key. No need to bloat every executable.
(Log in to post comments)
Follow up: How to write a Linux virus Posted Feb 13, 2009 11:20 UTC (Fri) by dgm (subscriber, #49227) [Link]
Note that this will NOT solve the security problem, that is that any program can be disguised as any other. Also, this would require having a central icon db.
Follow up: How to write a Linux virus Posted Feb 13, 2009 12:38 UTC (Fri) by roblucid (subscriber, #48964) [Link]
Yes, so you have your allowed interpreters that understand the file formats. Now when someone saves a file as data, and it's not in your list, you don't legitimise it. People have to install a program, to run the pay load.
How is that worse than interpreters for handling mime types?
Follow up: How to write a Linux virus Posted Feb 13, 2009 15:34 UTC (Fri) by dkite (guest, #4577) [Link]
Great. A Windows Registry.
Derek
|
|
||||||||||||