HLS ECDSA Authorization

4 posts / 0 new
Last post
VitalyP
HLS ECDSA Authorization

Hello,

For HLS ECDSA Authorization defined, that CtoS string (transferred in CallingAuthenticationValue of AARQ) have to be 32..64 bytes long.
While Gurux send only 16 bytes.

1: 00 01 00 01 00 01 00 4C 60 4A A1 09 06 07 60 85 74 05 08 01 01 A6 0A 04 08 45 4D 52 07 00 00 00 02 8A 02 07 80 8B 07 60 85 74 05 08 02 07 AC 12 80 10 51 1E 62 66 00 20 00 16 79 74 45 0D 0B 14 03 29 BE 10 04 0E 01 00 00 00 06 5F 1F 04 00 60 00 1D 01 00
<WRAPPER len="54" >
<TargetAddress Value="1" />
<SourceAddress Value="1" />
<PDU>
<AssociationRequest>
<ApplicationContextName Value="LN" />
<CallingAPTitle Value="454D520700000002" />
<SenderACSERequirements Value="1" />
<MechanismName Value="HighECDSA" />
<CallingAuthentication Value="511E6266002000167974450D0B140329" />
<InitiateRequest>
<ProposedDlmsVersionNumber Value="06" />
<ProposedConformance>
<ConformanceBit Name="GeneralProtection" />
<ConformanceBit Name="GeneralBlockTransfer" />
<ConformanceBit Name="Get" />
<ConformanceBit Name="Set" />
<ConformanceBit Name="SelectiveAccess" />
<ConformanceBit Name="Action" />
</ProposedConformance>
<ProposedMaxPduSize Value="0100" />
</InitiateRequest>
</AssociationRequest>
</PDU>
</WRAPPER>

regards,
Vitaly

Kurumi
Kurumi's picture

Hi Vitaly,

You are right about this. This is broken and ECDSA authentication is not working at the moment. I'll add this to the worklist. The next release is next week.

BR,
Mikko

________________________________________
Mikko Kurunsaari
Gurux Ltd
http://www.gurux.fi

VitalyP

Hi, Mikko

The new revision still send only 16 bytes for CallingAuthenticationValue in HLS ECDSA Authorization.

regards,
Vitaly

Kurumi
Kurumi's picture

Hi,

You are right. That is still on test and it's coming in part of the next release.

BR,
Mikko

________________________________________
Mikko Kurunsaari
Gurux Ltd
http://www.gurux.fi