Hi Kevin,

We are open to scope what would be needed to move to more supported alternatives, for example: https://pypi.org/project/cryptography/

If you have any specific idea, please submit it. As far as I can see now, there is not a specific reason to stick with the old pycrypto module.

Thanks, Antonio

-----Original Message----- From: TF-M tf-m-bounces@lists.trustedfirmware.org On Behalf Of Kevin Townsend via TF-M Sent: 31 July 2019 15:28 To: Thomas Törnblom via TF-M tf-m@lists.trustedfirmware.org Subject: [TF-M] Outdated pycrypto dependency in BL2's imgtool.py

Hi,

As part of an effort to enable automatic builds of TF-M in Zephyr, I've been trying to get the TF-M + Zephyr S/NS images building and passing on Zephyr's CI system.

The only missing requirements for building TF-M in a clean Zephyr SDK 0.10.1 based environment is the pycrypto module, which is used in the imgtool.py utility, specifically:

https://git.trustedfirmware.org/trusted-firmware-m.git/tree/bl2/ext/mcuboot/...

My concern is that this module is no longer actively maintained (last release was 2013!), and it seems like a poor decision to rely on something that isn't actively maintained when more recent alternative are available.

Is there a specific reason to keep this module in the script in favour of something more modern?

Best regards, Kevin -- TF-M mailing list TF-M@lists.trustedfirmware.org https://lists.trustedfirmware.org/mailman/listinfo/tf-m IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.