One of our friends, one of our team, one wearing a red hat with pride is in the battle of his life and faced yet another huge skirmish today. I've mentioned before we have someone in our midst who is desperately ill with a disease that this week has claimed two famous souls and therefore is on so many radars in the most raw fashion. Except this time for us it's personal. Someone who matters to all of us at Red Hat who has given everything he has for the cause needs some prayers and has our admiration, respect and unconditional affection.

Tonight I would welcome you direct you point any prayers towards the Northern Lights for a man mountain whose bravery is without peer in my lifetime. Someone who means so much to many people on my friends list and who is not just a peer but so much more than I can ever be as a human. A father, one of my best friends, an Open Source apostle, a traveller - a journeyman who has helped carve the Red Hat story for over a decade. 

As the light faded this evening a group of us who wear the scarlet fedora sent a request, no a demand, a fervent commanding dictat to whichever idol we individually worship for the heedful and gentle loving care of one of our own.

This will be a long night, a long weekend. This hasn't been a battle, it's been a fucking onslaught, it's not been a scrimmage, it's been a campaign and now the guns fall silent and we hope for a quiet uneventful and peaceful armistice that creates a silent place where things start making sense.

Five years ago this week he and I, two mad Englishmen drove in thick driving snow from Westford, Massachusetts  to JC Penny cross the state border in Nashua New Hampshire to look at new iPads and pick up a MacBook for his wife because thats what you do, risk your life to play with tech toys. The snowdrifts were the size of trucks, we were in a front wheel drive rented sedan not a 4x4 or SUV and we needed our heads looking at. Later that evening we would drive up into the hills without a GPS without a clue where we were going for a team meeting, Laughing and probably farting nervously everytime the car skidded out. BOTH of our wives were pregnant at home in the UK and Sweden and with hindsight it was probably dumb but we survived.

Every minute I've ever spent with him has been a joy, every conversation, every piece of guidance and every laugh delivered in his own inimitable style. Breakfasting with him, whiteboarding stuff we would go on to try and invent with no resources, watching him train and shape the first steps of new starters at Red Hat saw him in his true light. Getting the best out of everyone around him.

So tonight dear friend, my companion in all things utterly politally incorrect, wrap yourself in all our love, every single drop of it is sent to cosset you as you roll up your sleeves and Queensberry Rules climb into the boxing ring for another pugilistic round with the demon that is this horrid disease.

This is for you because you would laugh, like a drain. Also he's your double !

We adore you. Ding Ding, seconds out, round 10 ....

Over the last month I've read a lot of inane crap posted by security journalists who should know better. I'm specifically addressing the issue around the vulnerability discovered in Juniper's NetScreen devices. Conspiracy theories ranging from "it's a US agency pretending to mimic Chinese state intelligence" to NSA influenced or deliberately backdoored code making its way into the release system bypassing internal QE testing.

I do "not" know the full story and nobody ever will but heres my starter for ten.

Juniper just like two dozen major US technical vendors providing catalogue items to US Government and Federal Agency / Defense customers (as well as other global government accounts and the private sector which makes up 70% of their revenues) have grown by acquisition. Not innovation. Acquisition.

Having been a CEO that exited handsomely from his own non VC funded startup I've got some experience here. As a casual investor, VC and journalist I sit and research this stuff to the nth degree and I'm still none the wiser about the rationale behind some "marriages" of technology vendors. There seems to be an expectation from a lot of analysts who frankly haven't the first clue about where tech comes from and is going, and institutional shareholders that companies should use warchests of saved revenue to grow their product range by acquiring other companies.

Rather than innovate and grow their own products safely and sanely - even if it means an increased R&D curve. Not every acquisition leads to bottom line success but often a company is acquired for its people not its product, or its market position and revenue share rather than it's product and people. It's not a precise science and you can count the number of commercially savvy acquisitions in the network sector where direct reflected growth has resulted on two hands. Often its the weak hugging the almost as sickly or it's the oft commented over valued acquisition where the inbound company (and their advisors) run towards the hills rubbing both hands as soon as their vesting period is done.

