FUJ00176547 - Peak Incident Management System - Call log - PC0189343 - Quality Centre Raised Incidents/Defects - SVIC9 - Audit - Gaps in Message Sequence are not reported when Crypto errors are reported

Evidence on official site

FUJ00176547
FUJ00176547

Peak Incident Management System

Call Reference PC0189343
Release Targeted At -- HNG-X 00.14.16.xx

Deleted User -- QC Interface
AUDIT_EXTRACT SVR_INT14_V040-V039

Call Logger
Top Ref

Call Type Quality Centre Raised Incidents/Defects Priority B -- Medium Impact - Priority 3
Contact Deleted Contact Call Status Closed -- S/W Fix Available to Call Logger
Target Date 26/10/2009 Effort (Man Days) 0
Summary SVIC9 - Audit - Gaps in Message Sequence are not reported when Crypto errors are reported
All References Type Value

QC Severity 3 - High

QC_DEFECTID 12174-hng_x_hng x release_1_db.

QC Defect No 12174

QFP Review COMPLETE

Product Baseline AUDIT_EXTRACT_SVR_INTI4_V040-V039
Progress Narrative : :

fbate:13-Oct-2009 18:05:10 User:John Rogers

CALL PC0189343 opened

Details entered are:~

Summary:SVIC9 - Audit - Gaps in Message Sequence are not
call Type:

call Priority:

ffarget Release:SVaI Cycle 9

lkouted to:EDSC - Unassigned_

reported when Crypto errors are reported

Ledueteseuteeseutssets Quality Centre Bug Report *##+s#+eeeeeeeeeeues

Bug Reference: 12174-hng_x_hng_x release 1 db.
fest Date: Oct 13 2009 12:00AM
test User: rogers}
: 3 = High
: Path201
None
: Infrastructure
product Version: N/A
summary: SVIC9 - Audit - Gaps in Message Sequence are not reported when Crypto errors are reported
incident Description:

hen an ARQ has been run on a FAD in which there is both a Gap in the FAD Data Message Sequence and an unrelated Crypto error
then the Crypto error is reported but the "Size of the Message Gap" is reported as NONE.

