View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0004452Compliance Test Tool (CTT) Unified Architecture5 - General Problempublic2018-11-12 10:382019-07-25 15:03
ReporterBernd Edlinger Assigned ToAlexander Allmendinger  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionfixed 
PlatformPCOSWindowsOS Version8.1
Product Version1.03.341.383 
Target Version1.03Fixed in Version1.03.341.383 
Summary0004452: Most security profiles do not work
Description

Those seem to send an invalid ApplicationSignature:

Base128Rsa15
Base256
Aes256Sha256RsaPss

only Base256Sha256 and Aes128Sha256RsaOaep do work.

This applies to the Settings dialog and all scripts.

The difference is already visible in the Algorithm URI:

Base128Rsa15:
expected: 'http://www.w3.org/2000/09/xmldsig#rsa-sha1'
received: 'http://www.w3.org/2001/04/xmldsig-more#rsa-sha256'

Base256:
expected: 'http://www.w3.org/2000/09/xmldsig#rsa-sha1'
received: 'http://www.w3.org/2001/04/xmldsig-more#rsa-sha256'

Aes256Sha256RsaPss:
expected: 'http://opcfoundation.org/UA/security/rsa-pss-sha2-256'
received: 'http://www.w3.org/2001/04/xmldsig-more#rsa-sha256'

The signature itself was successfully validated, though.

TagsNo tags attached.
Files Affected

Relationships

related to 0004543 assignedPaul Hunkar CTT UA Test Case Create TestCase and TestScript for using not requested AlgorithmUri 

Activities

Paul Hunkar

2018-11-12 15:48

administrator   ~0009580

Need to add a test case to make sure server does not accept the wrong algorithm. they are specified in the policy and must be adhered to.

Alexander Allmendinger

2018-11-14 15:11

developer   ~0009591

Has been fixed to use the correct Algorithm URI for all cases.

New Test case needs to be created to verify servers do decline connections with not correct uris because most of the testing servers were accepting the connection.

Paul Hunkar

2019-07-25 15:03

administrator   ~0010600

reviewed in CMP call

Issue History

Date Modified Username Field Change
2018-11-12 10:38 Bernd Edlinger New Issue
2018-11-12 15:44 Paul Hunkar Assigned To => Alexander Allmendinger
2018-11-12 15:44 Paul Hunkar Status new => assigned
2018-11-12 15:48 Paul Hunkar Note Added: 0009580
2018-11-14 15:11 Alexander Allmendinger Note Added: 0009591
2018-11-14 15:11 Alexander Allmendinger Status assigned => resolved
2018-11-14 15:11 Alexander Allmendinger Fixed in Version => 1.03.341.383
2018-11-14 15:11 Alexander Allmendinger Resolution open => fixed
2018-12-19 11:58 Alexander Allmendinger Relationship added related to 0004543
2019-01-28 14:14 Paul Hunkar Category General Problem => 4 - General Problem
2019-01-28 14:15 Paul Hunkar Category 4 - General Problem => 5 - General Problem
2019-07-25 15:03 Paul Hunkar Target Version => 1.03
2019-07-25 15:03 Paul Hunkar Status resolved => closed
2019-07-25 15:03 Paul Hunkar Note Added: 0010600