Re: [Full-disclosure] 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
_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/

Relevant Pages

  • Re: embedding passwords/other sensitive strings into a C++ program
    ... > someone looking at the source code, pulling the project files out of ... > the repository (we use cvs, ... accessible on the next compile (or even modify the EXE version of the file ... unlimited access to your source code and who ...
    (comp.lang.cpp)
  • Re: .Net and SourceSafe
    ... "Arjuna" wrote in message ... Under IDE 6 we were able to ... This made it possible to backup the source code without ... > SourceSafe unless they are co-located with the project files. ...
    (microsoft.public.vsnet.ide)
  • Re: Is a custom project hierarchy possible for C# projects?
    ... The file hierarchy that I want ... decouples the project files from the source code and also have them under ... the schemas that define the MSBuild tags in the .NET directory do ...
    (microsoft.public.dotnet.languages.csharp)
  • Is a custom project hierarchy possible for C# projects?
    ... /temp (obj files) ... I want the solution and project files in the IDE directories, ... those project files to have the source code root directory point to /src ... Visual Studio do this. ...
    (microsoft.public.dotnet.languages.csharp)