Newsfeeds

Acquia Developer Center Blog: Decoupling Drupal 8 Core: Core REST, HAL, and Setting Up Drupal as a Web Services Provider

Planet Drupal - 29 March 2018 - 6:38am

Perhaps the most critical piece of any decoupled CMS architecture is the API layer which exposes data in the back end for consumption by other applications. In Drupal's case, the REST module (also known as the RESTful Web Services module) in Drupal 8 core fulfills this responsibility. The REST module contains important logic that drives the availability of data through formatted responses.

Tags: acquia drupal planet
Categories: Drupal

Opportunities widget from Science-Community.org

New Drupal Modules - 29 March 2018 - 6:12am

This widget allows you to incorporate smart self-updating list of academic conferences, scholarships or vacancies into your web-site.

You can configure and display these types of opportunities:
-- academic conferences; you can specify scientific area
-- grants/scholarships; you can select their type
-- scientific vacancies; you can choose their area

Additionally you can configure the language and the quantity of opportunities being displayed.

Categories: Drupal

Brazilian Address Field

New Drupal Modules - 29 March 2018 - 6:09am

This defines a new field type to store brazilian postal adresses according to
recommendations of the brazilian postal service company, Correios. The address
consists of the following fields:

* Thoroughfare (Logradouro): type and name of the thoroughfare
* Number (Número): the number of thoroughfare
* Complement (Complemento): apartment number and/or another info
* Neighborhood (Bairro)
* City (Cidade)
* State (Estado)
* Postal code (CEP)

Categories: Drupal

Steamforged Previews Veteran Decimate For Guild Ball

Tabletop Gaming News - 29 March 2018 - 6:00am
The Union in Chains event for Guild Ball saw the Union players spread out among the other Guilds. In the case of Decimate, she’s ended up with the Brewer’s Guild. Her knowledge with the sword is no longer employed with a foil or rapier, but a broadsword. So, what sort of changes does that mean […]
Categories: Game Theory & Design

An Open Letter About Making Gaming Work for You (and building your strengths through role play)

Gnome Stew - 29 March 2018 - 5:00am
This week at the Stew, some of us were inspired by a series of disparate recent events to send some love and sentiments out to young gamers, especially those who are marginalized. We wrote these letters to our younger selves, because in you, we see ourselves, and we hope that we can give you the […]
Categories: Game Theory & Design

bootstrap simple carousel

New Drupal Modules - 29 March 2018 - 3:41am

The module provides the carousel block. It uses the bootstrap carousel with all the features of bootstrap script.
All the info and available settings yon can see on the bootstrap page.

Features

The bootstrap carousel module:

Categories: Drupal

Thanks to the Drupal Security Team for keeping us safe

Dries Buytaert - 29 March 2018 - 12:36am

We released new versions of Drupal 7 and Drupal 8 yesterday that fixed a highly critical security bug. All software has security bugs, and fortunately for Drupal, critical security bugs are rare. What matters is how you deal with security releases.

I have the utmost respect for how the Drupal Security Team manages a security release like this — from fixing the bug, testing the solution, providing advance notice, coordinating the release, to being available for press inquiries and more.

The amount of effort, care and dedication that the Drupal Security Team invests to keep Drupal secure is unparalleled, and makes Drupal's security best-in-class. Thank you!

Categories: Drupal

Dries Buytaert: Thanks to the Drupal Security Team for keeping us safe

Planet Drupal - 29 March 2018 - 12:36am

We released new versions of Drupal 7 and Drupal 8 yesterday that fixed a highly critical security bug. All software has security bugs, and fortunately for Drupal, critical security bugs are rare. What matters is how you deal with security releases.

I have the utmost respect for how the Drupal Security Team manages a security release like this — from fixing the bug, testing the solution, providing advance notice, coordinating the release, to being available for press inquiries and more.

The amount of effort, care and dedication that the Drupal Security Team invests to keep Drupal secure is unparalleled, and makes Drupal's security best-in-class. Thank you!

Categories: Drupal

OSTraining: Learn Drupal 8 Layout and Theming By Taking the Class

Planet Drupal - 29 March 2018 - 12:16am

One of the most frequently asked questions among our Drupal students is "How to control layouts?"

If you really would like to be in control of layouts, you need to learn theming.

We created a brilliant "Drupal 8 Theming and Layout" video class to help you. In this post, you will take a look at the class modules and what you can learn while taking them.

Categories: Drupal

Words on a Screen: Accounting is Fun

RPGNet - 29 March 2018 - 12:00am
Information tracking in PbPs.
Categories: Game Theory & Design

myDropWizard.com: The continuing importance of the Drupal 6 Long-Term Support program

Planet Drupal - 28 March 2018 - 10:02pm

