2 ms·
> certificates need to expire while the original person deploying the system is still working on it. This seems really arbitrary. Elaborate?
by scrollaway 8y ago
> certificates need to expire while the original person deploying the system is still working on it.
This seems really arbitrary. Elaborate?
- geofft 8y agoFirst, it's a lot more robust for the system to be initially designed to support certificate renewal than to figure it out later, usually because "later" means "after it expires." That might either be going through the exercise of renewing certificates by hand or setting up automation. If the system is already in maintenance mode / "legacy", and you don't have a process for renewing certificates, you're at higher danger of missing it. Also, the person designing the system is evaluated on it working. If it breaks while it's on their watch, it counts against them; if it breaks while on someone else's watch, standard performance review practices are generally unreliable at making it count against them even if it really ought to. Therefore, if you assume standard performance review practices (which is the right way to model incentives for present-day developers/deployers working for for-profit companies, and because of the massive influence of for-profit companies, not a wrong way to model social incentives for everyone else), you want to incentivize them to make renewal part of the system, again either via automation or documentation.