DES3 default encryption differs between SilkPerf and SCTM ?

[Phill1]

Hi there,

I recently setup a test using a SilkPerformer project that has a variety of predefined parameters (baseline data and custom parameters used with the script logic (bdf)).

Of these parameters one is a password parameter (ie 'type' password). When inspecting the raw parameter data as described in the .ltp project file, I see this param type is encrypted using DES3

If I deploy with these parameters as set in the .ltp file, all is OK..

If however I modify the password parameter in SCTM (ie as done with test or execution config/containers etc) the test breaks.. (note that I'm presenting exactly the same password chars as set in Silk Perf).

Upon further inspection (ie the .ltp as fetched to the execution server), I see that the encrypted data is no longer valid (ie the value and default differ).

Clearly the DES3 treatment applied to the parameter in SCTM differs from that of Silk Perf.

Is this a bug, or is there an SCTM DES3 config I'm unaware of ?

Thanks.

[Florian Guenther]

Hi,

could you please contact support for better analyzing this problem?

There is no special DES3 configuration in Silk Central.

Thanks,

Florian

[Phill1]

Will do, thanks 🙂