Drupal 6 reached End-of-Life over 2 years ago, so you might be forgiven for thinking that Drupal 6 and its Long-Term Support (D6LTS) no longer matter.

However, yesterday (March 28th, 2018), there was a HIGHLY CRITICAL security vulnerability announced that affected Drupal 6, 7 & 8 (and even Backdrop).

This wasn't the first Drupal 6 LTS core release (did anyone notice that one?) and it probably won't be the last. And there are still ~65,000 sites running Drupal 6 according to Drupal.org, which were affected by this issue, and could be affected by future issues.

Luckily, the Drupal 6 LTS program is still going, and we got a patch and release out immediately!

But the D6LTS program won't go on forever... at least without users of Drupal 6 continuing to buy support from the D6LTS vendors.

I think this is a good time to remind everyone what the D6LTS program is and why it's still important to the Drupal community...

Categories: Drupal

Weixin Payment / WeChat Payment(微信支付)

New Drupal Modules - 28 March 2018 - 5:31pm

Weixin Payment is a popular thrid-party online payment solution in China, founded by Tencent Holdings Limited (HK0700).

This module integrate Weixin Payment with your Drupal website, support QR pay, H5 pay and Subscribtion pay(扫码支付、H5支付、公众号支付).

Dependencies
Please install Libraries API and download the PHP version SDK from Weixin developer center, unzip it under sites/all/libraries

Categories: Drupal

Weixin Payment/WeChat Payment(微信支付)

New Drupal Modules - 28 March 2018 - 4:45pm
This module has been moved to Weixin Payment for a new short name 'wxpay'

Weixin Payment is a popular thrid-party online payment solution in China, founded by Tencent Holdings Limited (HK0700).

This module integrate Weixin Payment with your Drupal website, support QR pay, H5 pay and Subscribtion pay(扫码支付、H5支付、公众号支付).

Categories: Drupal

Wunderkraut Sweden Blog: Drupal SA-CORE-2018-002 and us

Planet Drupal - 28 March 2018 - 2:27pm
One week ago, we got a warning about a very important security update for drupal core, that effected drupal 7 and 8 (and even 6, that is not supported anymore) were going to be released today. And we started to plan for updates. One week ago, we got a warning about a very important security update for drupal core, that effected drupal 7 and 8 (and even 6, that is not supported anymore) were going to be released today. And we started to plan for updates. For a couple of years ago, it was a hard work for us to update a site if a security update was released. Now days our hosting and our processes is much better and simplified, and thanks to the team effort of our Live-team at Digitalist, we got our most important sites patched in minutes after the security release were released.  Totally we patched around 1700 sites that we are hosting in less than 2 hours after the security patch were released. If you… Read More
Categories: Drupal

Platform.sh: More details on Drupal SA-CORE-2018-002

Planet Drupal - 28 March 2018 - 1:00pm
More details on Drupal SA-CORE-2018-002 Crell Wed, 03/28/2018 - 20:00 Blog

Platform.sh customers should visit Safe from DrupalGeddon II aka SA-CORE-2018-02 for the specific steps we took to protect all our Drupal instances.

Earlier today, a critical remote code execution vulnerability in Drupal 6, 7, and 8 was disclosed. This highly-critical issue affects all Drupal 7.x and 8.x sites and most Drupal 6.x sites. It is trivially exploitable remotely by anonymous users on any site that exposes forms. It is very possible that your site exposes this vulnerability even if you are not aware of publicly accessible forms. You should update immediately any Drupal site you have to versions 8.5.1, 8.4.6, or 7.58, as appropriate.

How to know if I am affected?

We are currently not aware of exploits of this vulnerability in the wild but this will undoubtedly change in the next few hours. Writing an exploit for this is trivial and you should expect automated internet-wide attacks before the day is out.

You should take immediate steps to protect yourself. This is as bad or worse than the previous highly-critical vulnerability SA-CORE-2014-05 that wreaked havoc three and a half years ago affecting more than 12 Million websites.

(Like, seriously, if you are reading this and you are not on Platform.sh or another provider that has put a platform-level mitigation in place, go update your sites and then come back and finish reading. Please. Platform.sh customers, see below for how to quickly update your site.)

Where does the vulnerability come from?

The issue is in Drupal's handling of HTTP request parameters that contain certain special characters. These characters have special meaning in various places in Drupal, which if misinterpreted could lead to unexpected code paths being executed. The solution in the latest patch is to filter out such values before passing them off to application code.

Fortunately that same strategy can be implemented at the network layer. We have therefore applied the same logic to our Web Application Firewall to reject requests containing such values and deployed it across all projects in all regions, both Platform.sh Professional and Platform.sh Enterprise. That should protect all Drupal and Backdrop installations running anywhere on Platform.sh until they are upgraded.

