You are very correct. They walked me out with two deputies as escort. And less than a year later, they were no more, gone the way of the dodo bird and Enron.
From: [email protected] [mailto:[email protected]] On Behalf Of Michael B. Smith Sent: Monday, November 27, 2017 12:28 PM To: [email protected] Subject: RE: [NTSysADM] OS in the CPU …and as long as you’ve planned for it, this is a good thing. You don’t have to work those two weeks! Saves a lot of trouble in packing, too. Seriously… if you are in that kind of nasty environment you should get out. It isn’t good for your health. From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of [email protected] <mailto:[email protected]> Sent: Monday, November 27, 2017 11:18 AM To: [email protected] <mailto:[email protected]> Subject: RE: [NTSysADM] OS in the CPU And ten minutes after you’ve given your notice, you’re marched out of the building by two security goons, or the local constabulary with the comment from management, “We’ll pack your things and ship them to you.” From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Kennedy, Jim Sent: Monday, November 27, 2017 8:56 AM To: [email protected] <mailto:[email protected]> Subject: RE: [NTSysADM] OS in the CPU It matters to management when you give your 2 week notice, which is exactly what I would do if they treated me as you described. Any of us that are half way decent can find a new better higher paying gig just by picking up the phone on the drive home. From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of [email protected] <mailto:[email protected]> Sent: Saturday, November 25, 2017 5:23 AM To: [email protected] <mailto:[email protected]> Subject: RE: [NTSysADM] OS in the CPU Since when does that matter to management? We’re all barely evolved pond scum as far as management goes when things are going right. When the environment blows up due to a zero day, or an undiscovered vulnerability and management is looking for retribution, IT people are the first to feel the axe on their necks. From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Melvin Backus Sent: Tuesday, November 21, 2017 1:01 PM To: [email protected] <mailto:[email protected]> Subject: RE: [NTSysADM] OS in the CPU And if the current stats are even close to accurate there are something like 200000 unfilled cybersecurity jobs at the moment with only about 20000 qualified people to fill them, and the unfilled numbers are growing faster than the qualified people. That would lead me to think that the ‘career ending event’ would actually be a gateway to a new job where they probably understand that you can’t possibly catch everything, particularly heretofore unknown things. How’s that saying go? You can’t know what you don’t know. -- There are 10 kinds of people in the world... those who understand binary and those who don't. ¯\_(ツ)_/¯ From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Andrew S. Baker Sent: Tuesday, November 21, 2017 11:43 AM To: ntsysadm <[email protected] <mailto:[email protected]> > Subject: Re: [NTSysADM] OS in the CPU Sure, but there are lots of ways to lose jobs -- many of which have nothing to do with your own personal actions. InfoSec currently lends itself more to employment than unemployment. Regards, ASB On Mon, Nov 20, 2017 at 12:05 PM, Jonathan Link <[email protected] <mailto:[email protected]> > wrote: More like job insecurity. Missing an exploit might be a career ending event, even if it is heretofore an unknown exploit. On Mon, Nov 20, 2017 at 11:54 AM Melvin Backus <[email protected] <mailto:[email protected]> > wrote: Some call them opportunities, we in IT call them job security. :) -- There are 10 kinds of people in the world... those who understand binary and those who don't. ¯\_(ツ)_/¯ From: [email protected] <mailto:[email protected]> [mailto:[email protected] <mailto:[email protected]> ] On Behalf Of Kurt Buff Sent: Monday, November 20, 2017 11:34 AM To: ntsysadm <[email protected] <mailto:[email protected]> > Subject: Re: [NTSysADM] OS in the CPU There are always more problems: https://www.thezdi.com/blog/2017/10/04/vmware-escapology-how-to-houdini-the-hypervisor https://www.youtube.com/watch?v=uRemWLNBSZg On Mon, Nov 20, 2017 at 8:05 AM, Andrew S. Baker <[email protected] <mailto:[email protected]> > wrote: But wait! There's more... https://www.youtube.com/watch?v=KrksBdWcZgQ (I see your "solution" and raise you two more problems) Regards, ASB On Sun, Nov 19, 2017 at 12:28 PM, Kurt Buff <[email protected] <mailto:[email protected]> > wrote: The OS in question (minix), isn't in the main CPU - it's in the CPU of the management engine, which is completely separate, and doesn't, or at least shouldn't, affect system performance. https://en.wikipedia.org/wiki/Intel_Active_Management_Technology#Hardware That actually makes it worse, since as long as the machine is connect to power, even though putatively "off", the management engine is available. That is, if it's been configured. This is an enterprise feature, so the ME is usually not active in consumer-grade computers. But, if it's present and turned on, then it's pretty risky: https://www.theregister.co.uk/2017/11/09/chipzilla_come_closer_closer_listen_dump_ime/ But there's some hope, of a sort - Google is on the case: http://www.tomshardware.com/news/google-removing-minix-management-engine-intel,35876.html Kurt On Sun, Nov 19, 2017 at 6:34 AM, Andrew S. Baker <[email protected] <mailto:[email protected]> > wrote: No wonder our machines don't seem as fast as we think they *could* be... They're busy running more stuff than we thought: http://www.zdnet.com/article/minix-intels-hidden-in-chip-operating-system/ The security implications are also pretty staggering... Regards, ASB
