From: Lee Revell <rlrevell@joe-job.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: alsa-devel@alsa-project.org,
Olivier Galibert <galibert@pobox.com>,
linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>,
Olaf Hering <olh@suse.de>,
James Courtier-Dutton <James@superbug.co.uk>,
Adrian Bunk <bunk@stusta.de>,
perex@suse.cz
Subject: Re: OSS driver removal, 2nd round
Date: Sun, 02 Jul 2006 17:16:18 -0400 [thread overview]
Message-ID: <1151874979.25802.31.camel@mindpipe> (raw)
In-Reply-To: <Pine.LNX.4.61.0607022304230.5218@yvahk01.tjqt.qr>
On Sun, 2006-07-02 at 23:08 +0200, Jan Engelhardt wrote:
> >> Well you could patch the affected plugin's .dynstr table so that it should at
> >> best try to call a function that has not yet been defined somewhere else (like
> >> open); IOW, you change the .dynstr entry from 'open' to say 'my_open', and
> >> regularly include libmy.so through e.g. LD_PRELOAD.
> >>
> >> Of course the MD5 won't match afterwards, but I think the plugin should execute
> >> as usual afterwards, since .dynstr is something no app should rely on.
> >
> >Is this likely to work with an app like Skype that takes extensive steps
> >to thwart reverse engineers?
>
> We do not reverse engineer the .text section, but change the .dynstr
> section that is specific to the ELF format. I doubt any app out there md5s
> itself.
>
It's possible. They certainly try very hard to thwart reverse
engineers.
http://www.secdev.org/conf/skype_BHEU06.handout.pdf
Lee
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
next prev parent reply other threads:[~2006-07-02 21:16 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-29 19:21 OSS driver removal, 2nd round Adrian Bunk
2006-06-30 15:48 ` Ralf Baechle
2006-06-30 16:13 ` James Courtier-Dutton
[not found] ` <44A54D8E.3000002@superbug.co.uk>
2006-06-30 16:31 ` Olivier Galibert
[not found] ` <20060630163114.GA12874@dspnet.fr.eu.org>
2006-06-30 21:29 ` Lee Revell
[not found] ` <1151702966.32444.57.camel@mindpipe>
2006-06-30 21:34 ` Arjan van de Ven
2006-06-30 21:42 ` İsmail Dönmez
2006-06-30 21:56 ` Lee Revell
2006-06-30 23:49 ` İsmail Dönmez
2006-07-03 22:38 ` Bill Davidsen
[not found] ` <1151703286.11434.61.camel@laptopd505.fenrus.org>
2006-06-30 21:54 ` Lee Revell
2006-07-01 7:31 ` Olivier Galibert
2006-07-01 7:43 ` James Courtier-Dutton
2006-07-01 13:52 ` Lee Revell
2006-07-02 6:55 ` James Courtier-Dutton
2006-07-02 9:58 ` Jan Engelhardt
2006-07-02 15:28 ` Lee Revell
2006-07-02 21:08 ` Jan Engelhardt
2006-07-02 21:16 ` Lee Revell [this message]
2006-07-03 9:26 ` Jan Engelhardt
2006-07-01 9:26 ` Jaroslav Kysela
2006-07-01 16:01 ` Adrian Bunk
2006-07-01 23:12 ` Adrian Bunk
2006-07-03 11:52 ` Benjamin Herrenschmidt
2006-07-03 19:42 ` Adrian Bunk
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=1151874979.25802.31.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=James@superbug.co.uk \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=alsa-devel@alsa-project.org \
--cc=bunk@stusta.de \
--cc=galibert@pobox.com \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=olh@suse.de \
--cc=perex@suse.cz \
/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