Software locks

Revision as of 03:11, 27 January 2025 by JamesTDG (talk | contribs) (Small fixes, mostly formatting and grammar)

Software locks are security measures used to control access & features in consumer electronic hardware & software. [1] [2] software locks by definition are not a bad practice and are very necessary for basic cyber security and operation of most hardware.

Noteworthy bad practice examples

Anti Interoperability

Also see: Proprietary protocols, Anti Interoperability, Hardware Anti Interoperability[3]

wip stub example you can't use our competitors Bluetooth headset with our XYZ operating system because we invented a our own new proprietary XYZ Bluetooth audio codec and that product doesn't support it.

real example apple mfi certifications on charging and data transfer accessories

apple's history of anti-Interoperability

Account-required products

Mobile phones

ref Small preamble focused on how mobile phones require an account in order to be used, reference Google Pixels and specific Android devices requiring a Google account, and iPhones needing an Apple account.

in appliances

hvac app activation of furnace control boards (also an example of Forced app download (editors note hard to find credible ref this is a thing with ruud furnace control boards) )

Binding hardware features to non-transferable user accounts / activation & licensing locks

-wip

Server connectivity reliance

Also see: Subscription service, Digital rights management

-wip

Further reading / also see

DRM (digital right managment)

Proprietary Software

Walled garden / Software Ecosystem

Bootloader unlocking

Proprietary firmware