Showing posts with label Cisco. Show all posts
Showing posts with label Cisco. Show all posts

Wednesday, June 15, 2016

Microsoft Buys LinkedIn...Another shot in the foot


If you've spent any time looking for greener professional pastures in the past few years your path has undoubtedly crossed with LinkedIn.

Touted as "The Facebook for business" the social networking site promised the same kind of experience in the professional world.  Career consultants and HR types lauded it as an invaluable resource for connecting with the hiring movers and shakers in industry.  It was supposed to be the missing link between casting your resume into the void of Monster.com and a lunch date with your potential boss.

Which it was.  That is, so long as you actually knew someone.  

Just like any other social network its usefulness is limited by the people you actually know.  The sad reality is you're more likely to run into people you never want to see again than anyone that could give you a leg up.

Worse, over the years LinkedIn has become infected with the same resume-stacking, quota chasing,  recruiter types on the job boards that send you emails like this...

"Hi Everyone,
We have Informatica Architect available @ Charlotte, NC area. He is looking opportunities only @ NC, TX and GA areas. If anyone is having requirements in that areas. Kindly share me the job details along with the client information. We are marketing around $75-80/hr c2c.
Thanks for your time…

Thanks,

Spammy D Recruiter
Ph: 555- 555- 0412 
Email: spammy@spammyrecruiter.com"

Yeah, UMMM, I'm actually looking for work not hiring and that other thing....I live in Arizona....

So what does this have to do with Microsoft?  Are they looking to take on ZipRecruiter?

Unlikely....

It's just the latest reach into the dream of ubiquity dearly held by Microsoft CEO's.  They already have a hand in Facebook, Android and gaming.  They've owned the office for years and this latest purchase is proof of their intention to keep it.

The most likely outcome from the $26.2 billion dollar deal is to absorb the analytics capabilities of the LinkedIn platform and place yet another useless live-tile flashing in the Windows 10 start menu.

So how has all this buying paid off for Microsoft?

A look at their buying habits reveals that they're better at acquiring stocks than companies.

Let's compare and contrast....



Microsoft makes $34 billion off Android Patents, writes off $9 Billion for the Nokia Acquisition.

Microsoft invests $150 million in Apple  ultimately saving the company and enjoying a tidy profit when the stock splits and they sell it a few years later.  Oh yeah, and they have a guaranteed space on a competitors platform for Office.

Microsoft buys Skype for $8.5 Billion and turns an innovative, lightweight VOIP solution into a bloated mess with a paywall making it among the most hated services in its portfolio.  

Next, they kill off the beloved Windows Messenger after buying Yammer for $1.2 billion.  Once positioned as Messenger's hipster "Facebook-esque"replacement it was never heard from again outside of an Office 365 subscription. 

It seems Microsoft's acquisition strategy is to buy up companies that are just past their heyday, gut them then take a write-down later.  Kind of like when IBM purchased ROLM and  Lotus.

LinkedIn is no different.  It's only useful to those HR types that have to meet a contact quota every week and enjoy self-congratulating articles about what a good job the industry has done commoditizing job seekers like so much cattle at an auction.

Mark my words, this isn't a good thing for Microsoft.  At least no more than Nokia was going to win them market share in the mobile space or Skype was going to supplant Cisco's VOIP offerings.

But all is not lost!  Take heart friends because every time Microsoft screws up another tech company the resulting void proves to be a boon for the open source community.

Which is almost as bad but at least you're free of Microsoft's incessant sales campaigns and licensing boondoggles. 

I got off LinkedIn a couple of months ago precisely because the service did nothing for me but fill my inbox with spam.  It's a service in decline which made it a ripe target for Microsoft. 

Meaning a change in ownership, especially when its Microsoft, won't make it any more attractive.

I'm just not interested in turning my next job search into another Microsoft marketing opportunity...





Tuesday, April 22, 2014

Why Heartbleed Happened

Originally published on Kupeesh!


So what's up with all this HeartBleed nonsense?

What could possibly be behind the greatest crisis in Internet security since the invention of phishing emails?
How could this possibly happen?  What could possibly jeopardize the security of thousands of websites and secure services we take for granted like Google, Tumblr and even banking sites?

I have an easy answer and it points right back to the Achilles heel of Open Source. 

While proponents will argue the merits of solutions that don't come from commercial sources the one inescapable fact of Open Source software is that it's developed under mob rule.

Therein lies the problem. 

While nobody questions the benefits of Open Source software like cost and ease of customization, proponents tend to gloss over the fact that some projects are better managed than others.

