3 ms·
Sure. Disable all the optional features you aren't using, and hope there's no unpublished security errors in the site itself or the stack. Same thing you'd do o
by toast0 3y ago
Sure. Disable all the optional features you aren't using, and hope there's no unpublished security errors in the site itself or the stack. Same thing you'd do on any other language/stack; except something that's formally verified in which case you'd also need to hope the verification model matches the actual environment.
Lack of security updates / process doesn't definitely imply an insecure environment, but it puts the onus for security more clearly on the host. You've got to at least watch all the security updates in newer revisions and consider if they apply, but there's also things that may have gotten fixed or at least changed without realizing the old version was insecure.