[Damien]

Dear Chris,

Thank again. It works perfectly. In MUtil, we have to set the parameter during load of ALU.
#pragma attribute(“access_list”,”1003″) in the program was not enough.

I have not tried again my student’s program when he got firewall violation.

BTW, the miDebuggingEnable() should not be called.

Best regards,
Damien

[Damien]

Thank you Chris. I have connected as you suggest the Vcc (PIN 11) and one GND (PIN 32) and it was working.

Great.

[Damien]

Hi Chris,

Thank you but how I can interpret the values of fields?
I know that it is an SLE78 IC. I know the rom_ic_details means 0x84 0x53 M5-P22
But where I can get other data? I guess that 0xf5 of ic_manufacturer_id means Infineon.

However I do not know which chip it is from the SLE78 series since in link you give there is

RF interface (SLE78CLUFX5000PHM only)

. So what chip is it?


hterm -serial COM39 -multos
MULTOS data
rom_ic_details 0x84 0x53
ic_manufacturer_id 0xf5
multos_implementor_id 0x02
mcd_id.Mism_id 0xff 0xff
mcd_id.icc_serial_number 0xff 0xff 0xff 0xff
msm_mcd_permissions.mcd_issuer_product_id 0x00
msm_mcd_permissions.mcd_issuer_id 0x00 0x00 0x00 0x00
msm_mcd_permissions.set_msm_controls_data_date 0x00
msm_mcd_permissions.mcd_number 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
msm_mcd_permissions.RFU5 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
0x00 0x00 0x00 0x00 0x01
msm_mcd_permissions.RFU2 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
msm_mcd_permissions.RFU6 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
0x00 0x00 0x00 0x00 0x01
msm_mcd_permissions.RFU4 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
max_dynamic_size 0x26ac
max_public_size 0xc80
max_dir_file_record_size 0xff
max_fci_record_size 0xff
max_atr_hb_record_size 0x0f
max_atr_file_record_size 0x20
multos_pk_certificate_length 0xc8
security_level 0x5a
certification_method_id 0xf2 0x00
app_signature_method_id 0x01 0x01
encipherment_descriptor 0x00 0x01
hash_method_id 0xf2 0x00



hterm -serial COM39 -manufacturer
Manufacturer data
ic_manufacturer_id 0xf5
ic_type 0x00
rom_ic_details 0x84 0x53
mcd_id.Mism_id 0xff 0xff
mcd_id.icc_serial_number 0xff 0xff 0xff 0xff
initialisation date 6699 60 77 94 111 0
processor_page_size 0x20
max_tx_tpdu_size 255 max_rx_tpd_size 256



hterm -serial COM39 -apdu 80100A0006
[ 80100A0006 ] => [ 00 02 00 02 00 14 90 00 ]

I know this is the build number of the operating system.

Thank you.
Damien

[Damien]

Dear Chris,

You are right for the smaller ones.

You are also right for M511, Curve383187 and M383 since they were Montgomery curves.

I have tried and I have succeeded with secp521r1 …

It is a pity since the safe curves are not on Short Weierstrass curve https://safecurves.cr.yp.to/

Best regards,
Damien

[Damien]

Dear all,

I also failed to use curves under whose parameter are smaller than 192 bits like secp160r1, secp160k1 (it might be an issue for those two of N length) or secp128r1 or secp112r1…

Is this a known limitation?

[Author]

Posts