Take the case of OpenSSL.  It's the foundation for thousands of web services like Google, Yahoo and even your bank.   Except that somebody wasn't minding the store and for two years the mechanism that was supposed to secure your communications...didn't.

The flaw was inadvertently discovered by Google's Neel Mehta during a routine security sweep but the flaw had been in existence for 2 years.  Overlooked by one of OpenSSL's core developers, Stephen N. Henson, the vulnerability came as the result of additional but apparently untested new functionality known as a Heartbeat for OpenSSL.  The functionality was supposed to function as little more than an "I'm still here!" beacon to whatever service you're connected to.  

The short of it is this...

The problem comes from not bothering to check that what's sent matches what was requested.  A crafty hacker can take advantage by continually sending heartbeat requests claiming to be of a certain size but not actually being that size.  The server dutifully responds by sending back a response of the claimed size to the client and inadvertently dumping the contents of its memory to fill the otherwise empty space of the response.  The contents of which have been shown to contain user credentials among other compromised information.

It's apparently a simple fix but it's taken two years for anyone to notice. 

Meanwhile, nobody knows how long the bad guys have been aware of the flaw.  How can something like this get by the supposed vigilance of security gurus and major corporations alike? 
I can tell you how, it's endemic, it's cultural and it's arrogance...

It's a misguided belief that oversight of a product is best left to a community regardless of its qualifications to do so.  A community that frequently finds itself more concerned with the technical wizardry of its products than the users who deploy them

It's the same mindset that's kept other Open Source offerings like Linux in the shadows of Windows.  Let's be honest here.  You can only stomach so many unintelligible whitepapers or narcissistic support forum posts before you just give up.  The inmates are indeed running the asylum...

Heartbleed shines a light on the failure of the Open Source community in that it lays open the lack of even the most basic oversight of a critical and widely used service.  It's not so much about the failure of OpenSSL but rather that nobody including its chief stewards noticed the problem for two years.


This is nothing less than a reality check on the entire Open Source community.  One that should be raising questions in anyone that relies on their wares.

Thursday, January 16, 2014

Dealing with the latest Java Security update for your legacy apps

Java's gotten a bad rap lately and with good reason.  It's got so many security holes that it triggered an alert last year from Homeland Security.  Since then we've been getting pretty regular updates from the folks over at Oracle.

If you happen to administer networking equipment, especially Cisco branded devices, you've no doubt run into issues that come with Java updates.  If you have to manage different generations of networking equipment, for example, there's not doubt you have to maintain multiple versions of Java to manage them.

The latest Java security update for Java, 1.7.0_51, has finally made good on a threat.  It's activated functionality that effectively blocks any Java applet that doesn't have the "security manifest" parameters enabled.

That can leave you dead in the water.  Except, if you know how to work around it.  The video below shows you how to set an exclusion for trusted connections and applets.

Remember, this is only for connections and applets that you have complete trust in.




Saturday, July 6, 2013

The Truth about IT

I'm going to let you in on a secret...

If you're in IT nothing you do really matters.  At least not in the sense  of doing anything the world cares about.  I've said it before, IT exists to service people who actually create something.  It's a classic service industry job no matter what your title and that puts you right up there with the plumbers and auto mechanics. 

Plumbers don't get their names on monuments.  Neither do cab drivers, doormen or IT pros.  The world becomes more inconvenient without them but in the end they only exist to make someone else's life easier. 

I suppose that's why there's so many certifications for the profession now, assuming you could call it a profession.  It's not good enough to just be competent, now we need a governing authority to validate us.  A governing authority that's built a multi-billion dollar business out of our own insecurities.  As though we needed another reason to doubt our own abilities.

Even worse, validation from these governing authorities is suspect.  They exist less for the advancement of knowledge than their own revenue.  Why for instance would I need to not only carry a certification for Network knowledge but also specific product knowledge?

If I've been building networks for 20 years who cares if I have a Network + , A+ or ITIL anyway?  Those are supposed to be vendor neutral.  Surprise! network + was primarily developed by Cisco and A+ was written by hardware manufactures like HP, Dell and IBM.

 ITIL was written by masochists.

I've actually been disqualified for entry level tech jobs with (at the time) a decade of experience because I didn't have the right certification.  Never mind that on top of the experience  I had an electronics engineering degree, actually know what to do with a logic probe and was trained to troubleshoot PC's at board level. 

Because I refuse to spend $110 on an exam to see if I know which pin of a Molex connector is ground I can be denied a job I could do in my sleep because somebody thinks managing IT is all about the right certification.   If I've been working with networking  and computer equipment for most of my career why is it important what brand names were on the faceplates?

I know why and so do you, the people you're talking to don't have a clue about the department they're managing or worse don't really care. 

