3 ms·
Example off the top of my head: you have devices in the field which have not received an update since they were purchased 10 years ago. A common crypto algorit
by leggomylibro 8y ago
Example off the top of my head: you have devices in the field which have not received an update since they were purchased 10 years ago.
A common crypto algorithm gets broken to a degree where it is phased out of use industry-wide to prevent leaking user data, MitM attacks, etc.
But once you flip the switch on that old crypto algorithm, your old devices can no longer be updated without a complex manual process (good luck getting the group of users who have never updated to do that,) and the devices will stop working with any secure online connectivity the users have been used to having (purchasing, downloading, etc.)
You have been trying to let users choose how they use their devices, but now they are upset that you broke their product, which they purchased in a working state. What do you do? This is a very small number of people and the years of accommodating them is getting very expensive, but you want to do right by them.
- lazyjones 8y ago> What do you do? Offer the old crypto algorithms as a configuration option, or offer 2 versions of the firmware (standard vs. compatibility). Can't be prohibitively expensive, but isn't necessary when it's in the clear interest of customers not to use these old algorithms.
- leggomylibro 8y agoThe issue is that you cannot forcibly update devices; not all users accept them, often because of the concerns which were being discussed in this thread. But if you continue to 'support' the legacy algorithm to keep things working for those users, you also open them up to attack and they will surely complain if someone steals their information from "your service".