full-disclosure - Re: Evilgrade 2.0 - the update explotation framework is back

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <172212.1288536001@localhost>
Date: Sun, 31 Oct 2010 10:40:01 -0400
From: Valdis.Kletnieks@...edu
To: Christian Sciberras <uuf6429@...il.com>
Cc: full-disclosure <full-disclosure@...ts.grok.org.uk>
Subject: Re: Evilgrade 2.0 - the update explotation
	framework is back

On Sun, 31 Oct 2010 14:24:59 BST, Christian Sciberras said:

> In my opinion, all in all, you're creating a yet another overly complex
> system with as yet more possible flaws.
> Don't forget tat each new line of code is a potential attack vector which
> affects any system.

Amen to that.

A more subtle issue is the tradeoff issue:  Any time they have a code engineer
spending time building and feeding that code-signing infrastructure is time that
code engineer *isn't* spending writing actual new features the users *want*.

Which user-requested feature are you going to heave over the side in order to
do code-signing instead?  That question has to enter into the calculus as well.

Content of type "application/pgp-signature" skipped

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/