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: <201109162307.FFF57890.OSFOtFLHJQVOMF@I-love.SAKURA.ne.jp>
Date:	Fri, 16 Sep 2011 23:07:35 +0900
From:	Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
To:	nab@...ux-iscsi.org
Cc:	zohar@...ux.vnet.ibm.com, andy.shevchenko@...il.com,
	safford@...son.ibm.com, target-devel@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC][PATCH 5/5] target: check hex2bin result

Mimi Zohar wrote:
> Now that hex2bin does error checking, on error add debugging error msg.

We are waiting for response from Nicholas, aren't we?
Quotuing from http://www.spinics.net/linux/fedora/linux-security-module/msg11570.html :
| I was assuming that, by adding error check, hex2bin() will leave the buffer
| uninitialized in case of bad input because hex2bin() user in Linux 3.0 can
| return errors. Now you are a new user of hex2bin() but your code cannot return
| errors. Nicholas, how do you want to handle bad input?
--
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