From: Andy Grover <andy@groveronline.com>
To: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
Cc: Dax Kelson <dkelson@gurulabs.com>,
target-devel@vger.kernel.org,
linux-scsi <linux-scsi@vger.kernel.org>,
Jerome Martin <jxm@risingtidesystems.com>
Subject: Re: TPG_Authentication style not supported by kernel?
Date: Fri, 14 Jun 2013 17:04:54 -0700 [thread overview]
Message-ID: <51BBAFA6.9090708@groveronline.com> (raw)
In-Reply-To: <1371245691.15314.120.camel@haakon3.risingtidesystems.com>
On 06/14/2013 02:34 PM, Nicholas A. Bellinger wrote:
> Hi Dax,
>
> On Tue, 2013-06-11 at 16:21 -0600, Dax Kelson wrote:
>> I have a fully updated Fedora 18 box with kernel 3.9.4-200.
>>
>> I'd like to use the technique listed here:
>>
>> http://linux-iscsi.org/wiki/ISCSI#TPG_Authentication
>>
>> Specifically, "Setting up authentication information for every single
>> initiator separately can be cumbersome, so targetcli provides the
>> capability to define common login information for all Endpoints in a
>> TPG. As a result, all initiators connecting to that TPG can use the
>> same login credentials."
>>
>> The only problem is that the kernel doesn't appear to support this?? I
>> don't see an "auth" directory under the tpgt directory.
>>
>> Help?
>>
>
> So TPG authentication has not been included into mainline + targetcli as
> of yet, so it actually should not be on the wiki..
>
> That said, it's an TODO item on my list to add proper support for v3.11
> -> v3.12 mainline kernel code.
>
> --nab
git://linux-iscsi.org/targetcli.git
commit ab442938d5516e8748b4a323f991b6a8aa5bab5a
Author: Jerome Martin <jxm@risingtidesystems.com>
Date: Thu Dec 15 13:33:20 2011 +0100
Added generic auth support in ui_node
* Replaces Node ACL ad-hoc auth support
* Allows auth support in TPGT (recently added in iSCSI)
Actually support was added to targetcli in Dec 2011.
Obviously this is another feature that has been in your proprietary
product for *years*. Can you at least be upfront with us on what the
features you have implemented but not yet shared publicly are, and what
your schedule for open-sourcing them is? Or at least highlight the
differences on the linux-iscsi.org website? Because people look at that
website and assume those features are in the mainline Linux kernel.
-- Andy
parent reply other threads:[~2013-06-15 0:14 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1371245691.15314.120.camel@haakon3.risingtidesystems.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51BBAFA6.9090708@groveronline.com \
--to=andy@groveronline.com \
--cc=dkelson@gurulabs.com \
--cc=jxm@risingtidesystems.com \
--cc=linux-scsi@vger.kernel.org \
--cc=nab@linux-iscsi.org \
--cc=target-devel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.