Software locks

Revision as of 17:10, 21 June 2025 by JP (talk | contribs) (Improve summary)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Article Status Notice: This Article is a stub


This article is underdeveloped, and needs additional work to meet the wiki's Content Guidelines and be in line with our Mission Statement for comprehensive coverage of consumer protection issues. Learn more ▼

Software locks are security measures used to control access and features in consumer electronic hardware and software. [1][2] Software locks are not considered bad practice and are necessary for basic cybersecurity and operation of most hardware, though they can be abused.

Noteworthy bad practice examples edit

Anti Interoperability edit

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 edit

Mobile phones edit

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 edit

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 edit

-wip

Server connectivity reliance edit

Also see: Subscription service, Digital rights management

-wip

Further reading / also see edit

DRM (digital right managment)

Proprietary Software

Walled garden / Software Ecosystem

Bootloader unlocking

Proprietary firmware