is lib-safe adopted in fc8? - Security

This is a discussion on is lib-safe adopted in fc8? - Security ; Hi, I've just install fc8 and tried some new tech it use in anti-buffer overflow Here is the test... --------------------------code--------------------------------------- #include int main(int argc,char * argv[]) { char buf[10]; strcpy(buf,argv[1]); return 0; } ------------------------------------------------------------------------ it's a quite obvious stack buffer ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: is lib-safe adopted in fc8?

  1. is lib-safe adopted in fc8?

    Hi,

    I've just install fc8 and tried some new tech it use in anti-buffer
    overflow

    Here is the test...

    --------------------------code---------------------------------------
    #include
    int main(int argc,char * argv[])
    {

    char buf[10];
    strcpy(buf,argv[1]);
    return 0;



    }
    ------------------------------------------------------------------------

    it's a quite obvious stack buffer overflow vul..

    Then I started the program ..
    ../test AAAAAAAAAA
    the argv[1] is just 10 'A' and I got a seg fault?

    I tried gdb test

    (gdb) r AAAAAAAAAA
    Starting program: /root/test AAAAAAAAAA

    warning: Missing the separate debug info file: /usr/lib/debug/.build-
    id/ac/2eeb206486bb7315d6ac4cd64de0cb50838ff6.debug
    (no debugging symbols found)
    Error in re-setting breakpoint 2:
    Function "strcpy" not defined.
    (no debugging symbols found)

    warning: Missing the separate debug info file: /usr/lib/debug/.build-
    id/ba/4ea1118691c826426e9410cafb798f25cefad5.debug
    (no debugging symbols found)

    Breakpoint 2, 0x00bf3c34 in strcpy () from /lib/libc.so.6
    (gdb) c
    Continuing.

    Program received signal SIGSEGV, Segmentation fault.
    0x00000000 in ?? ()
    (gdb) bt
    #0 0x00000000 in ?? ()
    #1 0x00000001 in ?? ()
    #2 0x00000000 in ?? ()

    Is it a lib-safe or something else ?

    Grez




  2. Re: is lib-safe adopted in fc8?

    xi4oyu writes:

    > Hi,
    >
    > I've just install fc8 and tried some new tech it use in anti-buffer
    > overflow


    > Is it a lib-safe or something else ?


    libsafe is a LD_PRELOAD dynamic lib that catches calls to certain
    functions (see the libsafe manpage). You have to specifically use
    libsafe via LD_PRELOAD, or via /etc/ld.so.preload containing the full
    path to libsafe.so.2 binary. So this is likely not libsafe. Also
    libsafe reports in the syslog what it does.

    There's other BO protectors too: libssp, some linker switches, and
    3rd-party kernel add-ons. From what you posted, I can't see if any of
    those are in use, but it doesn't appear libsafe is.


    The binary is like so:

    -rwxr-xr-x 1 root root 20356 2003-02-25 03:14 /lib/libsafe.so.2.0.16



    --
    [** America, the police state **]
    Whoooose! What's that noise? Why, it's US citizen's
    rights, going down the toilet with Bush flushing.
    http://www.wired.com/politics/securi...007/08/wiretap
    http://www.hermes-press.com/police_state.htm

+ Reply to Thread