Project

General

Profile

Bug #11432

full compatibility for SECURITY-POLICY:ENCODE-DOMAIN-ACCESS-CODE

Added by Constantin Asofiei 3 months ago. Updated 3 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:
reviewer:
production:
No
env_name:
topics:

History

#4 Updated by Constantin Asofiei 3 months ago

In #11097, we've implemented the return value for SECURITY-POLICY:ENCODE-DOMAIN-ACCESS-CODE to be the same as AUDIT-POLICY:ENCRYPT-AUDIT-MAC-KEY. This is not full compatibility as Stefanel mentions in #11097-4:

Stefanel Pezamosca wrote:

Out of curiosity I made an experiment myself.
AUDIT-POLICY:ENCRYPT-AUDIT-MAC-KEY("test").
This output is deterministic; it will always look exactly like this for the same input. 24373c33.

SECURITY-POLICY:ENCODE-DOMAIN-ACCESS-CODE("test")
This output is non-deterministic. Each time you run the command, the string following the prefix will change. Below are three possible outputs for the same input. A base64 encoded string with odeb0:: prefix.
  • Result A: odeb0::N/xwelJdaxLHENAWC2J/eOxmquz5zTxU6YG5Jth0gh2Swxk/35rb9mlAaNUsea
  • Result B: odeb0::A7b9kLmP2qRsTvUwXyZ1N2M3L4K5J6I7H8G9F0E1D2C3B4A5N6M7L8K9J0I
  • Result C: odeb0::9mKj8Ih7Gg6Ff5Ee4Dd3Cc2Bb1Aa0Zz9Yy8Xx7Ww6Vv5Uu4Tt3Ss2Rr1Qq

This task is meant to determine if FWD needs the same level of support, and provide full compatibility if so.

Also available in: Atom PDF