4 ms·
Drupal. Interesting choice in 2024
by piker 3y ago
Drupal. Interesting choice in 2024
- bsenftner 3y agoI agree. Unless Drupal redesigned their core, the way plugins and themes work is insecure by design. Similar to how software was back in the 80's where it was assumed no bad actors were running within the environment, and due to that assumption every single thing is available to be mucked with.
- dubcanada 3y agoIs there a CMS with such an ability?
- kapilvt 3y agoPlone was closest I saw, also run by several gov agencies, but drupal popularity won out to due to ease of staffing.
- deleted 3y ago[deleted]
- calvinmorrison 3y agoYeah this is why you use a php platform like laravel which actually is engineered to build abd extend rather than say WordPress with an insane plugin system
- karlshea 3y agoDrupal is way more similar to Laravel these days (Drupal is now also built on top of Symfony) than WordPress.
- treflop 3y agoYou don’t have to use third-party plugins or themes though? I mean if you built a site from scratch in Spring or Next.js and you start using third-party libraries or UI frameworks, all those third-party bits have full access to everything too.
- chx 3y ago> the way plugins and themes work is insecure by design. Tell us more. (A lot more. "Extraordinary claims require extraordinary proof".)
- bsenftner 3y agoAnytime any plugin does anything, the submission of that "anything" into the Drupal subsystem proceeds to pass that plugin's payload to every single plugin in the system so they can make modifications. What those modifications are, you do not know, they are just applied and then your modified payload is accepted into the subsystem to modify whatever it modifies.
- chx 3y agoIf you are installing rogue code then you will have a bad time. Modules/themes on drupal.org which show "Stable releases for this project are covered by the security advisory policy" are written by trusted users. There is no other protection from rogue code because they are inherently able to access the database. It utterly doesn't matter what extension points the code supports and how because of that. In very broad strokes, if you are using any CMS which a) accesses a database b) allows installing additional code and it runs that in the same process as the CMS code accessing the database -- then you are vulnerable to rogue code. Like, a headless CMS where the frontend only talks to it via an API is protected from rogue code in the frontend part but that's about it. This means the Drupal ecosystem is vulnerable to a supply chain attack, yes but ... um ... that doesn't make Drupal design insecure, does it?
- dubcanada 3y agoNot really, most government websites use it. It’s still very popular.
- bazil376 3y agoMost? Source?
- dubcanada 3y agohttps://groups.drupal.org/government-sites https://groups.drupal.org/government-sites https://www.acquia.com/blog/drupal-for-government https://www.acquia.com/blog/drupal-for-government https://www.drupal.org/industries/government https://www.drupal.org/industries/government https://www.zyxware.com/article/6229/top-7-reasons-why-drupal-best-cms-federal-sites https://www.zyxware.com/article/6229/top-7-reasons-why-drupa... https://www.drupal.org/openplus https://www.drupal.org/openplus https://www.applytosupply.digitalmarketplace.service.gov.uk/g-cloud/services/315701751718009 https://www.applytosupply.digitalmarketplace.service.gov.uk/... Now most may be a stretch, it's a hard metric to calculate without going around and counting every gov site. But for English speaking countries, it is very popular enough so that I'd say most gov/state/department websites are Drupal. That and I am a Drupal consultant. So I may be biased.
- circusfly 3y agoWheels remain an interesting choice in 2024 as well.