This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/iot-wg@ripe.net/
[iot-wg] algorithm agility for IoT
- Previous message (by thread): [iot-wg] algorithm agility for IoT
- Next message (by thread): [iot-wg] algorithm agility for IoT
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jim Reid
jim at rfc1035.com
Mon Jan 21 14:31:02 CET 2019
> On 21 Jan 2019, at 13:22, Marco Hogewoning <marcoh at ripe.net> wrote: > > Agility as you propose doesn’t rule out hardware solutions, but they are probably harder to modify on-the-go and less agile as an entirely software based solution. Thanks for that clarification Marco. For the avoidance of doubt, I was *NOT* talking about hardware when I mentioned "hard-wired crypto”. Though the term could include that. Crypto done in software would be hard wired if that software couldn’t be changed. For instance if it was burnt into ROM or the vendor couldn’t be bothered to provide some way for the software to be updated or reconfigured whenever the crypto landscape moved.
- Previous message (by thread): [iot-wg] algorithm agility for IoT
- Next message (by thread): [iot-wg] algorithm agility for IoT
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ iot-wg Archives ]