Thanks Shyam.
So in this case target replies with NONE as it has choosen NONE
between CHAP and NONE.
Here initiator is asking for authentication and Target is not ready
for authentication. In this scenario authentication should fail.
Right?
To make authentication strict, initiator should only pas
Nandkumar wrote:
> Here is what initiator and taget passes to each other while iscsi
negotiation phase. Assuming CHAP is only enabled on initiator and not on
target.
> 1) Initiator pass "CHAP,NONE" as Authentication parameter.
> 2) Target replies with "NONE".
> 3) Both will settle on "NONE" as Auth
HI,
During unidirectional CHAP configuration on RHEL5.2, I found following
odd behaviour.
"If initiator CHAP is enabled and Target CHAP is _not_ enabled ,
Authentication Passes".
I looked at code, trace and RFC and here is my observation.
Here is what initiator and taget passes to each other w
