From: Lee Duncan <leeman.duncan@gmail.com>
To: stgt@vger.kernel.org
Subject: possible issue with CHAP
Date: Wed, 7 Feb 2024 15:39:04 -0800 [thread overview]
Message-ID: <EE0EC088-7F99-4FC5-AF54-E959644CEBA5@gmail.com> (raw)
Hi:
Long time no talk.
I was testing a possible bug in open-iscsi initiator today, and I tried the tgt target for the first time in a while.
My issue has to do with CHAP. I am trying to generate an error by setting up CHAP in my open-iscsi initiator, and not setting it up in your target. I expect my initiator to complain that there is no CHAP.
But to my surprise I’m able to login to the target, even though I’m expecting CHAP. Is this expected.
I thought (perhaps incorrectly) that the initiator and target would negotiate the authmethod at startup. My initiator would say “CHAP”, and the target would say “None”, and they wold fail.
When I try this with the kernel LIO target. it definately complains that it cannot login.
So what do you think? What is the correct behavior?
P.S. Please include my email in replies, as I’m not yet on your mailing list.
—
Lee Duncan
reply other threads:[~2024-02-07 23:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=EE0EC088-7F99-4FC5-AF54-E959644CEBA5@gmail.com \
--to=leeman.duncan@gmail.com \
--cc=stgt@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).