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  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 12 Jan 2015 12:27:53 +0100
From:	Richard Weinberger <richard@....at>
To:	Harald Geyer <harald@...ib.org>
CC:	Jonathan Cameron <jic23@...nel.org>, knaack.h@....de,
	lars@...afoo.de, pmeerw@...erw.net, sanjeev_sharma@...tor.com,
	linux-iio@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCHv2 1/3,RESEND] iio: dht11: Fix out-of-bounds read

Am 12.01.2015 um 12:26 schrieb Harald Geyer:
> Richard Weinberger writes:
>> Am 10.01.2015 um 12:14 schrieb Jonathan Cameron:
>>> On 07/01/15 12:15, Harald Geyer wrote:
>>>> As we access i-1 we must not start with i=0.
>>>>
>>>> From: Richard Weinberger <richard@....at>
>>>> Signed-off-by: Richard Weinberger <richard@....at>
>>>> Acked-by: Hartmut Knaack <knaack.h@....de>
>>>> Acked-by: Harald Geyer <harald@...ib.org>
>>>> Reviewed-by: Sanjeev Sharma <sanjeev_sharma@...tor.com>
>>>> ---
>>>> Resending again to get the metadata right.
>>> Putting a From: in doesn't work, you need to use
>>> git commit --amend --author to fix it up.
>>
>> Or just use "git am" to apply a patch to a tree and keep the original author.
>> If you use "git format-patch" later it will produce the correct "From:".
> 
> Thats exactly what I did initially, but of course when pasting the
> patch into my MUA, the headers got lost. I guess you don't suggest that
> I forge your address, so what's the right way to handle this? Include
> the entire mbox file into the body of the message?

Use git send-email. :-)

Thanks,
//richard
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