Attention is currently required from: daniel, dexter, fixeria.
1 comment:
File library/PyHSS_REST_Functions.ttcn:
Patch Set #2, Line 43: private function f_pyhss_algo(template (omit) charstring algo2g := omit,
In that case, the variable in line 84 would always be set to the algo2g value?
yes
When I look at f_vty_subscr_create() that sets the algorithm for both 2g and 3g, but I don't know how/if that works in pyhss.
In PyHSS, there is [only one algo field](https://github.com/nickvsnetworking/pyhss/blob/572af5012b41f6140a2e01d64984dbf4c37a8444/lib/database.py#L80), with the following description:
2G Authentication Algorithm (1 = Comp128v1, 2 = Comp128v2, 3 = Comp128v3, All Other= 3G auth with 2g keys from 3G Milenage)
So as I understand it, we can't properly map the "both algo2g and algo 3g are != omit" case to PyHSS. This doesn't affect the outcome of the testcases, so at least initially this should be good enough IMHO.
To view, visit change 41227. To unsubscribe, or for help writing mail filters, visit settings.