What to do?

You must update any and all Drupal instances with 6.x, 7.x and 8.x or Backdrop CMS, or verify that your hosting provider has put in place an automated mitigation strategy for this vulnerability. (All Platform.sh clients are safe; our new WAF now detects and blocks all variants of this attack). Even if your hosting provider has a mitigation strategy in place you should update immediately anyway.

Drupal 6.x is no longer maintained and unlike Drupal 7.x and 8.x it does not support automated updates. Third-party support providers may provide a patch but you should make plans to upgrade from Drupal 6 to Drupal 8 as soon as possible.

Hopefully you are using Composer for your Drupal 7.x and 8.x or Drush make for Drupal 7.x, as is the default with Platform.sh installations.

To upgrade Drupal via Composer

To update your Drupal instances, and test nothing breaks you can follow the following simple procedure:

Verify that your composer.json file does not lock down drupal core to a minor version it should be something like "drupal/core": "~8.0". Then run:

git checkout -b security_update composer update

Make sure that Drupal Core was updated to 8.5.1 or higher. (Check composer.lock using git diff). Commit and push your changes:

git commit –am ’fix for SA-CORE-2018-02’ && git push

On Platform.sh you can test that everything is fine on your automatically-generated staging environment, then merge to master putting this to production.

If you do not use Platform.sh you should test this either locally or your testing server; and follow your normal procedure to update your live sites.

To upgrade Drupal using Drush Make

If you are using "Drush Make" style of dependency management, again, make sure you are not locked down to a vulnerable version such as:

projects[drupal][version] = 7.57

if it is, bump it up to 7.58. Then make a branch and update it:

git checkout -b security_update drush pm-update

Commit the changes and push the result to Platform.sh for testing. Once you're satisfied nothing is broken merge back to master and deploy.

To upgrade Drupal if you're checking Drupal core into your repository

If you're running a "vanilla" Drupal setup, with all of Drupal checked into Git, the easiest way to upgrade is using drush.

In your local environment, go to your Drupal document root and run:

git checkout -b security_update drush pm-update drupal

Commit the changes and push the result to Platform.sh for testing. Once you're satisfied nothing is broken merge back to master and deploy. Afterward, look into how to migrate your site to a dependency managed configuration, preferably Composer. It will make maintenance far easier and more robust in the future.

As a reminder, your Platform.sh instances are not vulnerable as they are protected by our WAF. You should still apply the fixes ASAP.

Damien Tournoud 28 Mar, 2018
Categories: Drupal

Platform.sh: SA-CORE-2018-002 Drupal core vulnerability: We've got you covered

Planet Drupal - 28 March 2018 - 12:56pm
SA-CORE-2018-002 Drupal core vulnerability: We've got you covered Crell Wed, 03/28/2018 - 19:56 Blog

An hour ago the SA-CORE-2018-002 critical Drupal vulnerability was disclosed. It was announced a week ago PSA-2018-001. That allowed us to gather our technical team and make sure we can develop and deploy a mitigation to all our clients immediately as the issue is made known.

If you're not running on Platform.sh, please stop reading this post and go update your Drupal site to version 8.5.1 / 8.4.9 / 8.3.8 / 7.58 right now. We're serious; upgrade first and ask questions later.

If you are running on Platform.sh: You're safe and can continue reading... then upgrade.

The vulnerability (also referred to as CVE-2108-7600) affects the vast majority of Drupal 6.x, 7.x and 8.x sites and allows arbitrary remote code execution that allow anonymous remote users to take full control of any affected Drupal site prior to 8.5.1 / 8.4.9 / 8.3.8 / 7.58.

The same issue is present in Backdrop CMS installations prior to 1.9.3.

If your Drupal site is not hosted on Platform.sh we encourage you to immediately update all your Drupal sites to 8.5.1 / 7.58 or to take your site offline. This is serious and trivially exploitable. You can expect automated attacks to appear within hours at most. If you are not on Platform.sh or another provider that has implemented a mitigation your site will be hacked. This is as critical as the notorious “DrupaGeddon” episode from three and a half years ago.

If you are hosting on Platform.sh...

Platform.sh is pleased to announce all Drupal sites hosted on all our regions and all our plans are automatically safe from this attack.

Platform.sh has many security layers that make attacks such as this much harder than on comparable services. Starting from our read-only hosts and our read-only containers, through our auditable and reproducible build-chain, and static-analysis based protective block.

In response to this latest vulnerability, we've taken two important steps:

  1. We've added a new rule to our Web Application Firewall (WAF) on all regions and on all Enterprise clusters that detects and blocks requests trying to exploit this latest attack vector, even if your site hasn't been updated. (But still, please update.)

  2. We are adding a check to our protective block to prevent deployment of affected Drupal versions. If you try to push an insecure Drupal version our system will flag it for you and warn you that you are pushing known-insecure code. Please update your code base as soon as possible.

