lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date:	Sun, 30 May 2010 20:54:59 +0200
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	linux1394-devel@...ts.sourceforge.net
CC:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] firewire: core: check for 1394a compliant IRM,	fix inaccessibility
 of Sony camcorder

H.S. wrote:
> Stefan Richter wrote:
> <SNIP>
>> The patch was generated against the latest kernel sources but is
>> applicable with harmless line offsets to the 2.6.32.y stable kernel
>> series too.  Hence it should be applicable to Debian's 2.6.32 sources as
>> well.
>>
>> H. S., could you please test this?
> 
> Yes, I can give it a shot. Please pardon this basic question, should I
> be downloading the vanilla kernel source, patching it, compiling it and
> then testing it?

Either this or the sources of the Debian kernel that you are currently
running.  The latter may perhaps be preferable for an easier switch
between distributed kernel and patched kernel.

> Or is there a precompiled binary available for download
> (i368 or amd64) with this patch included?

Alas not.
(I could build such a package if I had Debian myself, but I don't.)

> I admit I have never patched
> and compiled a kernel before for testing a patch. I have, however,
> compiled kernels numerous times quite a while ago (just for learning
> objectives).

OK; the patching as additional step is going to be the easiest one.

A quick web search turned up the following pointers for using a custom
kernel on Debian:
http://www.debian.org/doc/FAQ/ch-kernel.en.html
http://www.debian.org/releases/stable/i386/ch08s06.html.en
(I hope the described method provides an already configured kernel
source tree with Debian's configuration as baseline.)

Before you start compilation, save the email with the patch somewhere,
change into the top-level directory of the kernel sources, and apply the
patch with "patch -p1 < /the/path/to/the/email".
-- 
Stefan Richter
-=====-==-=- -=-= ====-
http://arcgraph.de/sr/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists