Function signature

An openOBD function can be called from another openOBD function. Before the function can be published on the Jifeline infrastructure it needs to be assigned an unique identifier. Along with this identifier a signature is needed that is used as proof that you are the actual owner of the function.

Below we show example code that can be used to obtain an unique function id an signature from the Jifeline network.

Info

We do not need to execute this, we can use our fresh_signatures.py to retrieve signatures for our functions. We show this to illustrate that the retrieval of a function signature is a one-time operation at the creation of your script.

When you want to test this, copy this to a python file (.py) and use chmod 755 <filename.py> to make it executable. Then, execute it.

#!/bin/env python

from openobd import *

function = OpenOBD().generate_function_signature()

print(f" [+] Generated new function id: {function.id}")
print(f" [+]                 Signature: {function.signature}")

Register your EOBD script

  • Run the ./fresh_signatures.py script.
  • Notice: every time you run the ./fresh_signatures.py script, new id's and signatures will be generated.
  • Copy the id and signature for your EOBD script and make them permanent by copying them into the EOBD script.
  • Run ./overview.py and check that the id and signature of your EOBD script are now fixed every time you run this script.

Registering your scripts with a fixed id and signature is important in case you want to make function calls from your function to other functions.

But first, we will try to get our function on-line on our partner dashboard.

Continue to hosting