News for hackers. Stuff that matters.
Re:Security vulnerability in #Drupal contrib module puts 120... by orf on Friday April 14, 2017 @02:42PM (#14116257)
> Drupal is known for it's large number of community contributed modules that add functionality to the bare bones core system.

No, it's known for its ridiculous number of security issues and sloppy code :/

Re:Security vulnerability in #Drupal contrib module puts 120... by ksenzee on Friday April 14, 2017 @02:55PM (#14116335)
Drupal is easy to criticize, but its handling of security issues and its code quality aren't the two places I'd start. They're actually two of the strengths of the project.
Re:Security vulnerability in #Drupal contrib module puts 120... by jacquesm on Friday April 14, 2017 @04:05PM (#14116853)
You're missing a /s there.
Re:Security vulnerability in #Drupal contrib module puts 120... by mschuster91 on Friday April 14, 2017 @04:13PM (#14116912)
I've seen worse, way worse, than Drupal Core.

That of course does not include Drupal modules - there is, similar to the Wordpress ecosystem, the really bad stuff.

Re:Security vulnerability in #Drupal contrib module puts 120... by jacquesm on Friday April 14, 2017 @04:19PM (#14116959)
But that's the whole problem right there. Such a plug-in architecture with every Tom, Dick & Jane writing modules that are loosely vetted and deployed in the 100's of thousands is broken by design. There is no way a small review team focused on security will be able to audit what 1000's of dedicated lesser gods produce.

I can see the advantage of it, you just focus on the core and let the world take care of its own problems but you end up with nearly every site being critically dependent on a couple of obscure modules that will not get the attention they need until it is much too late. This coupled with Drupals nasty habit of obsoleting everything every couple of year (I hear they are changing now) and you're set up for disaster.

So even if Drupal Core is not all that bad it is never just Drupal Core.

Re:Security vulnerability in #Drupal contrib module puts 120... by Gaelan on Friday April 14, 2017 @04:29PM (#14117062)
To get a module marked as "covered by the Drupal security team" it is required to go through a community code review.
Re:Security vulnerability in #Drupal contrib module puts 120... by jacquesm on Friday April 14, 2017 @04:41PM (#14117161)
Yes, but that's backwards. There are many many modules that don't have that stamp but that are distributed via the site and besides I strongly believe that security is not something you just vet for after the fact but that should go in to the design of your product.

If you don't do that it becomes a 'find the last hole in the cheese' exercise and very likely there will be many holes that you don't find that way that would not have been there in the first place had the whole thing been designed from day one with that in mind.

On the whole I think 'let amateurs build it and experts vet it' is better than just 'let amateurs build it' but it doesn't come close to 'let experts build it and experts vet it'.

Re:Security vulnerability in #Drupal contrib module puts 120... by lightlyused on Saturday April 15, 2017 @04:09PM (#14122576)
Which is pretty easy to pass, you just have to follow the coding standards.
Re:Security vulnerability in #Drupal contrib module puts 120... by Gaelan on Saturday April 15, 2017 @08:42PM (#14123718)
And not have any (glaring) security flaws.
Re:Security vulnerability in #Drupal contrib module puts 120... by devwastaken on Saturday April 15, 2017 @12:18AM (#14119372)
This I can agree with. The community frowns upon selling modules. This is reflected by the official repository offering no option of purchasing modules, no marketplace. Contributors only make money by being sponsored by hosting sites like Acquia, where usually they're making modules /for/ them. This of course makes Drupal unnattractive for more advanced functionality. But, single developers still try to create that functionality anyways, even if its something that needs constant work and usual updates. This then understandably falls to the way side because life. Some things just need business behind them, they can't survive on openness alone.

Also: https://www.lullabot.com/articles/why-paid-drupal-modules-fa...

Re:Security vulnerability in #Drupal contrib module puts 120... by jpetso on Saturday April 15, 2017 @01:58PM (#14121878)
Drupal is GPL, so a module written specifically for Drupal must always be redistributable under GPL as well since it's a derived work. That places a natural limit on the feasibility of module purchases, since anyone could buy it and then mirror it for free.

The correct answer here is that if you don't like Drupal's free & community-focused development model, you're likely better off switching to some off-the-shelf software. Alternatively, you can pay a consulting company to maintain the module, which is how many of them get written anyway (and then given away for free). So if you focus on modules with commercial backing, you've got a pretty close approximation without giving up GPL freedoms.

Re:Security vulnerability in #Drupal contrib module puts 120... by ajsalminen on Friday April 21, 2017 @03:24AM (#14163684)
If you think going non-free with the modules would help you should take a look at the codebases of some of the most popular premium Wordpress modules. You'll find much worse than in a popular Drupal contrib module.
Re:Security vulnerability in #Drupal contrib module puts 120... by heywire on Friday April 14, 2017 @04:54PM (#14117261)
> But that's the whole problem right there. Such a plug-in architecture with every Tom, Dick & Jane writing modules that are loosely vetted and deployed in the 100's of thousands is broken by design.

Wait, are you talking about npm or Drupal? (only kind of kidding)

Re:Security vulnerability in #Drupal contrib module puts 120... by devwastaken on Saturday April 15, 2017 @12:22AM (#14119383)
That actually is a really good point about packages on NPM, or rather the culture of a 'package for everything.'. All it would take is somebody to lose their github account or go rogue, for one popular package that requires their package to also be compromised, and then hundreds to thousands of sites are silently vulnerable.

Seriously. A standard ES6 JS project will run you to actual hundreds of packages. Thats a huge attack surface.

Re:Security vulnerability in #Drupal contrib module puts 120... by devwastaken on Saturday April 15, 2017 @12:10AM (#14119348)
This can be said of every CMS ever that isn't designed for very specific cases. Many would argue Wordpress is significantly worse and a massive mess. Atleast Drupal 8 tries to standardize and use good standards. If you know a better CMS out there, or any specific current problems with drupal 8, lets hear it.
Re:Security vulnerability in #Drupal contrib module puts 120... by mercer on Saturday April 15, 2017 @07:41AM (#14120364)
One reason why I prefer Wordpress is that I can pretty much build anything I want with just 'core' and a very small number of plugins (mostly Advanced Custom Fields, which has a paid version and quite actively developed).

With Drupal, on the other hand, I've always had to install a whole bunch of contrib modules just to get the basic functionality I needed. Has that changed significantly since Drupal 6 and 7?

Am I underestimating how insecure Wordpress core is, even considering that the get the equivalent you'd need Drupal plus a whole bunch of modules?

Re:Security vulnerability in #Drupal contrib module puts 120... by devwastaken on Saturday April 15, 2017 @11:23AM (#14121099)
Drupal 8 now has views as a core module, which so far has allowed me to make custom fields for editors and allow them to relate the data entry with other entries or tags/taxomonies. Its the only CMS I've experienced so far that allows me to make data entry highly customized towards the content being added. I'm not sure what you're specifically looking at, but views is pretty much a big abstraction layer for the database, there's a lot you can do with it.
Re:Security vulnerability in #Drupal contrib module puts 120... by lightlyused on Saturday April 15, 2017 @04:10PM (#14122580)
You need a whole bunch of wp modules to get to the same level has a Drupal 8 core install.