82,891
edits
Enforcing security: Difference between revisions
no edit summary
Amwelladmin (talk | contribs) No edit summary |
Amwelladmin (talk | contribs) No edit summary |
||
| Line 2: | Line 2: | ||
In the world of repack, this is for the counterintuitive reason that ''it really doesn’t matter''. One does not enforce security in a repack. To do so is to have admit you have failed in your one job. | In the world of repack, this is for the counterintuitive reason that ''it really doesn’t matter''. One does not enforce security in a repack. To do so is to have admit you have failed in your one job. | ||
====Why it’s best not to be giddy about enforcing security in a repack==== | |||
{{limited value of security in repack}} | {{limited value of security in repack}} | ||
{{sa}} | {{sa}} | ||
*[[Event of default]] | *[[Event of default]] | ||
*[[Repack Anatomy]] | *[[Repack Anatomy]] | ||
*[[Limited recourse]] | |||