Did Drupal and Drupalgeddon Lead to Panama Papers Leaks?
drupal.ovh
drupal.ovh
The text of the article betrays a troublesome double standard, saying things like:
> Because WordPress and Drupal are so mundane nowadays, people easily forget that they are continuously online targets for malicious activities.
Of course, all websites, regardless of which software, are continuously online and targets for malicious activities.
> Since there is no single entity to blame for Drupal or many Open Source CMSes, as opposed to commercial entities like Oracle or Microsoft - there is no single source to point take responsibility.
If you fail to apply Oracle and Microsoft patches in a timely manner, you will get hacked on those platforms too. And it won't be Oracle's or Microsoft's fault.
> Increased awareness of web services security matters is required from the Open Source communitities so that we will avoid large information leaks in the future.
This has nothing to do with the Open Source communities--Drupalgeddon was patched months ago. This is simply a business that failed to pay enough attention to their technology--a situation that is sadly very common.
The real reason that lead to this is the strategy of running security updates to a public-facing website containing sensitive materials with the frequency of only once every 1-2 years, or worse. Assuming of course that this website is the source of these leaks at all.
The developers (at least at the time) were more interested in making repeated breaking changes than they were in investing the effort to allow earlier adopters a reliable upgrade process.
My irritation was that this was the metaphorical equivalent of a business offering a fantastic deal to new customers but treating existing customers with palpable disdain.
Think of a database, but instead of a database you have some weird mix of MS Access and irresponsible use of EAV. That's Drupal.