[lkml]   [2008]   [Mar]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH prototype] [0/8] Predictive bitmaps for ELF executables
On Sat 2008-03-22 15:29:49, Andi Kleen wrote:
> On Sat, Mar 22, 2008 at 03:16:31AM -0700, Nicholas Miell wrote:
> >
> > *sigh* this is probably true
> Actually it is a relatively weak argument assuming the standard
> 4k xattrs, but still an issue.
> The other stronger argument against it is that larger xattrs tend to be
> outside the inode so you would have another seek again.
> > > and a mess to manage (a lot of tools don't know about them)
> >
> > At this point in time, all tools that don't support xattrs are
> > defective,
> Good joke.
> > I just have an instinctive aversion towards the kernel mucking around in
> > ELF objects -- for one thing, you're going to have to blacklist
> > cryptographically signed binaries.
> What signed binaries?
> Anyways there are two ways to deal with this:
> - Run the executable through a little filter that zeroes the bitmap before
> computing the checksum. That is how rpm -V deals with prelinked binaries which
> have a similar issue. You can probably reuse the scripts from rpm.

Is this good idea? Attacker can send you binary with the bitmap
inverted, it is now slow on your system and signature matches.

...might be important for benchmarks... 'here, see, Oracle is slow.
Feel free to verify the signature'.

...ok, I guess it is not too serious, because it is similar to
(cesky, pictures)

 \ /
  Last update: 2008-03-23 14:41    [W:0.105 / U:6.816 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site