Re: [cobalt-developers] gmon.out a security issue?

[CJ Johnson <cj.johnson@xxxxxxx>]

	> From     : Jeff Lasman <jblists@xxxxxxxxxxxxx>
	> 
	> Is it poossible for the gmon.out to be owned by root if
	> the compilation wasn't done as root?  Somehow I don't
	> think so.

    The gmon.out file is written by the application when it
    runs, so the person who ran the compile isn't an issue.

    If you compile with the right flags, you get a profiling
    version of the application.  When the application is run,
    you get a gmon.out.  You then use gprof to chew on the
    gmon.out and spit out profiling information about the
    dynamic behavior of the application.

    So if you have a gmon.out owned by root, either the
    profiled application is setuid root, or the application
    was run by root.

    Of course it is also possible to take an application that
    is compiled for profiling, and move it to another system.
    When the application is run on the target system, you will
    get a gmon.out even if there is no compiler on the target.

    My guess is that some program was built with a broken
    Makefile that resulted in a '-pg' flag on the cc line.
    If this is happening on boxes that are 100% stock Cobalt,
    then we must have a RPM with such a typo.  

    What flavor of systems and builds are being infested with
    gmon.out droppings?

    cj*