full-disclosure - Security Bug in MSVC

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] [day] [month] [year] [list]

Message-ID: <BAY19-DAV87567E37CA21F2EA86FE4D91F0@phx.gbl>
Date: Fri Jan 20 00:09:03 2006
From: se_cur_ity at hotmail.com (Morning Wood)
Subject: Security Bug in MSVC

> What's the point of building a bunch of sources unless
> 1. you trust their author, or
> 2. you have made sure their is nothing malicious there?
> 
> When you build an executable from untrusted sources, you get an untrusted
> executable. Either you run it and you're screwed anyway, or you don't run
> it and you wasted your time building it.
> 

again...

this does not exploit the source code.
it does exploit the build files.

if i was simply compiling badprog.c
then launching it, that would be stupid.

i am leveraging the project files, not the source code.

MW