linux-kernel - Re: [PATCH] x86: mkpiggy.c: fix resource leakage

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]

Message-ID: <CAGG-pUT2FJtnih23rZbA8XQMHq7s9GTZCUSEW7yPg3+kOM4VLQ@mail.gmail.com>
Date:	Mon, 7 Oct 2013 20:41:05 -0300
From:	Geyslan Gregório Bem <geyslan@...il.com>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	tglx@...utronix.de, mingo@...hat.com, x86@...nel.org,
	linux-kernel@...r.kernel.org,
	kernel-br <kernel-br@...glegroups.com>
Subject: Re: [PATCH] x86: mkpiggy.c: fix resource leakage

Peter,

Yes, Really doesn't have leakage, I explained it. The changes are just
to cleanup the code following a secure pattern.

Geyslan Gregório Bem
hackingbits.com


2013/10/7 H. Peter Anvin <hpa@...or.com>:
> On 10/07/2013 03:16 PM, Geyslan G. Bem wrote:
>> Even though the resource is released when the application is closed or
>> when returned from main function, modified to make it in accordance.
>> Now FILE pointer is always verified.
>
> By the way, the subject is misleading - there is no resource leakage
> since the program is terminated anyway.
>
>         -hpa
>
>
--
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/