Software locks: Difference between revisions
m Small fixes, mostly formatting and grammar |
m →Noteworthy bad practice examples: fixed red links |
||
| (3 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
{{StubNotice}} | |||
Software locks are security measures used to control access and features in consumer electronic hardware and software. <ref>https://en.wikipedia.org/wiki/Lock_(computer_science)</ref><ref>https://en.wikipedia.org/wiki/Comparison_of_open-source_and_closed-source_software</ref> Software locks are not considered bad practice and are necessary for basic cybersecurity and operation of most hardware, though they can be abused. | |||
=== Anti Interoperability === | ==Noteworthy bad practice examples== | ||
Also see: [[wikipedia:Proprietary_protoco|Proprietary protocols]] | |||
===Anti Interoperability=== | |||
Also see: [[wikipedia:Proprietary_protoco|Proprietary protocols]] | |||
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. | 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. | ||
| Line 12: | Line 13: | ||
apple's history of anti-Interoperability | apple's history of anti-Interoperability | ||
=== Account-required products === | ===Account-required products=== | ||
=====Mobile phones===== | =====Mobile phones===== | ||
| Line 23: | Line 24: | ||
-wip | -wip | ||
=== Server connectivity reliance === | ===Server connectivity reliance=== | ||
Also see: [[Subscription service]], [[Digital rights management]] | Also see: [[Subscription service]], [[Digital rights management]] | ||
-wip | -wip | ||
Latest revision as of 07:10, 2 September 2025
❗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 | edit source]
Anti Interoperability[edit | edit source]
Also see: Proprietary protocols
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 | edit source]
Mobile phones[edit | edit source]
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 | edit source]
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 | edit source]
-wip
Server connectivity reliance[edit | edit source]
Also see: Subscription service, Digital rights management
-wip
Further reading / also see[edit | edit source]
Walled garden / Software Ecosystem