Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Does a Visual Studio debug build contain any personal information?

I'm wondering about privacy and personal information that's contained in the debug files created by Visual Studio.

I have a project that I have compiled for both debug and release, and I have to zip basically the whole directory tree that contains the solution, the source, the pdbs, etc. and make it available.

I'm wondering what type of information will be released by doing this, other than source and binaries obviously.

Thanks!

like image 963
test Avatar asked Jun 22 '11 06:06

test


People also ask

What is a debug build?

The debug build is created with some embedded information which allows the debugger to debug the application and exposed the runtime behavior of the application. On the down side, the debug build is a bit slower and inefficient in execution and larger in size.

What is difference between debug and release build?

Debug Mode: When we are developing the application. Release Mode: When we are going to production mode or deploying the application to the server. Debug Mode: The debug mode code is not optimized. Release Mode: The release mode code is optimized.

What is difference between debug and release in Visual Studio?

Visual Studio projects have separate release and debug configurations for your program. You build the debug version for debugging and the release version for the final release distribution. In debug configuration, your program compiles with full symbolic debug information and no optimization.

How do you create binary debug information?

Right click your project in Solution explorer and select "properties" Select "Configuration Properties" Select "Debugging" in "Generate Debug Info" select "Yes (/DEBUG)"


1 Answers

Done correctly you will not release any personal information by doing this.

Things to watch out for:

  • Sensitive information in paths. If you keep your source files in My Documents folder, your Windows user name will be leaked in .pdb files, as it embeds full source file paths. I recommend copying solution to directory c:\dev\project (or similar) and rebuilding there.

  • Don't publish .suo, .user files, as these may contain sensitive information, and are generated by studio automatically for each user

  • Look out for sensitive information that may be in app.config files

One more suggestion: don't publish any intermediate files (usually in obj directory). These will not help recipients in any way, but may contain personal information.

like image 150
Juozas Kontvainis Avatar answered Oct 29 '22 09:10

Juozas Kontvainis