You usually see these on fields that are co-owned or need to be accessed by several municipalities. Everybody gets their own key but can still have access to the area whenever needed.
Duplicating the key removes some accountability. With this set up you can revoke access to only one person, while leaving the access in place for everyone else. If you had a single lock with six copies then a bad actor getting a copy means you’d have to replace everyone else’s keys
This also means one person can’t take their lock off and replace it with another, and therefore lock out everyone else
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programmerhumor@lemmy.ml
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
Posts must be relevant to programming, programmers, or computer science.
No NSFW content.
Jokes must be in good taste. No hate speech, bigotry, etc.
You usually see these on fields that are co-owned or need to be accessed by several municipalities. Everybody gets their own key but can still have access to the area whenever needed.
Wouldn’t just duplicating the key achieve the same purpose or am I missing something?
Duplicating the key removes some accountability. With this set up you can revoke access to only one person, while leaving the access in place for everyone else. If you had a single lock with six copies then a bad actor getting a copy means you’d have to replace everyone else’s keys
This also means one person can’t take their lock off and replace it with another, and therefore lock out everyone else