mhoppes wrote:We are using private IPs and access lists. A Kernel panic would only happen if someone is attempting to hijack code that is improperly written or not closing something (e.g. memory leak). Otherwise it should be handling it gracefully, shouldn't it?
Keep in mind we use Linux, and other add in services which we do not write such as what handles our SSH, HTTP, SNMP, and so on. So those packages we have little to do with their development other than if we find a hole we report it to them to fix. Pretty much same as all embedded devices on the market.
Also I will be the first to admit that we are not "perfect" and we make many mistakes but please inform we of some software package that you are aware of that is perfect and was never exposed to hackers or memory leaks, or other bugs?
MicroSoft = NO - many BILLION dollar company with countless programmers
Cisco = NO - many BILLION dollar company with countless programmers
UBNT = NO - Billion dollar company with many many programmers
Netgear = NO
The list goes on and on and on and on, hell recently medical devices like pacemakers have been hacked, power grids, voting system, banks, air ports, and recently many social media platforms. Again much bigger companies with many more programmers and BILLION dollar budgets and even they are not perfect.
Again I would suggest providing access to the device to our staff.
Maybe your statement was not meant to be a jab but I did read it that way.
Maybe we do have a hack-able vulnerability, who knows, but it happens but if it does we need to find it first.
Or maybe it is something specific to you network but still needs to be addressed and we simply can not replicate it, again who know but you are not seeing this on all your segments or all your switches, I think just this one segment?
