The upgarde of CCF App

[Silence-zyx]

I learn that updating-code-verison shows a way to update the app.
However when I type command:

sudo ./oesign dump -e ~/CCF/ccf-1.0.6/CCF-ccf-1.0.6/samples/apps/logging/build/liblogging.virtual.so

it returns

2021-07-26T16:22:55+0800.815387Z [(H)ERROR] tid(0x7f372e1d5c00) | Unsupported elf relocation type 16
 (oe_result_t=OE_UNSUPPORTED_ENCLAVE_IMAGE) [/source/openenclave/host/sgx/elf.c:_elf64_load_relocations:1920]
2021-07-26T16:22:55+0800.815537Z [(H)ERROR] tid(0x7f372e1d5c00) | :OE_UNSUPPORTED_ENCLAVE_IMAGE [/source/openenclave/host/sgx/elf.c:elf64_load_relocations:1957]
2021-07-26T16:22:55+0800.815559Z [(H)ERROR] tid(0x7f372e1d5c00) | :OE_INVALID_IMAGE [/source/openenclave/host/sgx/loadelf.c:_load_elf_image:447]
2021-07-26T16:22:55+0800.825607Z [(H)ERROR] tid(0x7f372e1d5c00) | :OE_INVALID_IMAGE [/source/openenclave/host/sgx/loadelf.c:_load_primary_image:1426]
2021-07-26T16:22:55+0800.825712Z [(H)ERROR] tid(0x7f372e1d5c00) | :OE_INVALID_IMAGE [/source/openenclave/host/sgx/loadelf.c:oe_load_elf_enclave_image:1445]
2021-07-26T16:22:55+0800.825732Z [(H)ERROR] tid(0x7f372e1d5c00) | :OE_INVALID_IMAGE [/source/openenclave/host/sgx/load.c:oe_load_enclave_image:63]
2021-07-26T16:22:55+0800.825745Z [(H)ERROR] tid(0x7f372e1d5c00) | :OE_INVALID_IMAGE [/source/openenclave/tools/oesign/oeinfo.c:oe_read_oeinfo_sgx:27]
./oesign ERROR: Failed to load SGX enclave properties from .oeinfo section
./oesign ERROR: Cannot find entry point symbol
=== SGX Enclave Properties:
product_id=0
security_version=0
debug=0
xfrm=0000000000000000
num_heap_pages=0
num_stack_pages=0
num_tcs=0
mrenclave=0000000000000000000000000000000000000000000000000000000000000000
mrsigner=0000000000000000000000000000000000000000000000000000000000000000
signature=000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
./oesign encountered 2 errors

And I changed the enclave_lib file to liblogging.enclave.so, it returns:

=== Entry point: 
name=_start
address=0x0000000011ae17

=== SGX Enclave Properties:
product_id=65535
security_version=65535
debug=0
xfrm=0000000000000000
num_heap_pages=65535
num_stack_pages=65535
num_tcs=65535
mrenclave=0000000000000000000000000000000000000000000000000000000000000000
mrsigner=0000000000000000000000000000000000000000000000000000000000000000
signature=000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

I wonder that:

1. If this method supports virtual mode (xxxx_virtual.so).
2. The SGX Enclave Properties of the command for the liblogging.enclave.so is very strange, is that right?

[Silence-zyx]

By the way, if the debug method supports virtual mode?

[eddyashton]

Hi @Silence-zyx. This upgrade process isn't intended to be used for .virtual enclaves, as they are not intended to be used in production. This governance operation would change the set of accepted mrenclaves, but these are only checked by the nodes if they are SGX enclaves. If you are running a test virtual network (using the .virtual.so files), then they do not check any CodeID of joining nodes and (I believe) any node should be able to join the network - you wouldn't need to do code upgrade as described, your new nodes can simply join the existing network.

oesign will only work on signed enclave images, so you need to use liblogging.enclave.so.signed. liblogging.enclave.so is ready to be signed, but is not yet processed by oesign and is not loadable by cchost/OE.

[Silence-zyx]

Got it, thank you!

[Silence-zyx]

@eddyashton Sir, is there a debug method for JS script in CCF network?

[eddyashton]

@Silence-zyx Its not possible to attach a debugger to the JS runtime executing inside a CCF node, even in virtual mode. We recommend using console.log to dump debug traces from your script during development, that will be visible in the node's output logs.

[Silence-zyx]

Alright, thank you!