| |||||||||||||
|
| |||||||||||||
WordPress 2.1.1 contained a trojan horseWordPress 2.1.1 contained a trojan horsePosted Mar 4, 2007 18:46 UTC (Sun) by intgr (subscriber, #39733)In reply to: WordPress 2.1.1 contained a trojan horse by jwb Parent article: WordPress 2.1.1 contained a trojan horse
No, but changed public keys, or public key fingerprints, on web sites are more likely to be noticed, as a single developer would use the same public key in more than one place.
And if you have already acquired the developer's public key earlier, you can use that to verify subsequent releases, and you don't have to rely on trusting the web site for public key distribution. In addition to that, you can rely on other people who trust the given developer, through the web of trust.
In short, it doesn't solve world hunger, but it would help a lot.
(Log in to post comments)
|
|
||||||||||||