One of the problems with acquisition of technology is that most companies in the EU and the US are utterly clueless as to how to do due diligence. The financial due diligence and the locking down of commercially sensitive news and key figures takes precedence. The concept of code escrow or sanity checking of code and process is hardly ever adhered to, often there "isn't time". Sadly for Juniper (and other companies) this has cost them because as well as acquiring brand and market share and position they also acquired a lot of accidentally naive processes and a company who had gone to market delivering great value and promise that wasn't reflected in the methodology in engineering.

In October 2003 Netscreen acquired Neoteris to bolt on a lot of strength and focus around their SSL products, four months later Juniper acquired Netscreen. So you have a company, Netscreen who can't have onboarded Neoteris and their processes and engineering in key SSL processes by the time they are then acquired by Juniper. Then you have Juniper trusting the product specialists at Netscreen where there is already confusion and poor co-working on SSL engineering taking ownership of core PKI stuff.

Dumb decisions around key management and key generation, cipher strength and release engineering result because nobody at an engineering level is understanding the core skills and risks around how you onboard or do sanitisation of code and QE process. This is allowed to fester and results in a car crash that will eventually happen down the line - it was just a question of when.

Juniper aren't alone, and they're a great company. I could name six major companies all trading in the US and Israel five of them on NASDAQ, all six providing goods and services to US Gov and major government accounts where this lack of intrinsic technical and process management is compressed into forked Linux based appliances and where M&A mistakes and loss of key staff who have gone, once vested, over the horizon to do their next startup without back filling or competency checking. Worse there are two of them where GPL v3 code has been backported to GPL v2 to get around licencing issues that are generating cataclysmic future security issues which when you add to the dumb mistakes made in M&A process make you just want to bang your head on a desk.

Do I think the NSA went after Juniper ? No. Genuinely they aren't that silly, the NSA is run and managed by bright folk who are there for a reason. Do I think the NSA / GCHQ in the UK knew about the vulnerability ? Sure, I hope so, they hire the brightest and the best for a reason.

Enough poor security journalism, look at the underlying facts nobody wants to talk about - onboarding and QE failed and some engineering release managers probably held to ransom by sales guys rushed stuff out to hit a revenue cycle. It was going to happen it was just when.

News breaking tonight of the sad passing Monday of Ian Murdock founder of Debian.

It's not wise to speculate nor should anyone start openly discussing the reasons behind his death. Right now concentrate on his achievements. Personally I'm just gutted he never got the chance to demonstrate his brilliance at Docker after joining them so recently.

I can't imagine the personal torture he endured the last few days or to speculate on his state of mind, nor do I want to. More it's the tragic loss of someone who gave so much at a formulaic stage of open source when we were all finding our feet.

What he co-created has lasted and given birth to so many derived versions. His attitude to packaging and release and his influence on others will long be remembered.

Life is fragile. Go hug someone who needs it. You never know the difference it will make. We should right now be thinking of his family and his kids and the pride he had in being a father. Everything else is just noise.

So today rolled over to 1st December which marks the fifth anniversary of coming back to RedHat. I first worked with Red Hat seventeen years ago. Actually it was only a few days ago I was talking to old work colleagues about booth duty at Linuxworld Paris in February 2000. It seems a lifetime ago. Rhys Oxenham my Red Hat colleague then reminded me he was 12 when I was on stage talking about Samba and LinuxHA. I felt incredibly old.

A lifetime spent in Open Source and security has brought me so many friendships. I'm closer to some of my friends in Linux than I am my own family. They know who they are and those relationships are forged in the fires of kernel lists, security vulnerabilities, podcasts and Red Hat Summits.

Long days, long nights, eighteen hour days and making my wife a Linux widow, this year post stroke I've found a work life balance that works for me. Also a massive big shout out personally to Bryan Che. One of the smartest folk I've ever met and a mentor who is so tolerant and actually believes in people. Wish we could clone him.

Working at RedHat is not a job. It's a responsibility to do it right.