self-destruct sequence for collocated program on ram drive?
Building on this answer http://security.stackexchange.com/a/36532/24408
and assuming the original assumptions in that question and also that I cannot be physically connected to the system at all times, I cannot keep a separate system that stores encryption keys online at all times, the main system is collocated, the main system has a dedicated IP, and the collocation operators are not trusted to enter the system at all, should a self-destruct process be written into the websocket++ server that dismounts the ram drive where the server excecutable & encryption keys are stored & terminates the executable when some condition of connectivity to the internet fails?
If so, how can it be done (what is that condition)?
Building on this answer http://security.stackexchange.com/a/36532/24408
and assuming the original assumptions in that question and also that I cannot be physically connected to the system at all times, I cannot keep a separate system that stores encryption keys online at all times, the main system is collocated, the main system has a dedicated IP, and the collocation operators are not trusted to enter the system at all, should a self-destruct process be written into the websocket++ server that dismounts the ram drive where the server excecutable & encryption keys are stored & terminates the executable when some condition of connectivity to the internet fails?
If so, how can it be done (what is that condition)?
No comments:
Post a Comment