What's really sad is that your choice to work in the field means you have an 8 in 10 chance for having to work for them.

Here's a newsflash for the uninitiated, In the IT space everybody has to play by the same rules or nothing works. 

Do you really believe that the whole world runs exclusively on Cisco, Juniper, HP or 3Com equipment? 
Then it might surprise you to know that two brand agnostic organizations (IEEE, IETF) make the  Internet and networking in general possible.  They could care less whose brand is on your router so long as it plays by the rules they make. 

It's a perfect example of how useless vendor certifications are and an equally perfect indicator of a broken IT organization should it subscribe to another useless certification, the ITIL.

If you see a job description that demands a specific brand certification or worse the dreaded "familiar with ITIL methodology" you're likely dealing with a hiring manager that doesn't understand their own department.  A hallmark of an ITIL organization shows itself when ability is defined only by plug and play solutions no matter how ineffective.  They're not looking for ability, they're looking for the status quo even if it's dysfunctional.

I'm not against education or training, I'm just against the commoditization of it.  I'm also against lazy management practices based on buzzwords and fads.  Effective IT managers know at least something about the nuts and bolts of their department and can lead from experience.   

Ineffective IT managers are just waiting around till the next seminar on their way to their next job.  They rule by edicts lifted straight out of the framework of the dogma they've embraced and then slam the door on your way out. 

Good managers lead from experience not seminars.  You have to know what's right to know when things have really gone wrong.  You also have to give a damn or you're useless. 

That can be a tall order considering how neutered the IT function has become in the last decade.  IT budgets are strictly administered (usually by someone other than IT) and organizations don't have the latitude they once did.

If you're unlucky enough to be working in an organization that's fully embraced the ITIL construct you can expect to be constantly swimming upstream.  ITIL demands that technology and technical concerns take a back seat to the every whim of the user base.  

Yes, IT is a service profession but constant pandering leads to sloppy IT organizations and eventually to another tenet of ITIL, workarounds.  In other words, band-aids and bailing wire take precedence over actually fixing the problem.

Everyone demands zero downtime but refuses to do what it takes to achieve it.  IT professionals are expected to be on-call 24/7 for a wage that doesn't compensate them for that commitment.   Lest we forget the hardware to make it happen.

You're a fool if you accept that but most fools in IT do. 

If you care about what you do you then you don't mind the crazy hours but I can count on one hand the number of people I've met who were doing more than going through the motions.  Here's another newsflash, they weren't working 9 to 5.

We've come full circle.  The cold hard reality is that IT is a service profession and doesn't lend itself to rigid schedules and the meaningless busywork. 

So what can you look forward to if you happen to land that "dream?" IT job.  Maybe you're the new System Admin or IT manager.  Good for you.  Now that the pleasantries are over it's time to figure out if you'll be around long enough to wear out your office chair.

Let's play a little point/counterpoint framed in the context of questions asked in the average IT interview...

Why do you want to work in IT?
Point
Counterpoint
I love technology and I want to help people make the best use of it.
Technology makes the world go round and it's better than flipping burgers for a living.  But not by much.

Where do you see yourself in 5 years?
Point
Counterpoint
Hopefully in a management position so I can help further business goals using IT.
Probably in management because the last 2 IT managers quit and I managed to not get fired.  However, I know I'll be burned out because nobody is willing to do what it takes so I'll just bide my time.  I'll probably attend a lot of seminars looking for a way to make my life easier and do the bare minimum.  I'll hire lots of people with letters behind their names to make the department look good till I move on to my next job.

What is IT's function?
Point
Counterpoint
To further the organization's goals with the services I provide.
To keep the executive suite from complaining too much and maintaining the status quo because nobody really gives a damn what I do so long as they get their email and can play Farmville on their IPAD.

What's the value of IT certification?
Point
Counterpoint
It shows a commitment to continuous improvement and allows me to keep up to date with the latest technology.
Nobody cares about my MBA so I better have some more letters behind my name if I want to keep my job. 

