For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Zdenda's avatar
Zdenda
Icon for Cirrus rankCirrus
Jul 26, 2019

ASM - Rest API - sig-set ID

Hi, signature-set IDs used in iControl Rest use those IDs: (either ID in a link of sig-set like: "/asm/signature-sets/XFklAdYbdN8MUWbi74WC3g", or ID of sig-set already used in policy like "/asm/pol...
ASM Advanced WAF
devops
iControlREST
security
Satoshi_Toyosa1's avatar
Satoshi_Toyosa1
Ret. Employee
Aug 01, 2019

Here's the steps to create the hash from the name of the ASM object.

  1. Create the MD5 digest from the name (yields 128 bits of binary data)
  2. Encode it using base64 (yields 24 characters)
  3. Trim the last two "==".

For example,

# echo -n /Common/sat | openssl dgst -md5 -binary | base64 | cut -c-22
9afAWDUoawpiNnfSfSGtMQ

Obviously, because MD5 is not reversible (one-way), the hashed ID cannot be decoded back to the object name.

See also

Sebastien6's avatar
Sebastien6
Icon for Altostratus rankAltostratus
Aug 02, 2019

Cool thank you. Works fine. Per chance, do you know the way to do it for whitelist=ips?

I know the name is based on a combination of ipAddress/ipMask, as hash change if you change the ipMask.

 

I tried all those without success for 192.168.0.30/255.255.255.255 that should be 2S_b6WCJRsVKz9zgrtxYPA:

 

b'192.168.0.30/255.255.255.255'

b'/192.168.0.30/255.255.255.255'

b'/Common/whitelist-ips/192.168.0.30/255.255.255.255'

b'/Common/whitelist-ips/192.168.0.30/255.255.255.255'

b'/Common/seb-dev-policy1/whitelist-ips/192.168.0.30/255.255.255.255'

b'/Common/seb-dev-policy1'

b'/whitelist-ips/192.168.0.30/255.255.255.255'

 

tried also all of them using 192.168.0.30_255.255.255.255 with no success.