From: Derek Glidden <dglidden@illusionary.com>
To: linux-kernel@vger.kernel.org
Cc: integrit-devel@lists.sourceforge.net
Subject: 2.4.20-aa1 breaks integrit
Date: 16 Jan 2003 15:51:36 -0500 [thread overview]
Message-ID: <1042750297.26999.10.camel@two.nks.net> (raw)
integrit is a filesystem checksumming tool:
http://integrit.sourceforge.net/
something in 2.4.20-aa1 breaks its ability to correctly determine
whether a file has been changed or not. _every_ file will turn up "new"
on subsequent runs of integrit, even if nothing about that file has
changed.
2.4.19-aa1 worked correctly.
2.4.20 "plain" works correctly.
I apologize for the vagueness of this report. I know that -aa are
collections of patches from other places and I have no idea which piece
may be breaking integrit, nor any real idea what the underlying problem
really is.
And no idea who to specifically contact, either, since I don't really
know where the breakage is occurring. :-P
Please reply directly for more info if needed.
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
#!/usr/bin/perl -w
$_='while(read+STDIN,$_,2048){$a=29;$b=73;$c=142;$t=255;@t=map
{$_%16or$t^=$c^=($m=(11,10,116,100,11,122,20,100)[$_/16%8])&110;
$t^=(72,@z=(64,72,$a^=12*($_%16-2?0:$m&17)),$b^=$_%64?12:0,@z)
[$_%8]}(16..271);if((@a=unx"C*",$_)[20]&48){$h=5;$_=unxb24,join
"",@b=map{xB8,unxb8,chr($_^$a[--$h+84])}@ARGV;s/...$/1$&/;$d=
unxV,xb25,$_;$e=256|(ord$b[4])<<9|ord$b[3];$d=$d>>8^($f=$t&($d
>>12^$d>>4^$d^$d/8))<<17,$e=$e>>8^($t&($g=($q=$e>>14&7^$e)^$q*
8^$q<<6))<<9,$_=$t[$_]^(($h>>=8)+=$f+(~$g&$t))for@a[128..$#a]}
print+x"C*",@a}';s/x/pack+/g;eval
usage: qrpff 153 2 8 105 225 < /mnt/dvd/VOB_FILENAME \
| extract_mpeg2 | mpeg2dec -
http://www.cs.cmu.edu/~dst/DeCSS/Gallery/
http://www.eff.org/ http://www.anti-dmca.org/
reply other threads:[~2003-01-16 20:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1042750297.26999.10.camel@two.nks.net \
--to=dglidden@illusionary.com \
--cc=integrit-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®