What's more important, Technology or customer service?
Point
Counterpoint
IT is a service industry, our users, customers or whatever the label, come first.  They need to feel confident in the resources we provide
IT IS a service industry and you shouldn't be in it unless you understand that.  However, if you don't have the resources to do your job properly and decisions are made based on price instead of value (there's a difference) then you're never going to achieve customer satisfaction.  That is unless they're satisfied with you constantly saying "I'm sorry"

Ok, so the counterpoint looks like someone you wouldn't want within 100 miles of an IT department.  Here's the rub, the Point column is largely BS and everyone in the field knows it.  It looks good on glossy brochures but you can't get blood from a stone. 

Most IT departments are lucky to get new patch cables let alone the resources they need to meet user  demands.  The "Counterpoint" side is sadly closer to reality than anyone wants to admit to.  It's why I personally prefer contract work because I'd rather not waste time spinning my wheels and going nowhere while the rest of the department struggles for legitimacy that the field just can't provide.

IT can be rewarding but not when it's treated like the accounting department.  Truth be told if technology was forced to evolve in an average IT department, we'd still be using Motorola Dynatacs and dialing up to AOL for email on 28.8K modems.

The problem with corporate IT management methodologies is that you have a lot of people sitting around just waiting for something to happen.  When you are busy it's generally because one of the band-aids fell off the server and the CEO is screaming about how he can't get to EBay because of it.

Lets' face it, we're the plumbers, electricians and architects of technology.  We know what to do and how to do it (Hopefully?)  The best measure of success is that things work when they need to and that's the only goal that matters.

 We do what we do because we care about our life's work. (Well, at least first before we get jaded.)  Thing is,  that much ambition doesn't get you too far in most corporate IT departments.  Too much passion scares corporate types which means you either get shown the door or you just trudge on and abandon your soul.

Where a real tradesman is looked upon as the authority in their profession, IT is frequently seen as a necessary evil.  It's hard if not impossible to meet the demands of an organization when your hands are tied by corporate dogma. 

It's not that I'd advocate IT having no oversight but when you have to pass every decision through the  corporate litmus test, the result is going to be mediocre at best. 

Thus we have the "standard of mediocrity" ultimately resulting in IT pros clutching at straws to appear relevant.  That feeds my earlier assertion of how IT certifications prey on your own insecurities.  If you really care about the field and really want to effect change then you have to be brave enough to not just suffer in silence or load your resume up with worthless certifications.

The best known figures in technology didn't hide behind their cubicles hoping for someday.  Bill Gates of Microsoft and Steve Jobs  of Apple would have never survived in the average IT department.  Hell, they couldn't even stand college where at least there was beer and girls!

So why do we expect people who thrive on technology to function like accountants?  Would it be reasonable to expect an auto mechanic to fix your car in your bathroom? 

Well, I'm sorry to tell you, that's the reality of IT more often than not.  Unless you can make a go of it with the feast or famine cycle of consulting (as in independent not Robert Half) you're stuck with it. 

Of course, If you're more into the management track or the cubicle lifestyle I suppose it can work for you but I can guarantee I won't at least not as your employee.

Wednesday, January 9, 2013

Goodbye Messenger, hello Skype


Today was a sad day for the masochist.  Microsoft has announced that it is officially pulling the plug on Windows Live Messenger on March 15th in favor of its latest acquisition, Skype.  While not much of an improvement the cries of the old guard of Internet social interaction bemoan the transition to a platform seemingly made worse by Microsoft's acquisition. 

Skype has become a staple of streaming podcasts in the past few years which while buggy was still adequate for real time interaction.  Once Microsoft picked it up for a cool 8.5 billion in 2011 it was obvious that it was to be the centerpiece of a new social strategy.  To that point, disparate applications usually woefully lacking left those in the Microsoft centric universe looking elsewhere. 

Of course as with any new acquisition Microsoft had to put their stamp on it.  A move that many podcasters (the most vocal group) found irritating if not debilitating.  Many of whom refused to upgrade from the Pre-Microsoft version of the application when "new" features effectively locked them out of their livelihood. 
It was still better than Live Messenger though.  A leftover from the days when AOL's instant Messenger (AIM) was the de facto IM client of record.  As it aged, it became the foundation for Microsoft's Office Communications manager (Lync) for corporate centered messaging.  For casual users it could be counted on to fail at inopportune moments often forcing a reboot to regain functionality.

570425_Up To 60% Off w/ Free Shipping 120x90Skype can make (mostly) free phone calls too, a feature messenger could never hope to achieve on its creaky underpinnings. If we want to peer into our crystal ball,  it's not inconceivable for Microsoft to be eyeing Skype as a professional VOIP solution.  That would provide them with a viable alternative to offerings from companies like Cisco and RingCentral.  Not unlike the DirectAccess product meant to replace VPN's from Cisco and Checkpoint.   

If you were wondering why Microsoft has decided to put Messenger out to pasture, look no further than the balance sheet.  Messenger's features are free for the most part, Skype's are not.  Even with free accounts, regular use eventually demands a credit card with subtle reminders in the app of how much better your life would be if you'd just "upgrade" your experience to the paid version.

So while today spelled out mandatory retirement for our cranky old social companion, we can look forward to the equal annoyance of Skype to salve (or open) our wounds. 

Where's open source when you need it..