[the problem was originally noticed in normal running, and was then forced to confirm the theory (ARQ OTH3747W) .

[fhe attachment Gap There is a

sen print which shows the Message Gap (Node 1 : 103980 to 103984).

lA Crypto error was then introduced into message 103975.
fhe attached Gap Abs Rep is a screen print that shows the Crypto Error being reported.

[fhe attachement Gap Not There is a screen print that shows the "Size of Gaps" reported as NONE but two gaps in the message
sequence :-

(Node 1 : 103975 to 103979)

(Node 1 : 103980 to 103984)

comments:

ohn Rogers <rogersj>, 13/10/2009 15:06:06:

impact:

though the circumstances that cause the error may not occur very frequently I believe that it is vital from the Audit point of
dew that these reports accurately report this type of information.

Audit Dev need to confirm but suggest that this needs to be Reset 10

John Rogers <rogersj>, 13/10/2009 15:12:19:
Please route to Audit Dev

Jbate:13-Oct-2009 18:05:12 User:John Rogers
evidence imported from QC ~ BUG 12174 0C12174.zip

[Date:14-Oct-2009 06:32:54 Uscr:Darran Avenell
[fhe Call record has been assigned to the Team Member:

Darran Avenell

[Date:14-Oct-2009 10:21:39 User:Lionel Higman

FUJ00176547
FUJ00176547

Reference Adda

7 QFE Review COMPLETE

jDate:14-Oct-2009 13:28:14 Uscr:Darran Avenell
lthe Call record has been transferred to the team: Audit-Dev

jbate:16-Oct-2009 10:31:04 User:Alan Holmes
[the Call record has been assigned to the Team Member: Gerald Barnes

bate: 16-Oct-2009 10:32:17 User:Alan Holmes
[fhe call Target Release has been moved to Proposed For -~ HNG-X 00.14.16.xx

jbate:16-Oct-2009 1
[fhe call Target Release has been moved t

1:01 User:Bionel Higman
‘argeted At -- HNG-X 00.14.16.xx

JDate:19-Oct-2009 10:30:42 User:Steve Evans
the Call record has been assigned to the Team Member:

lbate:19-Oct-2009 1.
[Start of Response]

Reset to 14 at QFP2

[End of Response]

Response code to call type Q as Category 40 -- Pending -- Incident Under Investigation

6:26 User:Lionel Higman

JDate:20-Oct-2009 17:13:41 User:Steve Evans
ftarget Date/Time updated: new value is 26/10/2009 18:05

(Start of Response]

jeeds to be in RESET 2

{End of Response]

lkesponse code to call type Q as Category 41 -- Pending -- Product Error Diagnosed

Date:20-Oct-2009 1
[Start of Response]

IRAG

[End of Response]

kesponse code to call type Q as Category 45 -- Pending -- QFP RAG Status Green

3:53 User:Steve Evans

[Date:21-Oct-2009 1!
evidence Added - H.

Jbate:21-Oct=2009 11
Isvidence Added - 1.

Date:21-Oct-2009 1
{Start of Response]

Fixed by version 1.0.0.3 of QueryDLL.dll. A handover note and test plan are attached as evidence.
[End of Response]

lkesponse code to call type Q as Category 45 -- Pending -- QFP RAG Status Green

tours spent since call received: 15 hours

1:36 Uscr:Gerald Barnes

jbate:21-Oct-2009 18:01:47 Uscr:Gerald Barnes
[the Call record has been transferred to the team: Audit-Rel

Ibate:22-Oct-2009 0:
{Start of Response]

issue addressed by baseline AUDIT EXTRACT SVR_INT14_v040-V039

[End of Response}

Iesponse code to call type Q as Category 48 -- Pending -- Fix Released to PIT

9:25 User:Phil Budd

bate: 22-Oct-2009 09:39:34 User: Phil Budd
lkeference Added: Product Baseline AUDIT EXTRACT SVR_INT14_v040-v039

JDate:22-Oct-2009 09:39:35 User:Phil Budd
TOP Reference set to: Product Baseline AUDIT_EXTRACT_SVR_INT14_v040-Vv039

JDat¢:22-Oct-2009 09:40:12 User:Phil Budd
[fhe Call record has been transferred to the team: Dev-Int-Rel

FUJ00176547
FUJ00176547

Date: 27-Oct-2009 01
[Start of Response]

Released to SVI via manual release

[End of Response]

Response code to call type Q as Category 60 —- Final -
Routing to Call Logger following Final Progress update.
Defect cause updated to 14 -- Development ~ Code

4:23 User:Vijesh Pandya

S/W Fix Released to Call Logger

Date: 27-Oct-2009 12:05:08 Uscr:John Rogers
comments Update:

rim Canniffe <canniffet>, 27/10/2009 11:50:1

IRRELEVANT jand retested. Baseline "AUDIT EXTRACT SVR_INT14 D040-D039" installed and log file checked. "QueryDLL.dll"

SYSH7T70.0.3. present.
laRQ:OTH3809W - HNGX
laRQ:OTH3808W - Horizon

luNGX Message Gaps have been tested on the basis of:
h) Single message gap
2) Range of messages

liorizon messages checked for:
h) Single CRC message change
2) Range of CRC messages changed

[the following components of the message signature have been checked:
h) BAL-Certificate

2) Authorisation Signature

Ib) Generic DTO Request content

4) Public Key

Note: Cryptographic errors will result in the failure of the integrity of the ARQ data and as such will not be used.

the following observations were made:
) Changes to BAL Certificate results in "Termination" of the abstraction and the whole file contents are ignored for the
jsubsequent processing of the data.

2) Changes to all other components of the message signature results in the specific "Session
lata is processed as expected. Message Gaps are reported if applicable.

data being ignored and all other

For both points above the "View Abstraction Errors" tab is displayed and reports the cryptographic errors accordingly and any
lessage Gaps are reported.

K to CLOSE.

Date: 28-Oct-2009 20:40:06 Uscr:dohn Rogers
Incident closure received from Quality Centre
comments Updat

Ihris Maving <mavinge>, 27/10/2009 12:53:52:
closing as requested.

JDate: 28-Oct-2009 20:40:06 User:John Rogers
CALL PC0189343 closed: Category 60 Type 0

Root Cause Development - Code
Logger Deleted User -- QC Interface
Subject Product : QC Defects -- Infrastructure (version: 1)

Assignee Deleted User -- QC Interface
Last Progress 28-Oct-2009 20:40 -- John Rogers