Customizing OpenSSL engine to access SE050 over eth/usb

[Widsinka]

Hi,

I'm trying to leverage SE050 from a host to which the SE050 isn't connected over I2C. The SE050 is accessible over I2C at another host, which is accessible across the network. Take for example this configuration: Host1 <-> Host2 <-> SE050, where Host1 and Host2 are connected to the same network, and SE050 is connected to Host2 via I2C.

My goal is to allow for Host1 to set up a TLS connection to an external host by using the certificates and keys stored on SE050. From what i can see this is not to far off from a standard network accessible HSM, but I haven't found anything specific to this use case.

Having banged my head against the wall for a month I'm stuck with no viable solution. I've managed to forward command line calls to openssl and ssscli over ssh to Host2, but this doesn't help as library functions are untouched. My best guess is to edit the OpenSSL engine in the Plug & Trust middleware software so that OpenSSL doesn't access the SE050 directly over I2C, but over I2C via a connection to Host2 - however it isn't done in an hour.

Is there any previous work done here, or does anyone have a different approach in mind?

[Kan_Li · Accepted solution]

Looks like it is an Access Manager use case, the Access Manager runs on Host 2 and clients run on Host 1, and they get connected via some remote protocol. Please kindly refer to simw-top/doc/hostlib/hostLib/accessManager/doc/accessManager.html for details.

Hope that helps,

Have a great day,
Kan

-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!
- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------