linux-kernel - Re: [PATCH] Add iSCSI iBFT support.

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 26 Sep 2007 20:16:45 -0400
From:	Konrad Rzeszutek <konrad@...nok.org>
To:	Randy Dunlap <randy.dunlap@...cle.com>
Cc:	linux-kernel@...r.kernel.org, pjones@...hat.com,
	konradr@...hat.com, konradr@...ux.vnet.ibm.com
Subject: Re: [PATCH] Add iSCSI iBFT support.

>
> i.e., what is this binary blob  (?)
>
> I don't see a binary blob in this patch (as stated in the first
> sentence).  I'd say that this patch adds methods for exporting
> (or exposing) the ibft thru sysfs.

I used the wrong choice of words. The correct one is, as you say, to
add methods for exporting the iBFT through sysfs.

>
> Is there some good reason that the iSCSI connection information
> shouldn't be exposed in real sysfs attribute files instead of just
> in a binary file?

My end goal is to export the iBFT data via individual sysfs attribute files. I 
was thinking to do that in the next version of this code and build on top of 
this patch. 

This way the existing exploiter (iscsi-initiator-utils) can use the parsing 
code it already has to extract the data from the binary blob. Then in the 
next version of the iscsi-initiator-utils (and for the kernel) I can post a 
patch for supporting (and exporting in the kernel) individual sysfs attribute 
files.
-
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/