As a client if you need any further assistance or want more information about the vulnerability, how it may affect you, and our mitigation strategy don’t hesitate to contact support. We have set our WAF to an especially aggressive stance for now and this may result in some users seeing a "400 Bad Request" message in some edge cases for legitimate traffic. If you experience this, please contact our support immediately they will be able to help.

Ori Pekelman 28 Mar, 2018
Categories: Drupal

Pantheon Blog: Security Update: Drupal SA-2018-002

Planet Drupal - 28 March 2018 - 12:28pm
The Drupal Security Team has published Drupal SA-2018-002 to address a critical vulnerability. This the first update of this magnitude since SA-2014-005 (aka “Drupageddon”) back in 2014. In that case, the time from release to automated exploitation was around seven hours.
Categories: Drupal

myDropWizard.com: HIGHLY CRITICAL Drupal core security update for SA-CORE-2018-002 (including Drupal 6!)

Planet Drupal - 28 March 2018 - 12:25pm

Today, there is a Highly Critical security release for Drupal core to fix a Remote Code Execution (RCE) vulnerability. You can learn more in the security advisory:

Drupal core - Critical - Remote Code Execution - SA-CORE-2018-002

As we noted last week, this issue also affects Drupal 6! So, we're also making a Drupal 6 Long-Term Support (D6LTS) release of Drupal core.

Drupal 6 core security update

As you may know, Drupal 6 has reached End-of-Life (EOL) which means the Drupal Security Team is no longer doing Security Advisories or working on security patches for Drupal 6 core or contrib modules - but the Drupal 6 LTS vendors are and we're one of them!

Here you can download the Drupal 6 patch to fix, or a full release ZIP or TAR.GZ.

If you have a Drupal 6 site, we recommend you update immediately! We have already deployed the patch for all of our Drupal 6 Long-Term Support clients. :-)

If you'd like all your Drupal 6 modules to receive security updates and have the fixes deployed the same day they're released, please check out our D6LTS plans.

Note: if you use the myDropWizard module (totally free!), you'll be alerted to these and any future security updates, and will be able to use drush to install them (even though they won't necessarily have a release on Drupal.org).

Categories: Drupal

Security advisories: Drupal core - Highly critical - Remote Code Execution - SA-CORE-2018-002

Planet Drupal - 28 March 2018 - 11:14am
Project: Drupal coreDate: 2018-March-28Security risk: Highly critical 21∕25 AC:None/A:None/CI:All/II:All/E:Theoretical/TD:DefaultVulnerability: Remote Code Execution Description: 

CVE: CVE-2018-7600

A remote code execution vulnerability exists within multiple subsystems of Drupal 7.x and 8.x. This potentially allows attackers to exploit multiple attack vectors on a Drupal site, which could result in the site being completely compromised.

The security team has written an FAQ about this issue.

Solution: 

Upgrade to the most recent version of Drupal 7 or 8 core.

  • If you are running 7.x, upgrade to Drupal 7.58. (If you are unable to update immediately, you can attempt to apply this patch to fix the vulnerability until such time as you are able to completely update.)
  • If you are running 8.5.x, upgrade to Drupal 8.5.1. (If you are unable to update immediately, you can attempt to apply this patch to fix the vulnerability until such time as you are able to completely update.)

Drupal 8.3.x and 8.4.x are no longer supported and we don't normally provide security releases for unsupported minor releases. However, given the potential severity of this issue, we are providing 8.3.x and 8.4.x releases that includes the fix for sites which have not yet had a chance to update to 8.5.0.

Your site's update report page will recommend the 8.5.x release even if you are on 8.3.x or 8.4.x. Please take the time to update to a supported version after installing this security update.

This issue also affects Drupal 8.2.x and earlier, which are no longer supported. If you are running any of these versions of Drupal 8, update to a more recent release and then follow the instructions above.

This issue also affects Drupal 6. Drupal 6 is End of Life. For more information on Drupal 6 support please contact a D6LTS vendor.

Reported By: Fixed By:  Contact and more information

The Drupal security team can be reached by email at security at drupal.org or via the contact form.

Learn more about the Drupal Security team and their policies, writing secure code for Drupal, and securing your site.

Categories: Drupal

Microsoft says Sea of Thieves sold well, even without counting Game Pass copies

Social/Online Games - Gamasutra - 28 March 2018 - 10:08am

With over 2M players, Microsoft has hailed the game as its "fastest-selling first-party new IP of this generation" and notes that that praise is without counting copies given away through Game Pass.  ...

Categories: Game Theory & Design

Pages

Subscribe to As If Productions aggregator