From: Fengkai Sun <qcloud1014@gmail.com>
To: libc-help@sourceware.org
Subject: Cannot audit dlopen-ed libraries?
Date: Wed, 30 Jun 2021 20:49:56 +0800 [thread overview]
Message-ID: <CAF6YOcOH8V7mcosXtE2c9nhU3HY+xkqWQJPUCfv3j6C2-4CAsQ@mail.gmail.com> (raw)
Hi list,
I want to use the audit interface to change the symbol bindings in
dlopen-ed libraries. However, the bindings in such libraries seem uncatched
by it:
// lib1.c
#include <stdio.h>
#include <stdlib.h>
int foo()
{
printf("hello world\n");
void *p = malloc(16);
return 0;
}
//libaudit.c
#define _GNU_SOURCE
#include <link.h>
#include <stdio.h>
#include <stdlib.h>
#include <dlfcn.h>
unsigned int la_version(unsigned int version)
{
return LAV_CURRENT;
}
unsigned int la_objopen(struct link_map *map, Lmid_t lmid, uintptr_t
*cookie)
{
// monitor everything
return LA_FLG_BINDTO | LA_FLG_BINDFROM;
}
uintptr_t la_symbind64(Elf64_Sym *sym, unsigned int ndx, uintptr_t
*refcook, uintptr_t *defcook, unsigned int *flags, const char *symname)
{
printf("binding symbol: %s\n", symname);
return sym->st_value;
}
// main.c
#include <stdlib.h>
#include <dlfcn.h>
int main()
{
void *handle = dlopen("./lib1.so", RTLD_NOW);
int (*foo)() = dlsym(handle, "foo");
foo();
return 0;
}
And the result is:
binding symbol: _dl_find_dso_for_object
binding symbol: __tunable_get_val
binding symbol: dlopen
binding symbol: _dl_catch_error
binding symbol: dlsym
binding symbol: _dl_sym
binding symbol: foo
hello world
I was expecting printf and malloc to appear, but it seems that only symbols
from main program are catched.
Is this an expected behavior or I misused the audit interface?
Thanks for your time.
Best,
Fengkai
next reply other threads:[~2021-06-30 12:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-30 12:49 Fengkai Sun [this message]
2021-07-07 9:23 ` Fengkai Sun
2021-07-07 9:25 ` Florian Weimer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAF6YOcOH8V7mcosXtE2c9nhU3HY+xkqWQJPUCfv3j6C2-4CAsQ@mail.gmail.com \
--to=qcloud1014@gmail.com \
--cc=libc-help@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).