Featured Articles

Analysts expect ARM to do well next year

Analysts expect ARM to do well next year

British chip designer ARM could cash in on the mobile industry's rush to transition to 64-bit operating systems and hardware.

More...
Huawei and Xiaomi outpace Lenovo, LG in smartphone market

Huawei and Xiaomi outpace Lenovo, LG in smartphone market

Samsung has lost smartphone market share, ending the quarter on a low note and Xiaomi appears to be the big winner.

More...
Intel Broadwell 15W coming to CES

Intel Broadwell 15W coming to CES

It looks like Intel will be showing off its 14nm processors, codenames Broadwell, in a couple of weeks at CES 2015.

More...
Gainward GTX 980 Phantom reviewed

Gainward GTX 980 Phantom reviewed

Today we’ll be taking a closer look at the recently introduced Gainward GTX 980 4GB with the company’s trademark Phantom cooler.

More...
Zotac ZBOX Sphere OI520 barebones vs Sphere Plus review

Zotac ZBOX Sphere OI520 barebones vs Sphere Plus review

Zotac has been in the nettop and mini-PC space for more than four years now and it has managed to carve…

More...
Frontpage Slideshow | Copyright © 2006-2010 orks, a business unit of Nuevvo Webware Ltd.
Wednesday, 21 March 2012 11:16

Hackers nick digital certificate

Written by Nick Farrell



Insecurity expert warns to be careful where you sign


Kaspersky Lab has discovered that a recently distributed Trojan, Mediyes, was digitally signed using a stolen private signature key whose digital certificate was owned by Swiss firm Conpavi AG.

According to John Grimm of Thales e-Security what the situation shows is how digitally signed code is assessed more favorably by anti-virus vendors from a risk perspective, so stealing the key and creating a perfectly valid signature on the code helps further promulgate the nefarious Trojan before it can be detected.

He said that whenever evidence surfaces such as this, we worry that people will incorrectly assume that the concepts of digital signatures and key management are flawed. The problem is not the concept; the problem is that those responsible for the keys and the digital signature process are not following standards of due care. If the keys are not afforded proper protection, it's easy to find them, steal them and create “valid” signatures over maliciously modified code.

He  advises companies never to allow anyone to come into possession of the full plain text of a private or secret key. While the circumstances in this situation are still to become clear, the private key was indeed somehow compromised, which means someone was able to access it in full plain text.

While not listed as a standard of due care, best practice suggests encryption keys should be protected in high assurance hardware-- not software-- since it's an absolute failsafe way to ensure the keys are not exposed outside the protected boundary of a certified, tamper-proof device. The lesson learned here, once the dust has settled, is to ensure that keys involved in code signing are protected in dedicated hardware as opposed to being stored on more vulnerable host computers.


Nick Farrell

E-mail: This e-mail address is being protected from spambots. You need JavaScript enabled to view it
blog comments powered by Disqus

 

Facebook activity

Latest Commented Articles

Recent Comments